The call path in one view

Six stages run on every call: the phone network, speech-to-text, conversation logic, your business tools, text-to-speech and the record. Each one can fail on its own, so test each one.

Details

Every call to an AI receptionist passes through six main stages, most of them invisible to the caller. The phone network delivers the call. Speech-to-text turns the caller's words into text. Conversation logic works out what the caller wants and what to say next, using only the facts and rules you supplied. Business tools then act: the calendar, the transfer line, the alert to your phone. Text-to-speech speaks the reply. Last, the system writes a record of what happened. Each of those stages can fail on its own. A pleasant voice proves that two stages work and says nothing about the other four. Those four decide whether the plumber gets the job and whether the law firm hears about a new client before a rival does. A federal regulator saw the same pattern in bank chatbots: useful for basic questions, weaker as problems got complex10.

Phone network

speech-to-text

conversation logic

business tools

text-to-speech

record

Open End-to-end sequence diagram

End-to-end sequence diagram

End-to-end sequence diagramFollow each step in order. Every arrow is a point where a call or chat can go wrong.
End-to-end sequence diagramFollow each step in order. Every arrow is a point where a call or chat can go wrong. The complete sequence is repeated as text after the diagram.1Answerverify before next2Qualifyverify before next3Actverify before next4Confirmverify before next5Recoverrecord outcome
  1. Answer: Identify the caller's intent without assuming the requested action is allowed.
  2. Qualify: Collect only the information needed by the approved workflow.
  3. Act: Attempt the booking, routing or message action against the live destination.
  4. Confirm: Read back or otherwise confirm the downstream result.
  5. Recover: Escalate failures to a named person with context.
Phone network
The call travels from the caller's phone to the system, often by call forwarding from your existing number. If forwarding is set wrong, nothing after it runs.
speech-to-text
The caller's words are turned into text. A misheard address or name here sends wrong details down the rest of the chain.
conversation logic
The system works out what the caller wants and what to say next, using only the facts and rules you supplied.
business tools
Here the system acts: it books on the calendar, rings the transfer line or sends an alert to your phone. This stage decides whether the job really gets booked.
text-to-speech
The reply is spoken back to the caller. A pleasant voice proves only that this stage and speech-to-text work.
record
Last, the system writes down what happened on the call. That record is how you check that the other five stages did their jobs.
Show sequence-step details

Follow each step in order. Every arrow is a point where a call or chat can go wrong.

  • Phone network: The call travels from the caller's phone to the system, often by call forwarding from your existing number. If forwarding is set wrong, nothing after it runs.
  • speech-to-text: The caller's words are turned into text. A misheard address or name here sends wrong details down the rest of the chain.
  • conversation logic: The system works out what the caller wants and what to say next, using only the facts and rules you supplied.
  • business tools: Here the system acts: it books on the calendar, rings the transfer line or sends an alert to your phone. This stage decides whether the job really gets booked.

Step 1: the call reaches the service

The call has to reach the software first. That means a new number or forwarding from your carrier, plus a plan for the second and third callers who ring in the same minute.

Details

Your customers can keep dialing the number they already know. There are two common setups. The service gives you a new number to publish, or you forward your existing line to it, either all the time or only when nobody picks up. Forwarding is set at your phone carrier, not at the vendor, so ask who sets it up and who fixes it when it breaks. Then ask what happens when three calls arrive in the same minute. A system that answers one and gives the others a busy signal has moved the missed call, not removed it. Check the direction too. Some products, First AI Employee among them, answer inbound calls only2.

Number provisioning

call forwarding

simultaneous calls

Step 2: the system hears and speaks

The system has to hear the caller, know when they have finished, and answer without an awkward pause. Accuracy varies by speaker7, so test with your real callers' voices.

Details

A caller talks over the greeting to say the water heater is leaking. The assistant has to stop, hear the interruption and judge when the caller has finished. Each step adds delay. Interruption handling needs its own test. FD-Bench, published at Interspeech 2025, evaluated three open-source dialogue systems using 293 simulated conversations and 1,200 interruptions. The systems still struggled with disruptions and noise21. That study does not rank today's receptionist services. Test what happens after you interrupt: does the assistant stop, hear the correction and continue from the right detail? Repeat the call with your customers' accents, from a truck, a busy kitchen and a weak signal.

Turn-taking

interruptions

latency

accents and noise

Open Latency budget illustration

Latency budget illustration

