DTMF Tool Improvements
Sedrick Pires
Im experiencing a technical problem with our outbound calling agent's ability to navigate IVR systems. While using Vapi's built-in DTMF functionality, the system logs indicate successful function calls with the correct digits, but many IVR systems fail to detect these inputs. This issue has been observed across multiple IVR systems, though it functions correctly with some.
Affected Call IDs
dde63818-b547-41eb-bfd3-9e587cddd2ab
df13e533-4b27-4cd7-9c07-54e7f61a807f
ea0db2d8-a59f-4ae9-9b50-d49116efc056
1f5dd938-b0e6-40f2-b549-d9a6280a3606
Kyle Holgate
This is a hard-requirement for me to be able to continue to build on VAPI
Canny AI
Merged in a post:
IVR Navigation and DTMF Support
H
Hugo Podworski
Vapi's current DTMF solution is essentially deprecated. And for me this feature is pretty important. In my experience Retell handles DTMF/IVR side of things really well, however I overall prefer Vapi's experience and would love this feature here :)
P
Parth Shah
+1
I am facing these issues too. I am currently using a Twilio number. I can see in the call logs that the assistant presses the correct key using the dtmf function, but it is not always recognised by the IVR on the other side. My guess is that this is because how the Twilio dtmf is setup - rfc 2833 vs inband