Workflows and DTMF
# support
a
I have a workflow that's asking the user to press either 7 or 9 and based on what they pressed, it transfers the call to diffent numbers. There are several issues: 1. The key is never detected, eventhough the WF has a DTMF tool attached. 2. I don't see all of the usual settings that an agent has and based on the API doesn't seem like I can configure them, is that correct? It has office background and I don't want that. 3. I need to set a specific end-of-call webhook but it uses the generai org one - NOT desired 4. end-of-call-report doesn't have transcript so I can't troubleshoot of it ever saw the key press "transcript": "", Call ID: a52e8182-04cd-404c-b721-dbd13a5ee460 Thanks for the support.
v
DTMF detection in Vapi workflows can fail if the IVR expects out-of-band (RFC 2833) tones, since Vapi's DTMF tool uses in-band audio. As a workaround, if the IVR supports speech input, configure your workflow to have the assistant say the option (e.g., "Sales" or "Press 7") instead of sending a DTMF tone. This increases compatibility with more IVR systems and can help bypass DTMF detection issues. Example: > Instead of prompting "Press 7 for support," have the assistant say "Support" if the IVR allows speech input. If you need more help with workflow-specific settings or webhooks, please clarify which setting is most urgent. Source: - [Vapi Default Tools Documentation](https://docs.vapi.ai/tools/default-tools)
DTMF detection in Vapi workflows can fail if the IVR expects out-of-band (RFC 2833) tones, since Vapi's DTMF tool uses in-band audio. As a workaround, if the IVR supports speech input, configure your workflow to have the assistant say the option (e.g., "Sales" or "Press 7") instead of sending a DTMF tone. This increases compatibility with more IVR systems and can help bypass DTMF detection issues. Example: > Instead of prompting "Press 7 for support," have the assistant say "Support" if the IVR allows speech input. If you need more help with workflow-specific settings or webhooks, please clarify which setting is most urgent. Source: - [Vapi Default Tools Documentation](https://docs.vapi.ai/tools/default-tools)
c
Hi alexrb1, Ensure DTMF detection is properly configured in the node settings, check UI permissions to customize agent settings, and verify your end-of-call webhook URL is correctly set up in the server properties..
a
@Kings_big💫 This is using the new workflows process. In there, there isn't the same ability as you have for the agent. Looking at the API, it also doesn't show the same ability to configure parts that one would think they should be in common with an agent; ie: ability to have an mp4 as the initial welcome message. Maybe I'm not setting up my workflow correctly, but I read and followed all into available on the new WF and it seems like there's a lot of configuration ability missing vs an agent. Is there something else I should be looking at?
c
Set DTMF in the workflow node, configure the MP4 welcome message in the Assistant settings, and verify the end-of-call webhook in Server Settings advanced features must be managed through the Assistant, not the workflow UI.
a
I'm failing to understand how Assistant works together with Workflows. My impression is that it is one or the other. Any docs or YT showing how they work together and how to set up? I can get assistant to work, just not workflows.
k
Workflows control the call flow using Conversation nodes, while Assistants handle AI behavior and tools..
a
@Sahil FYI.. here's the support issue and here's the last call we looked at: a52e8182-04cd-404c-b721-dbd13a5ee460 Thanks for the help.
s
Thanks
c
Reported it to the team about DTMF not working in workflow. For now, please use assistant as discussed during OH.
4 Views