Latency budget illustrationFollow each step in order. Every arrow is a point where a call or chat can go wrong.
Latency budget illustrationFollow each step in order. Every arrow is a point where a call or chat can go wrong. The complete sequence is repeated as text after the diagram.1Answerverify before next2Qualifyverify before next3Actverify before next4Confirmverify before next5Recoverrecord outcome
  1. Answer: Identify the caller's intent without assuming the requested action is allowed.
  2. Qualify: Collect only the information needed by the approved workflow.
  3. Act: Attempt the booking, routing or message action against the live destination.
  4. Confirm: Read back or otherwise confirm the downstream result.
  5. Recover: Escalate failures to a named person with context.
Turn-taking
The system has to judge when the caller has finished. Jumping in early cuts people off, and waiting too long sounds like a dropped line.
interruptions
When a caller talks over the greeting to say the water heater is leaking, the system should stop talking and listen.
latency
Each step adds a little delay between the caller finishing and the reply starting. Callers hear that delay as awkwardness.
accents and noise
Accuracy depends on who is speaking and from where. Test with your customers' accents, from a truck, a busy kitchen and a weak signal.

Step 3: business knowledge constrains the answer

The assistant should answer only from facts you approved. Tools that answer from their own documents still make errors13, so check what it says when it does not know.

Details

Good answers start with the facts you hand over. Short facts behave well: hours, service area, standard prices, which brands you repair. Long documents behave worse, because the system picks a passage and rewrites it, and a policy written for a careful reader can come out wrong. Answering from your own documents does not make it error-free. In one study, commercial legal research tools that answer from their own libraries still made things up 17% to 33% of the time, on questions far harder than a business FAQ13. So ask what it says when a caller raises something you never covered. Taking a message beats guessing an accountant's fee at midnight.

Structured facts

documents

unknown questions

Step 4: rules and tools take action

Rules decide what the assistant may do, and connected tools do it. Judge the finished booking, transfer or message, not the sentence that promised it.

Details

Talking is what vendors demo. Acting is what changes your week. A booking counts only when an event appears on your calendar. First AI Employee, for example, books straight onto a connected Google, Outlook or Calendly calendar, or onto its own built-in calendar1. Routing either connects the caller to a person or fails. Intake fills the fields you chose, so pick fewer and better ones. Alerts put the result in front of someone who can act. Take care if the system also calls customers back. The FCC confirmed that AI-generated voices count as an artificial voice under the TCPA9, so those calls need prior express consent unless an exemption applies20. This is not legal advice.

Booking

routing

intake

notifications

Step 5: fallbacks contain failure

Something will fail: the calendar, a transfer, or the system's grasp of the question. A good fallback keeps the caller's details, says what happens next, and never traps them in a loop10.

Details

Your first outage will land on a busy day, so decide now what callers hear. The calendar times out. The on-call phone rings out. The system half understands a caller, which is worse than not understanding. Someone asks a vet clinic about a dose or a law firm for advice. A good fallback tells the caller what happens next and puts the request in front of a named person. Two findings shape that design. Bank chatbots can trap people in loops with no way to reach a human10. And in text-chat studies, a chatbot with a human name and persona lowered satisfaction when customers arrived angry14. Send upset callers to a person fast.

Calendar down

transfer fails

low confidence

out-of-scope

Open Failure-point callouts

Failure-point callouts

Calendar down
The calendar times out mid-booking. A good fallback says the time is not confirmed, takes the details and puts them in front of a named person.
transfer fails
The on-call phone rings out. The caller should hear what happens next, not ringing that never ends.
low confidence
The system half understands the caller, which is worse than not understanding. It should ask again or pass the call on instead of acting on a guess.
out-of-scope
Someone asks a vet clinic about a dose or a law firm for advice. The system should decline and route the request to a person.

Step 6: the call becomes a record

Every call leaves a summary, often a transcript, sometimes a recording. Consent rules for recording differ by state17, so check what callers hear and how long each record is kept.

Details

On Monday a customer disputes the price they heard on Saturday. What the system kept decides if that costs five minutes or an afternoon. A summary is the system's reading of the call, good for sorting work but not proof. A transcript is closer but can hold words nobody said: a 2023 test of one engine, Whisper, partly on speakers with a speech disorder, found about 1% of transcripts held whole invented phrases12. A recording is the best proof and the most regulated. Federal law lets one party consent to recording16. About 11 states require every party's consent17, and California is one of them15. Ask how long each record is kept and who can export it. This is not legal advice.

