Mistakes Are Normal. But Some Are Preventable.
AI receptionists today are competent conversationalists. They book appointments, answer FAQs, and transfer when needed. But set them up wrong, and you'll wonder why you bothered. Here are the seven mistakes that separate well-tuned agents from ones that frustrate callers and owners alike. Each one is fixable in under 10 minutes.
Mistake 1: Vague Greeting (The "Hello, How Can I Help?" Trap)
What it sounds like:
Caller: *[Call connects]*
Agent: "Hello, and welcome. How can I help you today?"
Caller: "Is this [Your Business]?"
Agent: "Yes, this is [Your Business]. How can I help?"
The caller repeats their question. The conversation starts from zero.
Why it happens: You use a generic greeting that doesn't set context. The agent answers, but the caller has no signal for what to expect.
The fix: Your greeting should name your business and hint at the most common reason people call.
Good greeting:
"Hi, thanks for calling [Your Business]. I'm [Name]. Are you calling about a new cleaning estimate, or is this about an existing appointment?"
Better for same-day urgency industries:
"You've reached [Your Business] plumbing emergency line. I'm [Name]. Are you calling about water damage, no heat, or something else?"
For service areas where qualification matters:
"Hi, this is [Your Business] lawn care. Before I help you, what's your neighborhood or ZIP code? I want to make sure we service your area."
The greeting takes 30 seconds instead of 10 seconds. In that extra 20 seconds, you've answered the caller's first question and moved the conversation forward.
Where to fix: System instructions, under "greeting" section. Update it today.
Mistake 2: No Fallback Path (The Loop)
What it sounds like:
Caller: "I need to speak to someone about a custom project."
Agent: "I can help with that. Tell me about your project."
Caller: "It's really complex. Can I talk to [owner]?"
Agent: "I can help with that. Tell me about your project."
*[Repeat 3 times]*
The AI has no "escalate" path. It keeps trying to solve something it cannot solve. The caller hangs up furious.
Why it happens: Escalation policy is set to "Never" or the agent doesn't recognize when it's out of its depth.
The fix: Set escalation policy to "Complex queries only" (the default) and make sure the agent knows a few keywords that trigger it:
- "Can I speak to [owner/manager/a person]?" → Transfer immediately
- "This is complex" or "It's complicated" → Transfer immediately
- "I don't think you can help" → Transfer immediately
When the caller explicitly asks for a person, transfer. Do not retry the same question.
Where to fix: Call rules → Escalation policy. Set to "Complex queries only" or "When requested." Add 3-5 trigger phrases to your system instructions under "Escalation Triggers."
Mistake 3: Wrong Voice for Your Brand
What it sounds like:
You run a high-end interior design firm. Your agent has the "casual, upbeat" voice. Clients expect professional formality and get a best-friend greeting.
Or: You run a neighborhood plumbing company. Your agent sounds corporate and distant. Customers expect warmth and get a financial advisor.
Why it happens: You didn't match voice to brand. You picked a voice you liked personally instead of one that matches how your customers expect you to sound.
The fix: Listen to all 9 available voices. For each one, ask:
- Does this sound like someone my customer expects to call?
- Does this sound like someone my customer would trust?
- Does this sound like someone from my industry?
Map voice to brand:
| Business Type | Right Voice Vibe |
|---|---|
| Law firm, accounting, real estate | Professional, confident (Jon, Ryan, Kevin) |
| Hair salon, retail, home services | Warm, approachable (Sarah, Ava, Lucy) |
| Plumbing, electrical, HVAC | Friendly, reliable (Jake, Ryan, Kevin) |
| Medical practice, therapy | Calm, professional (Jon, Ava, Ryan) |
| Luxury/boutique services | Sophisticated (Dominic, Ava, Lucy) |
Where to fix: Voice & Speech tab → Preview all 9 voices → Pick the one that sounds like your brand. You can change this instantly if you get it wrong.
Mistake 4: Poor Transfer Logic (Everything Goes, or Nothing Goes)
What it sounds like:
Scenario A: Everything transfers.
Caller: "What are your hours?"
Agent: "Let me get someone for you. Hold on."
Scenario B: Nothing transfers.
Caller: "My basement is flooding. I need help now."
Agent: "I don't have information about emergency water damage. Is there anything else I can help with?"
Both are wrong. One wastes your time. One loses you an emergency call.
Why it happens: You set transfer policy too broadly or too narrowly. No nuance.
The fix: Create three buckets of calls:
| Bucket | What Happens | Examples |
|---|---|---|
| AI handles end-to-end | No transfer needed. Agent answers and closes. | Hours, pricing ranges, service types, booking appointments, FAQ questions |
| AI captures, you callback | Agent takes details but doesn't transfer. You call customer during business hours. | Unusual requests, requests for specific staff, requests for custom quotes |
| Live transfer to you immediately | Agent connects caller directly. Zero wait. | "My heat is out," "I have no water," "This is an emergency," customer explicitly asks for person |
Set these buckets explicitly in your transfer rules, with trigger phrases for each.
Where to fix: Call rules → Configure routing rules by topic/keyword/urgency. Test by calling your own line with a fake emergency. Does it transfer? Good. Now call with a routine question. Does it book? Good.
Mistake 5: Hallucinated Pricing or Policy
What it sounds like:
Caller: "How much does a roof replacement cost?"
Agent: "Most roof replacements run between $3,000 and $6,000 depending on your home size."
Caller books appointment, meets you, you quote $12,000.
Caller feels misled.
Why it happens: You didn't give the agent specific guardrails. It made an educated guess based on your industry. The guess was too low or too high or just wrong for your business.
The fix: Add explicit pricing guardrails to your system instructions.
Good guardrail:
"If asked about [specific service] pricing, respond: 'Pricing depends on [specific factors like square footage, existing materials, complexity]. Most jobs range [give realistic range], but I'd recommend getting a detailed estimate from our team. Can I book a time for them to assess your situation?'"
Better guardrail:
"If asked for exact pricing, never quote specific numbers. Say: 'Every project is custom. Our team will provide a free estimate within 24 hours. Can I get your phone and best time to call?'"
The second option is safer because it doesn't require you to update the agent every time your pricing changes.
Where to fix: System instructions → Search for every mention of pricing. Replace vague language with specific guardrails.
Mistake 6: No Follow-up Logic (Call Captured, Lead Lost)
What it sounds like:
Agent captures lead: Name, phone, service.
Agent: "Great! Someone will call you back tomorrow."
Agent sends transcript to your inbox.
*[You get buried in work. Three days pass. Caller books someone else.]*
Why it happens: The agent captures the data but doesn't route it anywhere. It lands in your inbox as a transcript. You have to remember to call back.
The fix: Set up automated routing for captured leads:
| After Capturing a Lead | Send To |
|---|---|
| Urgent (emergency, angry caller) | SMS to your cell immediately |
| High-intent (booking request) | Calendar entry + SMS confirmation |
| Medium-intent (quote request) | Email to your inbox tagged "LEAD" |
| Low-intent (just asking questions) | Weekly digest email |
If your platform supports integrations, connect your CRM so leads auto-populate. If not, SMS notifications work (faster than email).
Where to fix: Integrations tab → Connect SMS or email. Configure notification rules: which calls trigger immediate SMS vs. which go to email digest.
Mistake 7: Set and Forget (No Tuning for 30 Days)
What it sounds like:
Month 1: Agent works fine.
Month 2: Three callers mention the same question the agent can't handle. You never see the transcripts. Agent repeats the same mistake 30 times.
Month 3: You finally review transcripts. 15 common questions the agent gets wrong.
Why it happens: You set up the agent, it works, and you stop paying attention. No feedback loop.
The fix: Review transcripts on a schedule:
| When | What to Do | Time |
|---|---|---|
| Week 1 | Daily - review every transcript. Look for patterns. | 15 min/day |
| Week 2-4 | 3x per week - spot-check transcripts. Update FAQ if a question repeats. | 10 min, 3x/week |
| Month 2+ | Weekly - skim 5-10 transcripts. Update knowledge base if patterns emerge. | 10 min/week |
When you spot a question the agent handles poorly:
- Write it down (don't rely on memory)
- Add an FAQ entry with the right answer
- Test by calling your own line with that question
- Confirm the agent now handles it correctly
One FAQ per week. One small improvement per week. After 4 weeks, the agent handles 20% more calls than when you launched.
Where to fix: Your calendar. Block 15 minutes on Friday afternoon for transcript review. Non-negotiable.
The Mistake Prevention Checklist
Before going live, verify these:
| Check | Status |
|---|---|
| Greeting includes business name + hints at primary reason people call | ☐ |
| Escalation policy is set to "Complex queries only" or "When requested," not "Never" | ☐ |
| Voice matches business brand (professional vs. casual, formal vs. warm) | ☐ |
| Transfer rules have 3+ specific trigger phrases or keywords | ☐ |
| All pricing statements include explicit guardrails or use "depends on..." language | ☐ |
| Captured leads route to SMS/email/CRM, not just a transcript | ☐ |
| Calendar reminder set for weekly transcript review | ☐ |
FAQ
If I make one of these mistakes, is the agent ruined?
No. Every mistake is fixable in 5-15 minutes. Update the setting, test it, done. The agent is learning from the updates.
How quickly should I fix a mistake after I spot it?
The same day, ideally. Or first thing next morning. Do not let it repeat for a week.
Should I tell callers that mistakes happened?
Only if they directly experienced it and are upset. For mistakes you discover in transcripts, just fix the agent and move on.
Which mistake is most common?
"Set and forget" (Mistake 7). Most operators launch, it works, and they stop paying attention. By week 4, they've missed tuning 20+ opportunities.
Bottom Line
All seven of these are preventable with 30 minutes of setup work. Start with Mistake 1 (greeting) and Mistake 7 (transcript review schedule). Those two alone will make your agent feel 100% more professional. Fix the others as you have time.
See how to set up an AI phone agent for the step-by-step. Review call transfers to understand transfer logic. Learn how it works for technical architecture. Check your pricing options and get started with a free trial. Read your first week to understand what tuning looks like in practice, or visit how to forward calls to begin.