Your front desk, at every hour.
It answers the questions you get every day and organises the next step, working from your own information and the handoff rules you set.
Custom-built for your team. Built to order for your team: we scope the job with you, then build and hand over.
What a front desk cannot cover
The hours after six.
Questions arrive all evening. They are answered in the morning, by which time the person asking has gone elsewhere.
The twelfth identical question.
Timings, directions, what is included, whether you are open on Sunday. Trained staff spend the morning on answers that never change.
Three people waiting at once.
Somebody at the counter, somebody on the phone, somebody typing. One of the three is always being kept waiting.
Answers, organises, and knows when to stop.
The whole build is the four sentences below and the line under them. Everything else is your information and your rules.
Answers what you are actually asked.
From your own material — services, timings, what a visit involves. If the answer is not in what you gave it, it says so and fetches a person rather than improvising one.
Organises the next step.
The appointment request, the callback, the visit. Captured against the rules you set and put in front of whoever owns the diary.
Works where your customers already are.
The channel is confirmed in scoping rather than assumed, because what is possible depends on your provider and not on our enthusiasm.
Knows when to stop.
Negotiation, a complaint, anything outside the agreed brief — handed to a person with the conversation attached, so nobody starts from “hello”.
How a front desk build runs.
The first session is the one that decides whether the rest is worth doing. We would rather find a missing source there than in week four.
Scope together
Questions it can answer, booking steps, channels and the systems it needs to connect to.
Build on your information
Your services, timings and words. Where something is undecided — a price, a policy, who owns an answer — we flag it rather than fill it in.
Test with your team
The people on the desk try it on real questions, including the awkward ones, before anybody outside sees it.
Live and reviewed
Training, documentation, and a monthly read on what was asked, what it answered and what it passed over.
The first month is the one that matters.It is when the questions you did not predict arrive. We watch that month closely and change the rules with you rather than after you complain.
What is included, and what is not.
Agreed in scoping
- The questions it can answer
- The booking or request steps it can take
- The channels it works on
- The systems it needs to connect to
- The words it uses, in your voice
- Who gets notified, and how
Stays human
- Negotiations
- Complaints, and anything that has gone wrong
- Decisions outside the agreed brief
- Pricing, packages and discounts
- Anything clinical, legal or regulated
Related pages, if this one is not quite it.
Clinics & aesthetics
Where this role is asked for most, and the clinical line it never crosses.
AI systems
How any build is scoped, tested and handed over.
The AI workforce
The other five roles.
Tell us the job, not the tool.
Ask what people ask about the AI Receptionist, or describe what needs doing and who does it now. A person replies within one working day, and we will say if this is the wrong role for you.
Brand Wisdom A person reads every enquiry and replies within one working day.
Tell us what’s going on and we’ll help you work out the next step. A person reads every one of these, and you’ll hear back within one working day.
What should we work on?
Or ask first
No. A chatbot answers from a script somebody typed into it. This answers from your own information, does something with the answer — captures the request, notifies your team, records the conversation — and hands over when it should.
It says so and hands the conversation to a person, with the context. Those cases are defined before the build and tested during it; a workflow without an agreed handover is not finished.
Not necessarily, and that is a scoping question rather than a yes. What is possible depends on your provider and your account, and we confirm it before promising anything about a number.
We will walk you through a build on a call using examples from your own business, and you can ask it the questions your customers actually ask. We are not going to send you somebody else’s demo and call it proof.
It is designed to fail towards a person: when it cannot answer it stops, says so, and fetches someone, and your team is told. A system that guesses confidently is worse than one that admits a gap.
We store your answers so we can reply. Read what we keep and why in our privacy notice.