AI front desk
Every customer answered
before they call someone else.
One AI assistant trained on your business answers, qualifies and books — across your website, your phone and your messaging channels. One assistant on every channel, one record of every conversation.

The leak
More traffic doesn’t help
if nobody answers.
A local customer messages a few businesses and books the one that answers first. The leak is usually between the inquiry and the reply.
Illustrative day — statuses change, no metrics implied.

Context travels
One assistant.
Everywhere customers ask.
The customer switches website, phone, SMS, WhatsApp — the assistant keeps the name, the service and the history. One thread, not six bots.

01 · What it knows
It only works if it knows your business.
It answers from verified business knowledge only — your services, prices, areas, policies — and checks before it responds.

02 · Answer vs action
A basic bot answers. An agent acts.
Answering is only the start. The value is what happens after the words — the booking, the record, the confirmation.

03 · What it does
Six jobs your assistant takes off the desk.
Trained on your services, prices, policies and FAQs. It answers in your voice and knows when to bring in a person.
Answer
Hours, prices, service areas, what to bring — instant, in your words, from verified knowledge, on every channel.

Sample scenes — illustrative content, not a real conversation.
04 · Confidence & boundaries
The best AI knows when not to guess.
It answers from verified knowledge, acts only where it has permission, and hands off the rest. It never improvises.

Sample decision — example chosen to show behaviour, not a real case.
05 · Permissions
Not every action should be available to AI.
Read, write, act — the assistant gets only the access you grant. Restricted and sensitive actions stay with a person.
The assistant gets only the access you grant — nothing more.
06 · Contextual handoff
When a human takes over, the context comes with it.
The customer never repeats themselves. The human opens the conversation with the full context already in hand.

07 · The connected system
The conversation doesn’t end in the chat window.
One data object moves from the chat into your calendar, CRM and alerts — wired through the tools’ own APIs.
Illustrative — connected through your calendar, CRM and alert tools via their APIs.
08 · Chat + voice, one core
Chat or call, the core stays the same.
Text or voice comes in at the top; everything below the channel layer is shared — knowledge, logic, permissions, actions.
Chat or call, everything below the channel layer is shared.
09 · Testing
Before customers try it, we do.
We test behaviour, not just that the chat works: pricing, out-of-area, off-topic, complaints, no availability, handoffs.

10 · The build
Live on your site in 10 business days.
You approve the script before we build. You test it on your own questions before it goes live. The phone line adds 5 days.
Scope + knowledge
What it handles, where a person takes over, and the source material.
11 · Plans
Pick how much of the desk it covers.
One-time build, yours to keep. Care plans are optional. Usage (AI model + phone minutes) is billed separately, at cost to your accounts.
Usage is separate: the AI model and phone minutes are billed by the providers to your own accounts. You get the estimate for your volume before you sign.
12 · Guardrails
Automate the right things.
The line is the product. Automate the routine; keep judgment and sensitive calls with a person.
13 · Who this is for
How it answers, what it’s allowed to do, and what you own.
Yes. One assistant, trained once on your business, works across your website, phone, SMS, WhatsApp, Instagram and Messenger. It keeps one record of the conversation no matter where the customer starts or continues.
Ready when you are
Answer. Qualify. Book. Hand off.
Before the customer calls someone else.
Fixed price before work begins · usage billed at cost to your accounts








