AI receptionist or human answering service: which jobs should each handle?

A call answered is not necessarily a problem solved. Before choosing an AI receptionist or a human answering service, decide what should happen after someone picks up: accurate information, a confirmed booking or a message that reaches the right person.

An AI receptionist uses software to conduct the conversation. A human answering service uses people working to an agreed brief. Neither label tells you whether a particular supplier can use your booking system, manage exceptions or deliver a reliable handover. Test those jobs separately.

Start with a week of real call types

Keep a simple tally of why people call, when calls arrive and what the caller needs next. Use categories rather than unnecessary personal details. Separate opening-hours questions, new enquiries, booking changes, complaints and matters needing your judgement. Include the calls you already handle well.

If you only miss a few calls, a clear voicemail and a dependable callback routine may be enough. If the same factual questions interrupt your work repeatedly, a tightly limited automated service may be worth testing. A mix of routine handling and human follow-up can also be sensible.

Match the task to the boundary

A human answering service may still only take messages. Ask what its staff are authorised and trained to resolve. Healthcare deployments need competent specialist review; an approved script alone does not establish safety.

Price the whole job

Ask each supplier to price the same expected call volume and duration. Include setup, monthly subscription, included minutes or calls, overage rates, transferred-call charges, phone numbers, integrations, messages, VAT and cancellation costs. Check whether time on hold, spam and unsuccessful calls count towards usage.

Add your own time for updating instructions, checking outcomes and correcting mistakes. Use this worksheet: monthly service charges + expected usage charges + other recurring costs + the value of supervision time. Keep one-off setup separate so that both the first month and a normal month are visible.

Fictional example: a service costs £120 a month including expected usage. If each genuinely additional completed job contributes £30 after its direct costs, four such jobs cover that £120. That does not cover setup or supervision, and it is not a forecast. An answered call, a booking and a completed paid job are different outcomes.

Check privacy before switching it on

Tell callers clearly when they are speaking to AI. Explain any recording or transcription and provide accessible privacy information. The ICO says you need an appropriate lawful basis for handling personal information and must determine it before processing begins. Consent is not automatically the right basis for every activity; a recording announcement is not a substitute for assessing the requirements.

• Write down why each item of information is needed. Do not collect payment-card details or health histories in a general enquiry flow.
• Ask where audio, transcripts and summaries are stored, who can access them, whether they are used for model training and how deletion works.
• Review supplier responsibilities, security, retention and any overseas processing. Assess whether a data protection impact assessment is needed.
• Provide a workable route to a person or an alternative contact method for callers who cannot use the system.

These are procurement checks, not legal approval for a particular setup. Get appropriate advice where recording, sensitive information or sector rules are involved.

Run ten test calls before a limited pilot

Use fictional customer details. Have a colleague test these situations rather than only following the supplier's demonstration:

1. A straightforward opening-hours question.
2. A service the business does not offer.
3. A noisy connection or an unclear name.
4. A correction to a phone number already given.
5. A request for a slot that is unavailable.
6. A booking-system failure.
7. A cancellation needing identity checks.
8. A caller asking for a person.
9. A complaint needing an authorised decision.
10. An out-of-hours call when nobody can accept a transfer.

Record whether the answer was accurate, the booking actually appeared, the message arrived and the caller understood the next step. Ten calls are a starting check, not proof of reliability across all callers or situations.

Name the person who owns the fallback

Define who checks unanswered handovers, when they do it and what response time the business can honestly offer. If nobody is available, the service must not pretend that a transfer or immediate callback will happen.

Begin with a narrow job and review failures during the pilot. Pause automation if it invents prices, confirms unavailable appointments or mishandles personal information. Reliable boundaries matter more than sounding impressively human.

When you are ready to consider ongoing digital help, use the task list and test results as your brief. Explore the current options with More Hands by Foundry Works, without assuming any particular call-handling feature is included.