A $29-a-month AI receptionist: where the box ends and implementation begins

What exactly $29 buys

ElevenLabs announced Reception on 16 September 2026 and describes the product in one sentence: an AI receptionist for small businesses that answers calls around the clock, responds to questions about your business and books appointments in your calendar. For telephony you choose: forward an existing line or take a dedicated number. The trial is 14 days and 30 minutes of calls, no card required.

There are three paid plans. The figures below come from the reception.ai price list and the pricing page in the vendor's documentation as of 22 September 2026; the two sources match. Prices are in US dollars, before tax.

• Basic — $29 a month: 75 minutes, overage $0.45 per minute, one number, one concurrent call.
• Plus — $79 a month: 275 minutes, overage $0.38 per minute, three numbers, three concurrent calls.
• Premium — $199 a month: 1,000 minutes, overage $0.30 per minute, five numbers, ten concurrent calls, up to 20 locations.

On annual billing the same plans cost the equivalent of $24, $66 and $166 a month. According to the price list, the set of integrations is the same on every plan: Google Calendar, Calendly, Zapier, webhooks, MCP and your own telephony through Twilio or a SIP trunk (the term for connecting your phone carrier to a third-party service). In September the documentation said otherwise in one place; more on that in the section on boundaries.

What a minute really costs

The cost per minute is the subscription fee divided by the included minutes, plus overage. On Basic that is $29 ÷ 75 = $0.39 per minute, on Plus $79 ÷ 275 ≈ $0.29, on Premium $199 ÷ 1,000 = $0.20. Every minute over the allowance costs more than an included one: $0.45, $0.38 and $0.30 respectively.

The price list doesn't show the credit model. In the Reception documentation there is one pool of credits per month: a minute of a phone call equals one credit, a minute of web chat half a credit. A credit is also deducted in Staff-first mode, when the phone first rings your employee for 10, 15, 20 or 30 seconds and a person picks up: that minute counts too. Unused credits do not roll over to the next month.

An example using the price-list figures. Say a salon runs up 120 minutes of calls a month through its Reception number. On Basic, 75 minutes are covered by the $29 and another 45 are billed at $0.45 — that is $20.25 in overage, $49.25 in total, or $0.41 per minute. On Plus the same 120 minutes fit within the $79 plan: more expensive for the month, but with 155 minutes to spare for the busy season. In this calculation, “$29 a month” means 75 minutes of all traffic through the number, including the calls your own people answered; the minutes the AI itself worked are fewer.

Ask the vendor how partial minutes are billed before you work out a budget.

Where the box ends: four boundaries

The box does all of that on its own. According to the vendor's documentation, there are four places where the product ends and someone's work begins.

Reception writes the booking to Google Calendar and to its own built-in client record with a history of contacts. For a call to update an external CRM — create a deal, add to the history, assign a task to the sales rep — you need a webhook or an MCP server. A webhook here is an address in your system that the receptionist calls during the conversation; MCP is the protocol an agent uses to connect to external tools. Both are in the documentation, and the webhook can do more than read: next to a CRM lookup (GET), the vendor lists POST scenarios such as sending caller details to your marketing system or creating a support ticket during the call; MCP is described as a way to “pull customer data from your internal systems during calls.” But that is only the calling mechanism: the vendor does not supply the endpoint that creates a deal in Bitrix24, Uspacy or KeyCRM; someone has to write it and then maintain it. As of October 2026, Reception’s only ready-made CRM connector is for HubSpot, and it adds a conversation summary to the contact; there is no connector for Bitrix24, Uspacy or KeyCRM.

One more detail for anyone budgeting for exactly $29. As of 22 September, the integrations page in the documentation said that Basic included only Google Calendar and the rest started with Plus, while the price list and the pricing page in that same documentation gave Zapier, webhooks and MCP on every plan. As of October 2026 the contradiction is gone: the integrations page now says every integration is available on every plan, including the free trial. The documentation changed noticeably within a month, so before you buy, still ask in writing what your plan includes.

The documentation allows up to a hundred transfer rules per receptionist (as of October 2026 the price list still says “up to 10”), and each consists of a label, a condition in natural language and the phone number to transfer to. A number, and only a number: a transfer rule contains no CRM actions. By default the rep gets a call, not a conversation: it is a blind transfer. There is an option where the person receiving the call first hears a summary of the conversation, but it works only when all of the receptionist’s numbers are Twilio numbers, and a summary heard over the phone is still not a record in your system. What the client has already told the agent does not reach your CRM by itself, and for the rep to open the record and see what the call is about before picking up, you need that same external integration from boundary 1.

You can set up to fifty behavior rules, each with a priority: Strict, which the agent must always follow, or Suggestion, which, according to the documentation, it may deviate from “if the conversation requires it.” There is no algorithm behind these instructions. The vendor publishes no measurements of how accurately the agent will carry out “a booking can be rescheduled no later than a day in advance,” “new clients make a prepayment” or “the Sykhiv branch takes clients only until 18:00,” and gives no guarantee that a rule will work the same way every time. Nor does the box decide what counts as a mistake and who answers for it.

