Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer Based on the available sources, the press_digit tool accepts a digit parameter with specific enum values: "0", "1", "2", "3", "4", "5", "6", "7", "8", "9", "*", "#" [(1) ]() . There's no mention of support for Twilio-standard w (0.5s) or W (1s) pause characters in the digit_to_press string . The sources indicate that Retell does not support post-dial DTMF sequences with comma-separated syntax (like +1XXXXXXXXXX,1234#) [(2) ]() . This suggests that timing control characters like w and W are also not supported in the current implementation. For precise timing control over DTMF gaps, the available sources don't document a built-in solution. The press_digit tool appears to send individual digits without explicit pause control mechanisms [(1) ]() . If you need precise inter-digit timing, you might need to implement sequential press_digit calls with delays managed at your application level, though this isn't explicitly documented in the available sources.

​ To learn more, see the sources I considered: [[1] Press_digit Always Returns success: false - DTMF Never Works](https://discord.com/channels/1186424376300679209/1466107615812522189) [[2] Post-dial DTMF support with comma separated syntax](https://discord.com/channels/1186424376300679209/1459209466879934495) ​

Appreciate the feedback! Feel free to ask me again with additional guidance or context.