AI Receptionist That Answers Real Phone Calls
Key topics
What might be interesting to HN:
Conversation loop: telephony → streaming ASR → LLM tools → calendar/email → TTS, with turn‑taking and barge‑in control. Calendar booking: buffer‑time logic + double‑booking prevention; we expose a minimal function API for “OfferSlots/BookSlot/Confirm.” Multi‑channel capture: unify phone, email, and form leads into one record with transcript + fields (name, date, guest count, budget). Spam filtering: block patterns (e.g., 1‑800s / robocalls) before they hit staff; safe pass‑through rules for VIPs. Evaluation harness: scripted call scenarios (availability, pricing, policy) → check for grounding (answers must be in your docs) → score for correctness, safety, and escalation timing.
What didn’t work:
Over‑eager answers before knowledge ingestion; we now hard‑gate answers on verified sources and otherwise take a message or escalate. Elevenlabs; Latency is way too much to build a human like experience. Confusion on edge cases (“What’s your cancellation policy if…”). We added doc‑first retrieval + fallback to “collect info + route.”
Numbers so far (early, only 6 customers and improving):
Target answer time: sub‑second pickup; 5‑minute first reply on email. Reduction in missed calls and faster tour scheduling are the main wins; happy to share more once data matures.
Privacy/ethics:
Customer content is not used to train our models. Clear consent and recording policies; PII is encrypted at rest and in transit. What I’d love feedback on:
Better offline evaluation for voice agents (beyond happy‑path scripts). Turn‑taking and barge‑in strategies you’ve found to work well. Failure‑mode handling you’d want before trusting an AI with calls.
Link: https://mikla.ai
The post introduces an AI receptionist that handles real phone calls, captures leads, and books appointments, with a focus on wedding venues, and seeks feedback on its development and potential improvements.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
18m
Peak period
3
0-6h
Avg / period
2
Key moments
- 01Story posted
Oct 10, 2025 at 1:52 PM EDT
3 months ago
Step 01 - 02First comment
Oct 10, 2025 at 2:10 PM EDT
18m after posting
Step 02 - 03Peak activity
3 comments in 0-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 13, 2025 at 9:05 AM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.