Reception assigns a US or Canadian number instantly, with a three-digit area code such as 415 or 212; after you cancel the subscription, the number is released in 14 days. As of October 2026 the documentation also describes local numbers for about 50 more countries, Ukraine and Spain among them, but through a regulatory request with your business address and documents, and until it is approved the number does not take calls. The other routes for a business outside the US are forwarding its own line or its own telephony through Twilio or a SIP trunk, which now has its own page in the documentation. For a business outside the US, transfers to a person and Staff-first mode work only when all of the receptionist’s numbers come from your own Twilio account or SIP trunk. The cost of international forwarding and the delay on the line are not described in the documentation.

It is much the same with language. The vendor claims over 70 languages with automatic detection and switching mid-call, but publishes no list, and on the voice page the vendor itself advises: if you serve multilingual callers, test the voice in each language. Ukrainian is not named once on the Reception pages, and it is not stated which recognition model the product runs on. Ukrainian may well work fine; you will have to confirm that yourself, with a pilot on real calls. Why no vendor has a public measurement of Ukrainian speech recognition on a phone channel is something Grow2.ai, the AI division of Auspex, covered in a separate article, linked below.

Who the box is enough for

A salon with one location, bookings in Google Calendar or Calendly, calls in one language that was tested during the trial, one number and three or four rules that fit into a single paragraph: that is a business that doesn't need an implementer. If a calendar entry and a record in Reception itself are all you need after a call, and your front desk works from the calendar anyway, you pay $29 or $79, write the rules and spend the first week checking what lands in the calendar. In that case Auspex will say “buy the box” on the very first audit call.

Five questions: box or implementation

Answer them in order. Each question has two possible answers: one leads to the box, the other to work you pay for.

• Where should the booking live: in the calendar or in the CRM? The calendar: box. A CRM with the client's history, a deal and a task for the rep: implementation, because the vendor does not supply a webhook that writes to it.
• What language do your clients call in? A language you tested with real calls during the 30 trial minutes: box. Ukrainian or Surzhyk (mixed Ukrainian-Russian speech) without that test: first a pilot with measurement, then a decision.
• Whose telephony: a rented number or your own line? A number from the vendor (a US one instantly, a Ukrainian or Spanish one after a regulatory request), or forwarding to it, works for you: box. Your own Ukrainian or Spanish number that your clients need to keep: a SIP trunk that still has to be set up and tested.
• How many rules does the process have? Up to ten, all of them fit into one paragraph, and a deviation costs nobody anything: box. Prepayment, branches, rescheduling, different scenarios for new and regular clients: logic like that is better kept in the CRM, where a deviation is impossible by design.
• Who answers for the agent's mistake? The mistake is visible in the calendar and the front desk fixes it in a minute: box. The mistake is a lost client, a double booking for a treatment or a prepayment that was never collected, and there is nobody to fix it: you need a person who checks the agent, a handoff of difficult cases to that person and a log, and that is already a project.

One “implementation” answer: take the box for the trial period and close that one gap with a webhook or call forwarding before you pay anyone. Two or more: stop counting the cost of a minute and start counting the cost of a mistake.

What the implementer does when the answer is “implementation”

The boundary between the box and a project runs through the CRM and the process, so the implementer's work starts with them, and voice comes last. Auspex prepares the side the box doesn't reach:

• a webhook that turns a call into a contact and a deal in Uspacy, Bitrix24, Pipedrive or Zoho, adds to the history and assigns a task to the rep;
• the rules for rescheduling, prepayment and branches, rewritten from text into CRM logic;
• call transfer together with the client record;
• a log where every agent mistake is visible before the client notices it.

A full CRM audit takes 2–3 days, implementation 2–4 weeks, up to 6 with integrations; the median from start to go-live is 30 days. In Ukraine Auspex implements Uspacy; in the EU and Spanish markets, Bitrix24 as a Gold Partner.

The voice agent itself — the model, the prompt, measuring Ukrainian on real calls and three layers of protection: rules in the prompt, a second model that checks the answers and a human — is the work of Grow2.ai, the AI division of Auspex. That is where you go if the second question on the list gave the answer “pilot.”

How to test the box before paying anyone

The trial gives you 14 days and 30 minutes without a card. Spend them on calls that resemble real ones: from a mobile phone, from the street, in Ukrainian with Russian words mixed in, with a request to reschedule a booking and a question about a price that isn't in the knowledge base. After each call look at two things: what appeared in the calendar and what the agent did with a rule marked Strict. If after ten or so such calls all ten bookings are in the calendar, with no duplicates and at the right time, you don't need to look for an implementer.

If you answered “implementation” to two of the five questions, bring this list to a free 30-minute CRM audit call with Auspex: we go through where the call should land in your system, which rules need to move into the CRM and whether you need anyone at all besides the box. We will call you within 24 hours of your request. The service page is below, under “Read next.”