惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

爱范儿
爱范儿
量子位
人人都是产品经理
人人都是产品经理
小众软件
小众软件
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - Franky
Recent Announcements
Recent Announcements
A
About on SuperTechFans
Microsoft Security Blog
Microsoft Security Blog
N
Netflix TechBlog - Medium
H
Help Net Security
博客园 - 三生石上(FineUI控件)
博客园 - 司徒正美
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
MyScale Blog
MyScale Blog
The Cloudflare Blog
S
SegmentFault 最新的问题
H
Hackread – Cybersecurity News, Data Breaches, AI and More
J
Java Code Geeks
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
P
Proofpoint News Feed
宝玉的分享
宝玉的分享
Vercel News
Vercel News

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
We Built an AI Receptionist. The Hard Part Wasn't Making ...
Syed Noor · 2026-06-28 · via DEV Community

Syed Noor

It's 8:40 on a Tuesday evening. A dental clinic is closed, the front desk is dark, and the phone rings. A new patient wants to book a cleaning. Normally that call dies in voicemail, and the patient calls the next clinic on the list.

We wanted to see what would happen if something picked up instead. So we built one — an AI that answers the phone, has a real conversation, and books the appointment. We named her Ava.

Going in, we assumed the challenge would be making her sound human. That turned out to be the easy part. The hard parts were the ones nobody puts in the demo video.

Sounding human is basically a solved problem now

A few years ago, the giveaway was the voice — flat, robotic, obviously a machine. That's over. The voice we gave Ava is warm and natural enough that most people don't clock it as AI in the first few seconds.

So, if you're judging these tools by how human they sound, you're judging the wrong thing. The voice is table stakes. What actually breaks is everything underneath it.

The first thing that broke was listening, not talking

Our earliest version sounded great and understood almost nothing once a real person talked to it.

Real speech is messy. People trail off, restart, talk over the agent, and — in our case — speak with an accent the system kept mishearing. It would confidently grab half a sentence, decide the person was done, and answer the wrong thing. Cue the dreaded "sorry, can you repeat that?" loop that makes you want to mash zero for a human.

Fixing that meant changing how it listens — a different speech engine and teaching it to wait a beat longer before assuming you've finished. Unglamorous, but it's the difference between a demo and something a real customer could stand to use.

Then came the silence problem

Here's a strange thing we learned: on a phone call, silence reads as "broken."

When Ava paused even a second to think, it felt like the line had dropped. In a text chat nobody minds a short delay. On a call, your brain immediately assumes something's wrong. We had to design around that — keep her quick and have her say a natural "one sec while I pull that up" instead of going quiet. A small detail, a huge difference in whether the call feels alive.

The real lesson: the danger isn't a robot voice. It's a confident mistake.

This is the part I'd want every business owner to understand before they put any AI on their phone line.

The scary failure for a phone agent isn't sounding stiff. It's sounding great while doing the wrong thing — booking the wrong day, promising a discount that doesn't exist, confidently giving a wrong answer. A bot that bluffs is worse than no bot, because it does the damage in your name, to your customer, when you're not there to catch it.

So, the most important work we did wasn't making Ava smarter. It was teaching her restraint:

  • She reads the appointment back and waits for a clear "yes" before she books anything.
  • When she doesn't actually know something, she says a person will follow up — she doesn't guess.
  • The moment a call is beyond her, or someone just wants a human, she hands it over.

None of that shows up in a flashy demo. All of it is what makes the thing trustworthy enough to actually leave running.

"Knowing when not to act" is the whole game

If there's one idea I've taken from building this, it's that the value of an AI agent isn't how much it can do on its own. It's how reliably it knows the edge of what it should do — and stops there.

That's true for a phone receptionist, and it's just as true for any AI you'd let near your customers, your money, or your calendar. Speed and a nice voice get you in the door. Knowing its limits is what lets you trust it. We'd rather ship something that says "let me get a human" a little too often than something that fakes its way through and books a
mess you find out about on Monday.

You can hear it for yourself

Reading about a voice is a bit pointless, so we made it public. We set Ava up as the receptionist for a made-up clinic ("Brightside Dental") and put her behind a link you can open in your browser — click, talk, ask her to book a cleaning, and try your best to trip her up.

It's here if you're curious: talk to Ava.

We build these for real businesses too — but honestly, the demo makes the point better than we can. Go say hi, and hear what a front desk that never sleeps actually sounds like.