AI receptionist for inbound calls

Pick up promptly. Promise carefully.

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.

Incoming callsynthetic example
Caller needWebsite repair callback

Name, number and main problem confirmed

ResultHuman callback recordNo price or time promised

Answer, capture, route and boundary stay visible.

Inboundcalls the customer chooses to make
Clearbusiness and automated role
Limitedquestions, knowledge and actions
Ownedfallback, callback and review

Silent transcript, no real call

Hear the request. Keep the authority narrow.

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.

Interactive example
01
Inbound callCaller and assistant

“Hello, you have reached Example Business’s automated call assistant. I can take a message or help with an approved route.”

Caller

I need my shop website repaired. Can somebody call me today?

Assistant

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.

02
Business viewCall outcome
synthetic
Useful call record

Alex Morgan · callback requested · website repair

Next route
New enquiry for human callback
Boundary
No repair price or response time promised.

The human receives the reason, confirmed contact route and unresolved point, not an invented call summary.

What a pleasant voice can still get wrong

The call was answered. Was the promise safe?

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.

Availability

A time is invented

A booking is confirmed only from the connected diary.

Price

A rough answer becomes a quote

Published guidance and a project-specific promise stay distinct.

Privacy

A familiar name unlocks an account

Unverified callers cannot receive private customer information.

Authority

Speech becomes a privileged instruction

Model output cannot bypass validated business rules and permissions.

One useful route through the call

Introduce, understand, confirm, hand over.

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.

  1. 01
    Introduce

    Name the business and automated role

    Recording and its purpose are stated when used.

  2. 02
    Understand

    Ask the minimum useful questions

    One approved purpose controls what is collected.

  3. 03
    Confirm

    Repeat critical contact and request details

    Unclear speech gets a limited retry or human fallback.

  4. 04
    Hand over

    Create the record, transfer or open the live route

    Failure creates a callback rather than a false success.

Choose the smallest dependable outcome

Message, qualify, transfer or connect.

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.

01A callback is enough

Structured message

Capture name, contact route and reason, then notify the owner.

Lowest risk and fastest useful start.
02The team needs useful context

Qualified callback

Ask approved service, location, urgency or project questions without giving a quote.

Best for trades and service businesses.
03A live system or person should act

Transfer or connected action

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

A clear role. A justified record.

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.

01Identify the automation and business
02Explain recording and purpose when used
03Collect only what the route needs
04Set access, retention and deletion

Providers checked before the quote

Phone, knowledge, diary and handover.

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 number and inbound callApproved answers and call scriptBounded call outcomeHuman transfer or callbackBooking, CRM and notification

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

Demonstrate the boundary. Do not fake the phone.

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 standard

Acceptance is the difficult call handled safely

Test noise, refusal and unavailable systems.

01Unclear speechA limited repeat and human route prevent a loop.
02Caller refuses automationA person or message fallback is offered where agreed.
03Private account requestNo record opens without suitable verification.
04Unsafe instructionThe assistant refuses and cannot expand its tools.
05Diary unavailableNo appointment is falsely confirmed.
06Provider outageThe ordinary phone fallback remains understandable.

AI receptionist setup price

A range with visible reasons.

The proposal confirms call purposes, scripts, knowledge, actions, hours, disclosure, providers, fallback and tests before work starts.

See all website and system prices
Typical one-off setup£800 - £1,500timeline quoted after call-route audit
  • Inbound purpose, script and knowledge boundaries
  • Structured capture, notification and fallback
  • Agreed transfer, booking or CRM connection
  • Call tests, launch and handover

Price rises with several numbers, languages, complex qualification, live transfer, recording, sensitive information, booking or CRM actions and detailed reports.

Standalone support£35 - £45/moorRun Growthincluded in £199/mo

Support is optional. Phone, number, model, transcription and call usage providers charge separately.

Before answering inbound calls

AI receptionist questions.

Will callers know they are speaking to an automated assistant?

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.

Does every inbound call need to be recorded?

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.

Can the assistant book appointments or transfer calls?

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.

What happens when the assistant cannot understand the caller?

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.

Can it answer existing-customer or payment questions?

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.

Does this include outbound automated marketing calls?

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

Answer the call. Leave the risky promise to a person.

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.

Discuss your missed callsExplore every system and add-on Email or telephone only. No obligation and no phone-platform reseller pitch.