Enquiry handling that does not wait for business hours
A first response the moment someone messages, not the next time someone checks a shared inbox.
Everything below is ours and on our servers. Nothing follows you to another site.
Who
How we work
Rebuild
SMART BOTS · WHATSAPP AND TELEGRAM
Most enquiries do not wait for a website to load. They happen in an app the customer already has open, on a number they already trust, and a bot built for that channel answers faster than a contact form ever will.
A build here means enquiry handling, catalogue browsing, booking and routing running on WhatsApp and Telegram directly, on the same infrastructure we use to run our own support. You own the integration once it ships.
WHAT ACTUALLY BREAKS
Four problems specific to messaging apps, not generic complaints with the word bot swapped in.
A first response the moment someone messages, not the next time someone checks a shared inbox.
No app to download and no separate page to navigate to see what is available.
A slot confirmed in the same thread the enquiry started in, not a handoff to a booking page that loses the customer.
The conversation reaches whoever can actually answer it, the same load-based principle behind our own support.
Each of these is handled once, in the build, rather than left to whoever is next to check a shared phone.
WHAT WE BUILD
Four capabilities, sharing one data model rather than four separate tools stitched together after the fact.
THE ADMIN SIDE
Most vendors sell a script that runs until something changes, then bill you to change it. We hand over the console your own administrator edits themselves, without a developer.
An illustrative example of the interface, not a live feed. The conversations, names and numbers shown are not real.
PROOF
Not a demo. The exact channel and number we use every day.
The official channel, not a scraped integration that breaks the moment a policy changes.
The same number every visitor to this site can message right now, routed the same way a client’s bot would route an enquiry.
Open WhatsAppThe same infrastructure, used on ourselves first.
WHAT IT COSTS
A range, not a fixed price, because how many flows it handles moves the number.
Third-party services, including WhatsApp Business API and Telegram fees, are billed at cost. We do not mark up other people's software.
Usually toward the lower end for a single-purpose bot.
One or two channels, one or two jobs, shipped fast.
Code and integration, from handover.
STRAIGHT ANSWERS
The ones that come up on almost every call before a first message goes live.
Because that is where the conversation already happens. A widget waits for a visitor to notice it on a page they may never return to. WhatsApp and Telegram put the enquiry in an app people already have open, on the number they already use, which is why we run our own support through the same channel.
Enquiry handling, catalogue browsing, booking and routing to the right person, built on the WhatsApp Business API rather than a scraped integration that breaks when a policy changes. What it does not do is pretend to be a person indefinitely — it hands off to a human the moment a conversation needs one.
Scope and speed. A smart bot is built in days because it does one or two jobs on one channel, not because the engineering is shallow. If the requirement grows into a full CRM or an omnichannel inbox, that is a larger build we scope separately, not something this hides inside a small quote.
Between
A technical review covers speed, security, how search engines see your site, and what your current setup really costs each year. Two days, no charge, no obligation, and you keep the report whether or not you hire us.
WhatsApp and Telegram are different channels with different capabilities. Each has its own page below covering what is specific to it.
One tap, then your app opens with it written.