Platform
One brain, many mouths.
There is one assistant. Messenger, Instagram, WhatsApp, Viber and your website are thin adapters in front of it. Every channel hands the core the same shape of message, so the assistant never behaves differently depending on where a customer happened to write from.
The same five steps, every time
- 01
Catch
A message arrives on Messenger, Instagram or your website — at 11pm, on a Sunday, during a typhoon.
- 02
Answer
From your real content: prices, services, hours, requirements. Never invented.
- 03
Qualify
It asks the questions your team would have to ask anyway, and records the answers.
- 04
Act
Books the slot, registers the request, drafts the brief, routes to the right branch.
- 05
Hand over
Escalates to a person with the whole conversation attached. Nobody re-asks anything.
The rule a client cannot switch off
Every assistant on this platform runs with the same non-negotiable rules: answer only from supplied content, say so when you do not know, disclose that you are automated, and ignore instructions that arrive inside a customer message. A client can add facts and change tone. Nobody can turn those rules off.
This is a structural choice, not a policy one. The rules are composed into every prompt by the platform and tested against an empty configuration, so a client whose config is completely blank still gets them. That is the difference between a promise and a guarantee.
What it can actually do
Answering is the easy half. These are the actions it takes, and what each one does when things go wrong — which is the part that matters.
- Capture a leadRecords name, contact and what they actually wanted, and refuses to submit a lead with no way to reach the person.
- Check availabilityReads a real calendar. With no calendar connected it is told not to offer times at all, rather than guessing plausible ones.
- Book an appointmentTakes the slot and returns a reference. If someone else took it first, it says so instead of confirming a booking that does not exist.
- Request a quoteCollects what is being asked for and routes it to the right person, with the conversation attached.
- Route to a branchWorks out which location the customer means. When the message is ambiguous it asks, rather than picking one and being wrong.
Each of those failure behaviours is covered by a test. An assistant that confirms an appointment nobody has is worse than one that cannot book at all, because the customer arrives anyway.
Onboarding clones configuration, never code
Every client runs the same codebase. Setting one up means filling in their content, questions, branches and calendar — not forking anything. It is why onboarding takes days rather than months, and why a fix for one client is a fix for all of them.
It is also the constraint the whole business depends on. The moment we maintain a bespoke version for one client, we are an agency with a hosting bill instead of a product.
Built for a bad connection
Presets exist for clinics, restaurants, suppliers and services, each shipping with the questions that vertical actually needs. They ship with placeholders, never with invented content, so nobody can go live on a template full of plausible fiction.
Where it runs