Let a voice receptionist schedule appointments via MCP
We use a Twilio integration to make it work over a real phone line, but it could just as well be an app or websocket connection in a browser.Voice transport medium aside, the actual use case is not quite what you described.Companies like Eleven Labs and Vapi provide a full end to end voice agent platform. Task: We use a Twilio integration to make it work over a real phone line, but it could just as well be an app or websocket connection in a browser.Voice transport medium aside, the actual use case is not quite what you described.Companies like Eleven Labs and Vapi provide a full end to end voice agent platform. They handle the STT -> LLM -> TTS pipeline and infrastructure for voice agents. Think of a customer talking to a virtual receptionist to schedule an appointment.On the ElevenLabs platform, you provide them a system prompt (or an entire workflow/graph of system prompts) that instruct the voice agent on how to talk to the customer, tone, guardrails, how to answer specific questions, etc.At some point we need that LLM agent, running on an infrastructure we don't control, to talk to our "CRM" (for simplicity sake). Enter MCP.The MCP server we build and host supplies the "tools", like list_appointments, schedule_appointment, cancel_appointment-- whatever they may be.When eleven Labs voice agent connects, it sees all the tools available and can use them per the instructions in the system prompt.; tools: custom-built or unnamed agent. Human role: The original post does not say how a person stayed involved.; limitations: Prerequisites include access to a voice agent platform and a CRM system. Integration uncertainty exists regarding security handling, though comments suggest authenticating via phone start and passing session credentials. The source is a forum discussion, not a verified case study, so reliability is secondary. Human approvals are not mentioned..
Tools
custom-built or unnamed agent
Published on Agent Work Atlas:
Overview
We use a Twilio integration to make it work over a real phone line, but it could just as well be an app or websocket connection in a browser.Voice transport medium aside, the actual use case is not quite what you described.Companies like Eleven Labs and Vapi provide a full end to end voice agent platform.
Workflow
We use a Twilio integration to make it work over a real phone line, but it could just as well be an app or websocket connection in a browser.Voice transport medium aside, the actual use case is not quite what you described.Companies like Eleven Labs and Vapi provide a full end to end voice agent platform. They handle the STT -> LLM -> TTS pipeline and infrastructure for voice agents. Think of a customer talking to a virtual receptionist to schedule an appointment.On the ElevenLabs platform, you provide them a system prompt (or an entire workflow/graph of system prompts) that instruct the voice agent on how to talk to the customer, tone, guardrails, how to answer specific questions, etc.At some point we need that LLM agent, running on an infrastructure we don't control, to talk to our "CRM" (for simplicity sake). Enter MCP.The MCP server we build and host supplies the "tools", like list_appointments, schedule_appointment, cancel_appointment-- whatever they may be.When eleven Labs voice agent connects, it sees all the tools available and can use them per the instructions in the system prompt.
Reported result
The source does not report measured outcomes, success rates, or specific business impacts. It describes the architectural intent rather than executed results. Proposed acceptance check: Verify that the voice agent successfully retrieves and books an appointment via the MCP server in a controlled test environment.
Human role
The original post does not say how a person stayed involved.
Limitations
Prerequisites include access to a voice agent platform and a CRM system. Integration uncertainty exists regarding security handling, though comments suggest authenticating via phone start and passing session credentials. The source is a forum discussion, not a verified case study, so reliability is secondary. Human approvals are not mentioned.
Try it
I want to build a voice receptionist prototype using Eleven Labs and a custom MCP server. My business context is [replaceable: e.g., dental clinic scheduling]. I have a CRM with appointment data. Please guide me through setting up an MCP server that exposes tools: list_appointments, schedule_appointment, and cancel_appointment. Then, help me configure the Eleven Labs agent with a system prompt that uses these tools to book appointments over a phone line via Twilio. First, perform a dry run with a sample user request to verify the tool calls work correctly. Show me the logs and the resulting appointment record. Do not deploy to production or make real calls until I confirm the dry run is successful. If any inputs are missing, ask me for clarification before proceeding.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.