⚠️ Important: Simply turning on the DTMF toggle does not activate the full flow.
To make it work, you must also update your system prompt using the correct DTMF signals as shown below.
| DTMF1010
8197800293
)“Can you please provide your phone number after the beep tone? | DTMF1010”If the input is invalid:
“That doesn’t seem like a valid phone number. Please enter a 10-digit phone number after the beep. | DTMF1010”
| DTMF0610
560033
)“Can you please provide your pin code after the beep tone? | DTMF0610”If the input is invalid:
“That doesn’t seem like a valid pin code. Please enter a 6-digit pin after the beep. | DTMF0610”
| DTMF[XXYY]
XX
= Expected number of digitsYY
= Time (in seconds) allowed for user inputDTMF1010
→ Expect 10 digits, allow 10 secondsDTMF0610
→ Expect 6 digits, allow 10 seconds⚠️ Tip: Always set theYY
duration based on the TTS utterance length.
If the message is long but the time is short, the input might timeout before the beep.
Tip | Why It Helps |
---|---|
Match time to utterance length | If the YY value (input time) is too short for your message, users won’t be able to respond in time. |
Don’t strip or reformat DTMF signals | They must remain at the end of the prompt exactly as written. |
Handle invalid input loops | Guide the user to retry if their input doesn’t match the expected format. |
Use clear instructions | Mention “after the beep” to guide user expectations and ensure input is captured. |
Enable barge-in (optional) | If you’re using TTS, enabling barge-in allows users to enter input without waiting for the entire prompt to finish. |
Validate inputs post-call | You can log or validate the collected digits after the call for reporting or verification workflows. |
Use in noisy environments | DTMF ensures input collection even when speech transcription is unreliable due to background noise. |