Preben
10/04/2025, 7:40 PMcheck_availability
- book_appointment
- cancel_appointment
- send_text_tool
- Previously dtmf_tool (for phone number input)
- Model: GPT-5
- Voice provider: ElevenLabs
- Transcriber: Deepgram
---
Prompt (short version):
> Collect and confirm date/time → then collect and confirm phone number → complete booking or cancellation → send SMS confirmation.
>
>
> After digits are entered and tool completes, the assistant should confirm the number aloud and continue.
>
The call goes like this:
- Assistant recognizes digits correctly.
- When dtmf_tool completes, assistant is just silent. Then II need to speak, and it sometimes repeats the number confirmation endlessly in a loop.
- If I add a tool.completed message, assistant most often just hangs up after confirming the number. But sometimes before entering the number (very unreliable)
What is happening?? It works perfectly in chat mode. This is very frustrating as I cant deliver my projects to my customers using Vapi.
I love Vapi, but this issue is killing me.
@Shubham Bajaj please take a look this.
Related issue: https://discord.com/channels/1211482211119796234/1377398718847910000Chiranjeet Mishra
10/04/2025, 7:40 PMVapi Support Bot
10/04/2025, 7:41 PM" ") to stay silent and avoid overlapping or premature speech. This helps prevent the assistant from hanging or looping after DTMF entry in voice calls.
json
{
"reply": " "
}
Try adding this silent reply immediately after the DTMF tool completes, before prompting for confirmation. This approach is recommended for reliable IVR/DTMF flows in Vapi voice calls according to the documentation.
Source:
- [IVR Navigation Guide](https://docs.vapi.ai/ivr-navigation)Preben
10/05/2025, 10:45 AMPreben
10/05/2025, 6:27 PMChiranjeet Mishra
10/06/2025, 8:18 PMw for a 0.5s pause and W for a 1s pause between digits. Example: 1w2w3W4# for Twilio, Telnyx, Vapi Numbers, and BYOK SIP.
2. Wait for Menus to Finish: Ensure your assistant waits until all options are spoken before sending DTMF sequences. Use a single space character (" ") to remain silent during these pauses.
3. Retry with Slower Inputs: If initial attempts fail, try sending digits more slowly. Start with fast (123#), then medium (1w2w3# with 0.5s gaps), and slow (1W2W3# with 1s gaps) retries. If required, use spoken input as a fallback.
For detailed guidance, please refer to the [IVR Navigation documentation](https://docs.vapi.ai/ivr-navigation).
If there are any more specific issues or configurations you need assistance with, feel free to ask.Operations📟
10/15/2025, 2:22 PMChiranjeet Mishra
10/16/2025, 8:15 PMw = 0.5 second pause
- W = 1 second pause
- Example: To enter "1234#" with pauses, write it as 1w2w3W4#
- This helps ensure the IVR system registers each digit correctly
2. Waiting for Menu Options:
- Let the IVR finish speaking all options before responding
- Use a single space " " as your assistant's response to stay silent
- This prevents the assistant from talking over the IVR menu
3. Progressive Retry Strategy: If the IVR doesn't recognize the input, try these approaches in order:
First try: 123# (no pauses)Second try: 1w2w3# (0.5s pauses)Third try: 1W2W3# (1s pauses)Last resort: Speak the option out loud
This approach helps ensure reliable navigation through phone menu systems by adapting to different IVR timing requirements.Preben
10/24/2025, 3:40 PMChiranjeet Mishra
10/28/2025, 7:18 PM