Six Principles of Voice Design: Designing for the Ear and Encoding It into Agent Script

“Hello? Are you still there?” asks the caller in the first audio example below, after four seconds of silence from a voice agent. Each of the six voice design principles here comes with audible before-and-after examples like that one, plus the Agent Script that encodes the fix. Press play as you read. The voice channel has long occupied an awkward position in the enterprise stack: perpetually promising, rarely delivering. Voice AI struggled mostly because the technology fell short of consumer expectations, with poor natural language understanding, no contextual memory, and fragile multi-turn handling. Large (and small) language models have gone a long way toward overcoming these limitations. Enterprise voice AI adoption is now an operational reality for a growing share of the market,[1] and it’s coming for most of the rest. Technology will keep improving, and those improvements will keep mattering for user experience and business value, but technology is no longer the bottleneck. The biggest challenge now is designing the user interface. Designing for the ear is fundamentally different from designing for the eye. You can’t lift a chatbot onto a phone line and call it a voice agent. Voice users behave differently. They are more sensitive to latency.…