When should you use it?
- Callers mostly want to book, move or cancel
- You already have a scheduling database or CRM
- You prefer a hosted voice stack to building one
Not for: Calls that need clinical or legal judgment; Systems that cannot expose a narrow API
What do you need, and what do you get?
You need
- Voice platform account
- Phone number
- Your scheduling records behind a small server
You get
- A receptionist that can manage bookings
- Call logs tied to appointment changes
How does it work, step by step?
- Pick the voice platformUse a hosted service for speech and the conversation loop.
- Write the receptionist briefCover greeting, tone, what it may answer and when to hand off to a person.
- Expose only booking actionsHost a server with a short list of tools: look up openings, book, cancel.
- Connect the phone lineRoute a number to the agent through your telephony provider.
- Review calls weeklyListen to samples and check every booking against your calendar.
The prompt
Our own prompt, inspired by MitziMoto on Hacker News and written to work in ElevenLabs Agents and Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You are the phone receptionist for {business}.
Tools: list_openings, book, cancel.
Confirm the caller's name, phone number and requested time out loud before booking. If the request falls outside these tools or the caller is upset, offer a callback from staff. Never invent openings; always check with list_openings first.Inspired by MitziMoto on Hacker News: Hacker News comment on connecting a hosted voice agent to a CRM through MCP. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Exposing your whole CRM as tools invites mistakes; keep the tool list small.
- Callers give names and numbers inconsistently; confirm details before booking.
Our take
The useful clarification is the division of labor. The voice vendor handles hard real-time pieces; you own a small server that defines tools and rules. MitziMoto's breakdown is helpful because it shows how little you need to build yourself. The hosted voice service handles listening, reasoning and speaking, the telephony provider supplies the number, and your part is a system prompt plus a small server exposing a short list of booking tools such as look up openings, book and cancel. Keep that list short; exposing your whole CRM invites mistakes. Write the receptionist brief carefully, including when to hand off to a person. Callers give names and numbers inconsistently, so have the agent read details back before booking. Listen to a sample of calls each week and check every booking against your calendar. Calls that need clinical or legal judgment should always reach a human, and card details should never be taken on the call.
Where the time goes back: Routine booking calls are handled at any hour, and staff only take the calls that need a person.
FAQ
Why MCP here?
Is a phone number required?
Source and credit
Inspired by MitziMoto on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Hacker News comment on connecting a hosted voice agent to a CRM through MCP
- Creator
- MitziMoto on Hacker News
- Published on
- Hacker News
- Original date
- Sep 4, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- ElevenLabs Agents
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.