A time is invented
A booking is confirmed only from the connected diary.
AI receptionist for inbound calls
Answer missed inbound calls, capture the useful facts and create a clear next action without inventing availability, prices or private account answers. A focused setup is usually £800 - £1,500.
Provider, telephone number, call usage and model charges remain separate. This service covers inbound answering, not automated outbound marketing calls.
Name, number and main problem confirmed
Answer, capture, route and boundary stay visible.
Silent transcript, no real call
Choose a synthetic caller request. The preview shows the approved reply, structured record, next route and explicit boundary. No microphone, telephone, recording or provider is used.
“Hello, you have reached Example Business’s automated call assistant. I can take a message or help with an approved route.”
I need my shop website repaired. Can somebody call me today?
I can take the useful details for a callback. What is your name, telephone number and the main problem with the website?
This example does not record audio. A real setup states whether recording occurs and why.
The human receives the reason, confirmed contact route and unresolved point, not an invented call summary.
What a pleasant voice can still get wrong
A ringing phone interrupts live work, but a missed call gives the customer no reason to wait. Voicemail often captures too little, while a generic voice bot can sound confident, collect unnecessary information or promise an appointment, price or action that the business cannot honour.
A booking is confirmed only from the connected diary.
Published guidance and a project-specific promise stay distinct.
Unverified callers cannot receive private customer information.
Model output cannot bypass validated business rules and permissions.
One useful route through the call
The inbound call is answered with a clear business and automation introduction. The assistant follows an approved purpose, asks only the questions needed for that route, repeats important details, and creates a structured callback, booking handoff or transfer. Unknown, private, high-risk or unavailable actions stop at a human boundary.
Recording and its purpose are stated when used.
One approved purpose controls what is collected.
Unclear speech gets a limited retry or human fallback.
Failure creates a callback rather than a false success.
Choose the smallest dependable outcome
Best for a trade, clinic, salon, hospitality or service business that misses useful inbound calls while staff are working. Start with message capture when a callback is enough; add qualification, live transfer or booking only when the script, system connection, caller information and fallback have a clear owner.
Capture name, contact route and reason, then notify the owner.
Lowest risk and fastest useful start.Ask approved service, location, urgency or project questions without giving a quote.
Best for trades and service businesses.Check hours, route a call, or hand into booking and CRM with validation.
Only when provider and fallback behaviour are proven.Tell the caller before collecting
Calls can contain personal information about callers, customers and workers. The business needs a stated purpose, lawful basis, privacy information, access rules, provider details and retention for every recording, transcript or structured message.
Full audio is not the default merely because a provider offers it. A short structured record may meet the need with less information at risk.
Providers checked before the quote
Ernest checks the number, call forwarding, voice and model provider, supported countries, hours, latency, recording controls, live transfer, booking or CRM API and failure route before naming the implementation.
Business hours and no-answer timeout are tested
Provider outage creates a plain fallback
Duplicate calls and actions do not duplicate records
Proof without an invented deployment
There is no named AI receptionist deployment in the current Work library. This transcript demonstrates the intended acceptance standard, while the separate AI Assistant and booking pages show the approved-answer and live-diary disciplines that a call route may connect.
See the approved-answer standardAcceptance is the difficult call handled safely
AI receptionist setup price
The proposal confirms call purposes, scripts, knowledge, actions, hours, disclosure, providers, fallback and tests before work starts.
See all website and system pricesPrice rises with several numbers, languages, complex qualification, live transfer, recording, sensitive information, booking or CRM actions and detailed reports.
Support is optional. Phone, number, model, transcription and call usage providers charge separately.
Before answering inbound calls
Yes. The opening identifies the business and makes the automated role clear before collecting details. If audio is recorded, the caller is also told that recording is taking place and why. The longer privacy information can be provided through an agreed website, message or follow-up route.
No. Full audio should have a specific, justified purpose, access rule and retention period. A structured message or short transcript may be enough and less intrusive. The proposal states what the provider processes, what the business keeps and how callers can exercise their information rights.
Yes, when the live diary or phone provider offers a dependable connection. Availability must be checked at the point of booking, and transfer needs opening hours, ring duration, fallback and voicemail rules. A failed connection creates a callback record instead of a false confirmation.
It asks for a short repeat, confirms important details and limits the number of attempts. Background noise, accents, speech differences and poor connections are included in testing. The caller can request a person or leave a basic callback route rather than being trapped in a loop.
Only within the approved information and identity boundary. A public inbound call should not reveal a balance, booking, address or other private record merely because the caller knows a name. Sensitive requests move to a secure human or authenticated route.
No. This service page covers inbound answering. Automated outbound marketing calls have separate consent and identification requirements and are not silently added to an inbound call project. Any future outbound use would need its own legal, provider and customer-experience review.
Bring ten recent missed-call reasons
Show Ernest what callers need, when the team can take over and which systems hold the truth. You will know whether a structured message, qualified callback or connected route is appropriate.