Practical operating guide
What to do when an AI receptionist cannot answer a question
By ByTomorrow · Published
The caller asks a reasonable question that the receptionist cannot verify. A fluent answer would sound reassuring, but the business may have to undo it later.
The uncomfortable moment is often ordinary: an exception to a policy, an unfamiliar request or a detail that changed since the reference material was written.
Diagnosis
Unknown answers need an actual destination
More wording does not resolve missing facts
A longer response can make an unsupported answer sound more certain. The caller needs to know what remains unconfirmed and what can happen next.
A transfer offer can be empty
Retell documents a transfer tool for phone calls and settings for unanswered destinations. That is a vendor capability. A business must still test its destination, staffing and fallback before an agent offers the transfer.
A follow-up promise can create a second failure
Do not say a person has received the question merely because the agent tried to create a task. The record and its assigned owner must exist before the agent describes that step as complete.
Working worksheet
A script and routing card for uncertainty
The answer is not verified
Suggested script: "I do not have a confirmed answer to that question." State the specific missing fact when useful. Avoid filling the pause with a guess, an estimated policy or a claim that the request will be accepted.
A tested human route is available
Suggested script before attempting the route: "I can try to connect you with the person who handles that." Offer this only when the configured route and current coverage permit it. Record the result of the attempt.
No person is available
If a follow-up queue is working, ask: "Would you like to leave your question and a contact method for review?" If that queue is unavailable too, give only an owner-approved contact option. Do not invent a callback commitment.
Minimum follow-up record
Copy this record: caller's question ___; why the answer is unverified ___; source checked ___; requested contact method ___; task identifier ___; owner ___; caller-facing expectation ___. Blank owner or task identifier means the handoff is still incomplete.
Worked example
Illustrative caller: "Will you make an exception for my request?" The agent states that the exception is unconfirmed, offers the permitted route and records the question verbatim. It does not interpret the caller's persistence as authorization to grant the exception.
Use the worksheet
Put it into practice
List questions that require a person
Ask the owner which exceptions, commitments and missing facts the agent cannot resolve. Give each category a destination and unavailable-person response.
Test the unavailable branch
Use synthetic calls while the test destination does not answer. Verify the caller hears the approved fallback and that any follow-up record is real.
Review the unresolved queue
Have the designated owner review unresolved questions and update approved reference material where an answer becomes reusable. Repeated unknowns should identify a source gap.
Questions
Straight answers.
A brief acknowledgment is enough. State the uncertainty and the available next action without delaying the caller with repeated apologies.
Respect that choice. Offer an approved way to contact the business and record only what the business is authorized to retain. Do not make contact details a condition for ending the call.
Sources and further reading
- Retell transfer-call documentation
Supports phone-call transfer configuration and unanswered-destination settings. The uncertainty scripts and follow-up record are proposed operating practices.
Checked .
Define the unknown-answer route
Bring a question the agent should not answer alone and identify who can resolve it. That is the starting point for a useful fallback.
Discuss your workflow