Hi! Native DTMF support should be a core capability of our AI agent This is what bridges the gap between modern automation and the legacy infrastructure that still runs the business world.

Relying on middleware or third-party workarounds to send tones introduces latency, complexity, and failure points. All of which undermine the simplicity and reliability clients expect from our AI and costs us more as Agencies to employ- I've kept my AI's 100% native, until now because without this I'm forced to use an integrator.

In practical terms, DTMF isn’t a “nice-to-have”; it’s the difference between an agent that talks and one that acts. It enables fully autonomous call handling... transfers, confirmations, and menu navigation without breaking the flow or the illusion of competence.

If the AI agent is to be trusted in professional environments, especially where multiple departments or legacy phone systems are in play, native DTMF is non-negotiable.

Even so much as a .wave file that plays the tones based on user input would be sufficient...

Thanks