If your agent sounds like a robot, callers disengage fast. Some get nasty.
You'll see it in the transcripts: "Are you a robot? I want to talk to a f*cking human."
If your agent sounds like a robot, it defeats its main purpose.
The whole point of a voice agent, instead of an IVR menu or a web form, is that it sounds human. That's the only reason a caller stays on the line long enough to give you their name, their address, and their problem.
The moment they clock it as a machine, you've lost the advantage you paid for.
Human-sounding is not a nice-to-have. It is the product.
One main reason your agent sounds like a robot is the overuse of em dashes.
An em dash is this character: —
It's a long horizontal line, longer than a hyphen (-).
Text-to-speech voices usually treat an em dash as a pause. So when your prompt has too many em dashes, the voice agent does not just “read smoothly.” It pauses again and again.
That can make the caller feel like the agent is reading punctuation instead of having a conversation.
Check the demo below:
Why does this matter?
An em dash creates a noticeable break in speech.
That can be helpful when the agent is reading back important information, such as a phone number:
“5-5-5, 1-2-3-4 — right?”
The pause gives the caller a moment to check the number.
But the same pause sounds awkward in short everyday phrases, such as:
“Got it — Michael — how old is he?”
That sentence should sound quick and natural. The em dashes make it sound broken up and robotic.
Use em dashes when the pause helps the caller.
Use them for:
- reading back phone numbers, emails, or addresses.
- separating important information before a confirmation question.
- creating a pause the listener actually needs.
Avoid them for:
- short replies like “Got it”.
- simple name confirmations.
- normal conversation flow.
- style or decoration.
- places where a comma or period would sound more natural.
Other Articles on Voice AI.
- Call your Voice AI Agent a "receptionist," not an "assistant."
- Overusing Em Dashes Makes Voice Agents Sound Robotic.
- Use Contractions to make voice agents sound more natural.
- Avoid Using Tag Questions in Voice Agent Confirmations.
- Claude Beats ChatGPT for Voice AI Agents.
- How to A/B Test in Retell AI.
- Automated Alerts in Retell AI to Monitor Voice AI Operations.
- Custom Reporting For Voice AI - Mini-Course.
- CRMs like GHL are overkill for building Voice AI Agents.
- How To Bill Your Voice AI Clients Like A Pro.
- Voice AI Knowledge Base Creation Best Practices.
- How to build Cost Efficient Voice AI Agent.
- When to Add Booking Functionality to Your Voice AI Agent.
- Without IP your AI company is worth nothing.
- AI Automation Agency Pricing Rules.
- How to Prevent Toll Fraud in Retell AI.
- Voice AI - Build once → Sell many → Collect monthly forever.
- State Machine Architectures for Voice AI Agents.
- Missing Context Breaks AI Agent Development.
- Avoid the Overengineering Trap in AI Automation Development.
- Retell Conversation Flow Agents - Best Agent Type for Voice AI?
- How To Avoid Billing Disputes With AI Automation Clients.
- Don't 'Build' AI Automation Workflows, 'Code' Them.
- Critical Aspect of Prompt Engineering - Domain Parameters.
- Zero Shot vs Single Shot vs Multi Shot Prompting.
- How to Build Reliable AI Workflows.
- Stop Building AI You Can't Fix.
- Automating 100% of your workflows is a disaster waiting to happen.
- How to build Voice AI Agent that handles interruptions.
- AI Automation Without CRM Is Useless for Business Growth.
- Structured Data in Voice AI: Stop Commas From Being Read Out Loud.
- Why Your Voice AI Sounds Robotic and How to Fix It.
- Why You Need an AI Stack (Not Just ChatGPT).
- AI Default Assumptions: The Hidden Risk in Prompts.
- Vibe Coding Fails Without Context and Expertise.
- How to make your Voice AI Agent Date & Time Aware.
- Why AI Agents lie and don't follow your instructions.
- How to Write Safer Rules for AI Agents.
- Two-way syncs in automation workflows can be dangerous.
- Using Twilio with Retell AI via SIP Trunking for Voice AI Agents.