Summary

transcript

recording

retention

Example call, annotated

One made-up evening call, broken into what the caller says, what the system checks, and what lands on your phone. It shows the process. It is not a recording of any real product.

Details

Follow one evening call to a property manager. The greeting says the caller is talking to an automated assistant. California bans online bots that hide what they are to make a sale, though its reach to phone calls is unsettled18. Utah requires a business's generative AI to say so when a person clearly asks19. Disclosure can cost sales: in one outbound experiment in China, it cut purchases by more than 79.7%8. Disclose anyway. This is not legal advice. The caller says her tenant has no heat. The system matches that to your urgency rules, checks the address, finds an evening slot and books it. You get the address, callback number, the words no heat, and a calendar event.

What the caller says

what the system checks

what the business receives

Open Annotated sample transcript

Annotated sample transcript

Show synthetic call example

A made-up case to test a product against. It is not a result from any real product or customer.

  • What the caller says: An evening caller tells a property manager's line that her tenant has no heat. The greeting has already said she is talking to an automated assistant.
  • what the system checks: It matches no heat to the urgency rules, checks the address against the properties on file and looks for an evening slot.
  • what the business receives: The manager gets the address, the callback number, the words no heat and a calendar event for the visit.

What to ask a vendor

Ten plain questions that make a vendor show you the whole call path, including an action that fails. Write down each answer and anything they could not show you.

Details

Ask these ten questions and get the answers in writing. Who sets up call forwarding? How many calls can it answer at once? Can I hear it handle an interruption and a heavy accent? What does it say when it does not know? Does a booking create a real calendar event? What does a caller hear when the calendar or a transfer fails? Who gets alerted, and how fast? How long are summaries, transcripts and recordings kept? What does the greeting say about being AI? When the software cannot finish a call, who picks up? Answers differ: Smith.ai offers live agents as a per-call add-on3, while Dialzara transfers to your own team5.

Open Technical buyer questions

Technical buyer questions

  1. 1. What the caller needsCan I hear it handle an interruption and a heavy accent? Ask for a live test call, not a recorded demo.
  2. 2. What the receptionist may doDoes a booking create a real calendar event? Ask the vendor to book a test slot and show you the event.
  3. 3. If it failsWhat does a caller hear when the calendar or a transfer fails? Get the exact wording in writing.
  4. 4. Record that proves itHow long are summaries, transcripts and recordings kept? Ask who can see them and whether you can change the period.
  5. 5. What the caller needs: calls at the same timeHow many calls can it answer at once? A dental office at opening time or a landlord after a storm may get several together.
  6. 6. What the receptionist may do: the AI greetingWhat does the greeting say about being AI? Ask to hear it, and ask what it says when a caller asks directly.
  7. 7. If it fails: who picks upWhen the software cannot finish a call, who picks up? Some vendors offer their own live agents, and others transfer to your team.
  8. 8. Record that proves it: urgent alertsWho gets alerted after an urgent call, and how fast? Ask to see a sample alert as it would reach the on-call phone.
  9. 9. What the caller needs: honest gapsWhat does it say when it does not know the answer? Ask it a question you never set up and listen.
  10. 10. What the receptionist may do: call forwardingWho sets up call forwarding from your existing number? Ask whether the vendor does it or sends you instructions.

The table above is the accessible HTML version. Downloads contain the same blank prompts and no hidden scoring.

Frequently asked questions

Short answers on how these calls work. In 2024, just over half of US adults said they were more concerned than excited about AI in daily life11, so be ready to explain your setup.

Details

Frequently asked questions

Does an AI receptionist listen to audio directly?

Most systems turn the caller's speech into text, use conversation rules and connected tools to choose the next reply, then turn that reply back into speech. Setups differ, and some parts may work on the audio itself.

Why is there sometimes a delay?

Delay can come from the phone network, the speech recognition, the AI's reply, a connected tool or the voice that speaks the answer. Test with realistic calls, not just a scripted greeting.

How does it know my business?

Providers load the information you approve, such as hours, services, prices, common questions and call rules. A safe system says it does not know when the answer is missing or unclear.

How can it book without making mistakes?

It should read your live calendar, create the event through a secure calendar connection and wait for the calendar to confirm it before telling the caller the appointment is booked.

Can it understand every caller?

No. Background noise, accents, bad connections, names and unusual requests can all cause mistakes. Test it with the kinds of calls you really get, and make sure it repeats details back, confirms them and has a fallback.