Provisional review. Reception launched September 16, 2026, and this assessment draws on ElevenLabs’ public product pages, documentation, and launch coverage. No hands-on testing, no independent customer reviews. Treat the ratings as preliminary.
ElevenLabs launched Reception on September 16, 2026. It is an AI phone receptionist for small and medium businesses, built on the company’s ElevenAgents platform and sold through Reception.ai. You scan your website, choose a voice, configure the receptionist, and receive a phone number. ElevenLabs says a business can be taking calls in under five minutes.
Once configured, Reception answers inbound calls in more than 70 languages, books and reschedules appointments, takes messages, and keeps client interaction history in a dashboard. A business assistant handles the administrative side.
Who this is built for matters more than usual. Reception targets salons, plumbers, legal offices, real-estate firms, restaurants, and other appointment-driven local and professional-service operators. The clearest B2B overlap is professional services: the two-partner consultancy, the small law firm, the managed-service provider where one missed inbound call is one missed project. It is built to cover a small firm’s phone, not to sit inside a revenue-operations stack. If you run demand generation at a software company with staffed SDRs and mature inbound routing, this is the wrong tool.
What It Does Well
Onboarding is the product. Most voice-agent platforms open with a flow builder, prompt configuration, and telephony setup. Reception opens by scanning your website for services, hours, team information, and locations, then lets you refine voice, rules, language, and call behavior. For a firm with no operations hire, that gap decides whether the tool goes live or stalls in configuration.
Staff-first routing preserves human coverage. You can set staff-first answering during chosen hours. The staff phone rings first, and if nobody answers within a ring window you select between 5 and 60 seconds, the AI receptionist takes over. Outside those hours it answers directly. That suits overflow coverage at firms where a partner still needs to take the high-context calls personally.
The dashboard assistant confirms before it writes. Ask it to create, update, or delete anything and it displays the intended change, then waits for approval. Batch tasks such as cancelling a day of appointments show the complete list first. Assistant usage caps at 150 messages a day on Basic, 300 on Plus, and 500 on Premium.
How Each Role Puts It to Work
- Operations. Reception works as a configured front desk: business hours, staff availability, service definitions, routing rules, messages, transfers, and scheduling all administered in one system. Monday morning, replace the after-hours voicemail box with a receptionist that captures the caller’s details, identifies the reason for the call, takes a prioritized message, or offers an open slot. With technical support on hand, webhooks expose your own HTTP endpoints as tools the receptionist calls mid-conversation, so it can check service-area eligibility, look up a customer record, or open a ticket while the caller is still on the line.
- Salesperson. At a firm with no SDR function, this is inbound lead capture. Configure the receptionist to ask about project scope, timeline, service needs, and budget range, then offer qualified callers a discovery-call slot instead of a voicemail you return on Wednesday. Reception has no documented first-party CRM integration. Its Zapier documentation does cite creating a HubSpot or Salesforce contact during a conversation, but Zapier entitlement is inconsistent across ElevenLabs’ public materials, so confirm it on your intended plan before it becomes part of lead routing.
- Weaker fits: Marketing, Finance, HR, and Research. Transcripts surface real customer language, but inbound service calls replace neither message testing nor win-loss work; the analytics count calls, bookings, and client growth rather than anything a finance leader would take to a board; and nothing here touches hiring.
Where It Could Be Better
The entry tier has a usage cliff. Basic costs $29 a month and includes 75 credits, and a phone call burns one credit per minute. Spread evenly, that is about 2.5 call minutes a day. Overage runs $0.45 per credit, so a business using 275 phone minutes in a month adds $90 in overage for a $119 total before taxes and fees. Basic also supports one phone number and one concurrent call, which means the second caller during a busy hour gets nothing. Plus at $79 includes 275 credits, three phone numbers, and three concurrent calls. For a working service business, that is the realistic starting point.
The integration documentation contradicts itself, and this is the issue to settle before you buy:
- The public pricing page lists Zapier on Basic, and Zapier plus webhooks on Plus and Premium.
- The pricing documentation table lists Zapier, webhooks, and MCP across all tiers, Basic included.
- The Zapier documentation says Zapier requires Plus or higher.
- The webhook documentation says webhooks require Basic or higher.
Those cannot all be true. Get the entitlements in writing before you select Basic or design a workflow that depends on an integration.
Calendar support is Google-centric. The product page and documentation identify Google Calendar and an internal calendar, with no documented Microsoft Outlook or Microsoft 365 support. That excludes a large share of professional-services firms unless they are willing to run Google Calendar alongside everything else.
Number portability deserves scrutiny. Cancel, and service continues through the billing period, after which the assigned number is released following a 14-day grace period. ElevenLabs cautions that resubscribing may get you a different number. Do not treat a Reception-provisioned number as your primary business line until you have confirmed porting options.
Why Not Just Use ChatGPT, Gemini, or Claude?
General-purpose assistants do not provide what Reception packages: a provisioned phone number, inbound telephony, receptionist behavior, calendar scheduling, booking pages, client records, recordings, transcripts, and a business dashboard. This is a narrow voice-and-scheduling application built on ElevenAgents, not a chat wrapper.
The comparison that matters is against other voice-agent platforms and human answering services. Developer-oriented platforms such as Vapi and Retell give you finer control over prompts, workflows, telephony, and data models, at the cost of technical setup and ongoing ownership. A human service still wins on judgment, empathy, and the unusual call, and loses on recurring cost and 3 a.m. coverage. Reception sits between them and sells speed of setup.
Security & Compliance
ElevenLabs states that ElevenAgents is ISO 27001 and ISO 42001 certified and complies with applicable privacy regulations including CCPA. Calls handled by the receptionist are stored with recordings, transcripts, metadata, and outcome summaries.
Reception does not currently support HIPAA compliance, according to its own FAQ. ElevenLabs directs customers handling protected health information to the broader ElevenAgents offering, which it says may support HIPAA requirements for eligible accounts through a Business Associate Agreement. That sits awkwardly next to Reception’s healthcare-adjacent positioning. Do not deploy the self-serve product for patient intake or any PHI-bearing workflow without written confirmation of product scope, contractual terms, and safeguards.
Still unverified for Reception’s self-serve tiers:
- Whether ElevenLabs’ SOC 2 Type II attestation covers Reception.ai. Broader agent pages make the claim; the Reception-specific materials do not establish scope.
- Recording and transcript retention periods, deletion controls, and export behavior.
- Whether PII redaction is available here or limited to enterprise agent deployments.
- SSO, role-based access control, audit logs, data residency, and zero-retention modes.
- BAA availability for Reception itself.
Treat all of these as due-diligence questions, not assumed capabilities.
Data & AI Connectivity
Google Calendar is the only directly documented calendar integration. Zapier, webhooks, and MCP all appear in the documentation, with the entitlement caveat above.
Zapier connects through an MCP server and makes configured actions available to the receptionist, the internal assistant, or both. ElevenLabs cites examples including adding a Mailchimp contact, opening tickets in Zendesk or Jira, creating a HubSpot or Salesforce contact, and creating tasks in Asana or Notion. The documentation claims access to more than 5,000 apps, though what actually works depends on the actions configured in your Zapier account.
Webhooks are the more interesting capability. The receptionist collects the required parameters, calls your endpoint during the conversation, processes the response, and keeps talking. Live CRM lookup, inventory checks, eligibility screening, ticket creation, and custom quoting are all technically possible with the right backend. Reception can also connect to compatible MCP servers over SSE or Streamable HTTP, discover their tools, and let you assign each one to the receptionist, the assistant, or both.
What is missing runs the other direction. The public materials document no API for Reception itself. It can call out through webhooks and MCP-connected services, but nothing documented pulls Reception data into your systems on your schedule. No native CRM. No Microsoft calendar.
Ratings
| Dimension | Rating | Rationale |
| Usability | 4.5 / 5 | Website-scan onboarding, guided setup, and a natural-language business assistant put this within reach of a nontechnical owner, on vendor documentation rather than hands-on validation. |
| Power | 3.5 / 5 | It covers the core receptionist workflow well, including transfers, messages, multilingual handling, scheduling, and custom tools, but the scope is narrow and real-world reliability is unvalidated. |
| Flexibility | 2.5 / 5 | Webhooks and MCP extend it further than most tools at this price, though it remains an inbound voice and appointment product with unclear integration entitlements. |
| Cost | 3.5 / 5 | Cheap against continuous human phone coverage, but Basic’s 75 credits, single concurrent call, and $0.45 overage push most working businesses to Plus. |
Best-Fit Roles
Strongest for Operations, then Sales at small firms with no SDR function. Limited direct value for Finance, HR, Marketing, and Research.
Conclusion
Reception is an approachable AI receptionist for businesses that will never open a flow builder. Website scanning, staff-first routing, appointment scheduling, a built-in client record, and an administrative assistant all point at an owner or operations lead rather than a conversational-AI developer.
For a small professional-services firm the case is easy to state: answer calls when the team is busy, capture inquiries that would otherwise become voicemail, and offer a booking path at 11 p.m.
Staff-first routing is the setting that matters most, because it keeps Reception positioned as coverage for the calls your team cannot reach. The judgment it cannot exercise is knowing which caller needed a person. That work stays with you: review the transcripts, find the knowledge gaps, verify bookings and routing behavior, and tune the rules. A receptionist nobody listens to is an expensive voicemail box.
Last updated: 9/17/2026.