Silence and interruption handling
The AI voice agent manages two common situations that interrupt normal conversation: when the caller goes quiet and when the caller speaks while the agent is still talking. This article explains how the agent behaves in each case, what safeguards prevent unintended actions, and how to interpret these behaviors when reviewing call logs.
Audience: Center managers and AI Receptionist administrators who review call outcomes and troubleshoot unexpected call endings or incomplete flows.
On this page
- Before you begin
- How the agent handles silence
- How the agent handles interruptions
- Safeguards against unintended actions
- How calls end after extended silence
- Diagnosing silence and interruption issues
- Tips
- Related articles
Before you begin
- You need access to the AI Receptionist dashboard to review call logs and post-call summaries.
- Familiarity with how call transfer is configured at your center helps when interpreting call endings. See Call admission for background.
- The behaviors described in this article apply to all inbound AI voice agent calls. They cannot be individually disabled or adjusted per call.
How the agent handles silence
When a caller stops speaking during a conversation, the AI voice agent waits before taking action. After seven seconds of silence, the agent prompts the caller to re-engage — for example, by asking whether they are still there or by restating the last question.
The agent repeats this prompt up to five times across the call. Each prompt gives the caller another opportunity to continue the conversation.
Note: The seven-second wait and the five-prompt maximum are system-level defaults applied uniformly across all calls.
When the caller was not heard
If the caller spoke but the agent did not register what they said — for example, because of background noise or a brief connection issue — the agent apologizes and asks the caller to repeat themselves. In this situation, the agent does not ask whether the caller is still on the line. The distinction matters: the agent responds to what actually happened (speech that was not captured) rather than treating the caller as unresponsive.
How the agent handles interruptions
A caller can speak at any time, including while the agent is in the middle of a response. When the agent detects that the caller has started speaking, it stops immediately. The caller's input is then processed as the next turn in the conversation.
This means callers do not need to wait for the agent to finish before they can respond, correct a misunderstanding, or ask a different question.
Safeguards against unintended actions
Silence is never treated as agreement or consent. The agent will not book, cancel, reschedule, or charge for an appointment based on a caller who has gone quiet. Any action that affects an appointment — including creating a booking, processing a cancellation, or collecting payment — requires the caller to give an affirmative spoken response.
This safeguard applies regardless of how many silence prompts have been issued. Even after multiple prompts have gone unanswered, the agent ends the call without taking any appointment action.
Important: If you see a call in the call log where an appointment was created or changed, the guest confirmed the action verbally during the call. Silence alone cannot trigger these outcomes.
How calls end after extended silence
After the agent has issued its final silence prompt and received no response, the call ends in one of two ways:
- If call transfer to a human is configured and available: The agent transfers the call to the designated number before ending. The caller is connected to a staff member who can continue the conversation.
- If call transfer is not configured, or is unavailable at that time: The call ends. The agent does not leave the call open indefinitely.
The outcome is recorded in the call log. You can review the post-call summary for details about how the call ended and at what point silence occurred.
Tip: If you find that calls from engaged guests are ending unexpectedly, check whether your call transfer settings are configured. See Call admission.
Diagnosing silence and interruption issues
Use the following symptom-based guide to identify and resolve common issues related to silence and interruption handling.
The call ended but the guest says they were actively trying to speak
Likely cause: The caller's audio was not reaching the agent — for example, the caller was on mute, speaking too quietly, or experiencing a connection issue on their end.
Resolution:
- Open the call log in the dashboard and select the affected call.
- Review the transcript to confirm whether any caller speech was captured during the call.
- If no caller speech appears in the transcript after the greeting, the issue is likely on the caller's end (muted device, poor connection).
- If the transcript shows silence prompts followed by call end, the agent behaved as designed.
- Ask the guest to call back from a different device or a location with a stronger signal, if the issue recurs.
The agent asked whether the caller was still there, but the caller says they were speaking clearly
Likely cause: The agent detected silence rather than speech — often caused by the caller pausing between sentences or by audio dropping momentarily on the caller's network.
Resolution:
- Review the call transcript to find the point where the silence prompt was issued.
- Check whether any audio was recorded before the prompt. If audio is present in the recording but absent in the transcript, the speech may not have been processed.
- If this pattern recurs across multiple calls, review the call log for common times of day or center locations where it appears.
- If the issue affects many calls, contact Zenoti Support with the affected call details so the audio quality can be investigated.
The agent apologized and asked the guest to repeat themselves, but the guest expected a different response
Likely cause: The agent received audio it could not interpret — this is the correct behavior when speech is detected but not understood. The agent apologizes and asks for repetition rather than asking whether the caller is still present.
Resolution:
- Confirm in the call transcript that the agent received audio at this point. If audio is present and the agent still asked for repetition, the behavior is working as designed.
- If the guest finds repeated requests to repeat themselves frustrating, consider whether background noise at the guest's location may be interfering. There is no configuration to change this behavior.
A call ended without any appointment action, but the guest expected a booking to be confirmed
Likely cause: The guest did not confirm the booking verbally before the call ended. This may happen if the guest went silent at the confirmation step, or if there was a connection issue that prevented the confirmation from being heard.
Resolution:
- Review the post-call summary to see the last point in the booking flow that was completed before the call ended.
- Check whether a silence prompt sequence occurred at the confirmation step.
- If the call ended due to silence at confirmation, the safeguard against silent agreement prevented the booking from being created. This is the intended behavior.
- Advise the guest to call back to complete the booking. The AI voice agent will restart the booking flow from the service selection step.
After a long silence, the call transferred to a staff member who was unaware of the context
Likely cause: The call transfer occurred after the final silence prompt went unanswered. The guest may have reconnected as the transfer happened.
Resolution:
- Review the call log to confirm the sequence: silence prompts issued, then call transfer triggered.
- The post-call summary records the call outcome and the point at which the transfer occurred.
- The receiving staff member can use the call note in the dashboard to understand what the caller was attempting before the transfer.
- If call transfer to a human is not configured and you want it enabled, see Call admission.
Tips
- Review the post-call summary after any unexpected call ending. The summary records the call outcome and the intent the agent detected. Calls that ended due to silence appear with an incomplete intent in the call log.
- Check the transcript when a guest reports a problem. The transcript shows each turn of the conversation, including the silence prompts the agent issued. This is the most reliable way to confirm what happened during a call.
- Configure call transfer so extended-silence calls reach a staff member. Without a call transfer number, calls that exhaust all silence prompts end without any human follow-up. Setting up call transfer ensures the guest reaches someone who can help.
- Advise guests to call from a quiet environment when possible. Background noise can interfere with how the agent processes speech. If guests frequently need to repeat themselves, noise at their end is a common factor.
- Distinguish between "not heard" and "not responded." The agent uses different prompts for each situation. If the transcript shows an apology and a request to repeat, the agent received audio it could not interpret. If the transcript shows a re-engagement prompt ("Are you still there?" or similar), the agent detected no audio at all.