Zoom AI Receptionist pricing currently has two paths: Zoom’s public pricing page lists an “Any Phone” plan at $29.99 per month for 100 voice minutes, or $25 per month when billed annually. For Zoom Phone customers, it lists $0.30 per minute plus the cost of Zoom Phone. Prices are shown in USD; confirm local availability, taxes, add-on rates, and the current offer on Zoom’s checkout or quote page.

This is a meaningful distinction for teams deciding whether to keep an existing phone system or move calling into Zoom. The headline rates are not directly comparable until you include call volume, the underlying phone service, and the features your routing needs.

Zoom AI Receptionist pricing at a glance

  • Any Phone: $29.99 monthly for 100 minutes, or $25 monthly when billed annually, according to Zoom’s pricing page.
  • With Zoom Phone: $0.30 per minute, plus the cost of Zoom Phone.
  • Included capabilities listed: natural-language voice AI, multilingual support, live transcription, analytics and call review, and a dedicated phone number.

Zoom lists appointment scheduling with Google Calendar, Microsoft Outlook/Exchange, and Zoom Scheduler for both plans. Its comparison table marks SMS engagement and warm transfer to Zoom Phone users as features of the Zoom Phone option, not the Any Phone plan. That distinction can affect how a caller completes the next step.

What 100 minutes means for your monthly cost

For the Any Phone plan, $29.99 covers the first 100 minutes listed. Your effective cost depends on how quickly you use those minutes and the current add-on pricing for additional usage. Zoom describes flexible licensing and add-on minutes, so get the exact incremental rate before forecasting. For the Zoom Phone option, 200 minutes at the published $0.30 rate would be $60 for receptionist usage, before the Zoom Phone subscription and any other applicable charges. That calculation is illustrative, not a quote.

Estimate using answered calls × average billable duration, then run low, expected, and peak scenarios. If your reception line handles 400 calls of two minutes each, that is about 800 minutes before applying provider billing rules. Ask whether transfers, pauses, and calls abandoned early count the same way, and set an alert or usage review before the first full billing cycle.

Any Phone or Zoom Phone: how to choose

The Any Phone option is designed for deployment without replacing the existing telephone setup. This can reduce migration friction for a business that has invested in another PBX or VoIP service. Verify how your number is connected, what callers see, and which calls can be transferred back to staff. Zoom’s comparison table does not list SMS or warm transfer for this option, so test those requirements explicitly.

The Zoom Phone option may suit teams that want receptionist handling within the same communications environment. Zoom lists SMS support and warm transfers to Zoom Phone users on this route. The trade-off is to include the Zoom Phone subscription in the total cost and check whether migration, number porting, or licensing changes are needed.

Five questions to ask in a Zoom demo

  1. Can the receptionist book, change, or cancel the appointment type we actually use?
  2. What happens when the monthly 100-minute allowance is reached, and what do extra minutes cost?
  3. How does the Any Phone setup transfer a caller to an employee, and is context preserved?
  4. Which calendar, CRM, and language combinations are available in our country and plan?
  5. Can managers inspect call transcripts and routing outcomes to correct weak answers?

Who should consider Zoom AI Receptionist?

Zoom’s offer is relevant to small and mid-sized businesses that need around-the-clock call handling and want a choice between keeping an existing phone system and using Zoom Phone. Teams with unpredictable call durations should model usage carefully; teams needing SMS or warm handoffs should compare the Zoom Phone feature set against the Any Phone plan instead of assuming they are identical.

For a fair vendor comparison, include base phone charges, AI minutes, add-on rates, number setup, calendar access, escalation, and analytics. Ask for the final monthly cost at your expected volume in writing.

Frequently asked questions

How much does Zoom AI Receptionist cost?

Zoom lists $29.99 per month for 100 minutes on the Any Phone monthly option, or $25 monthly when billed annually. With Zoom Phone, it lists $0.30 per minute plus Zoom Phone service. Pricing may vary by region and change over time.

Does Zoom AI Receptionist work with other phone systems?

Zoom’s Any Phone plan is described as compatible with any business phone system. Confirm number connection and transfer capabilities for your carrier and configuration.

Does the Any Phone plan include warm transfers and SMS?

Zoom’s comparison table marks SMS engagement and warm transfers to Zoom Phone users for the Zoom Phone option. The table does not mark these for Any Phone.

Which calendars does Zoom support?

Zoom lists Google Calendar, Microsoft Outlook/Exchange, and Zoom Scheduler appointment calendar integrations for the receptionist plans.

Mapping the Full Call Journey Before You Commit to a Plan

Selecting a plan tier based on published minute allowances alone can leave a business surprised when real call patterns emerge. A more useful preparation exercise is to trace every call type your reception line currently handles, from the moment a caller dials in to the moment the call closes, and then assess where an AI receptionist would take ownership, where it would transfer, and where a staff member would need to intervene. That trace surfaces the operational requirements that a pricing page cannot answer for you.

Consider a fictional example. A small physiotherapy practice receives calls requesting new patient bookings, appointment rescheduling, insurance queries, and directions. A new-patient booking might take two minutes; an insurance query could take seven because the caller needs time to locate a card. If the AI receptionist handles only the first category reliably and escalates the others, the practice is effectively paying for a partial solution. The evaluation question is whether that partial coverage justifies the cost against the remaining staff workload, not whether the published feature list mentions appointment scheduling.

To build this picture, list every call type from the last representative sample period in your current call log or staff notes. Assign each a rough average duration and a desired outcome: completed in the AI session, escalated with context, or escalated without context. The third category is the one that adds hidden cost, because a staff member must re-ask for details the caller already provided. That repetition affects caller satisfaction and staff time, neither of which appears on a licensing invoice.

Evaluating the Handoff as a Distinct Operational Event

The moment a call moves from an AI receptionist to a human is a distinct process with its own success criteria. Evaluation teams sometimes test the AI's ability to handle calls in isolation, then treat the transfer as a secondary concern. In practice, a poor handoff can undermine an otherwise competent AI interaction.

When assessing any plan that includes call transfer, define what a successful handoff looks like for your business before running tests. A useful set of criteria might include whether the receiving staff member knows the caller's name and stated purpose without asking, whether the caller is told what to expect while waiting, whether the transfer reaches the correct person or queue on the first attempt, and whether any booking or reference created during the AI session is immediately visible to the staff member who picks up.

To test this concretely, run a scenario where a caller provides their name, states a specific purpose, and asks a follow-up question before being transferred. After the transfer, ask the receiving staff member to describe the call context from what they received alone. If they cannot accurately summarise the caller's need, the handoff is not carrying context effectively, regardless of what the feature description says. This is an observable test you can repeat across different call types.

Where warm transfer is listed as plan-dependent, as it is in the distinction between plan options described in the article, treat this test as a prerequisite evaluation step rather than a post-purchase adjustment. If warm transfer is essential to your service model, confirm its availability and test its behaviour before signing an annual commitment.

Structuring a Usage Forecast You Can Defend Internally

Any forecast of AI receptionist costs needs to be built on call data that reflects your actual patterns rather than round estimates. A defensible internal forecast might look like the following worked structure.

Call type Estimated calls per month Estimated average duration Likely AI ownership
Standard booking Variable, drawn from your log To be measured from recordings Full or transfer at confirmation
Rescheduling request Variable Likely longer; caller may need to check availability Depends on calendar lookup depth
General enquiry Variable Unpredictable; may loop Partial; escalation likely
Misdirected or silent call Variable Short but still billable under some billing models Terminated with standard message

The value of building this table is not the numbers themselves but the conversation it prompts with the vendor. Ask specifically whether misdirected calls, silent calls, and calls abandoned within the first several seconds count toward your minute allowance. Ask whether transfer time after the AI session ends is included. The answers will change your effective cost per useful outcome, which is a more meaningful figure than cost per minute.

Run three versions of this forecast: a lower-volume scenario using quieter periods, an expected scenario based on the recent average, and a peak scenario using your busiest weeks. If the peak scenario would trigger significant overage, understand the overage process before that situation occurs rather than after the invoice arrives.

Exception Cases That Reveal System Boundaries

A useful acceptance exercise includes calls that should fail gracefully rather than calls designed to succeed. These edge cases are where operational risk concentrates.

Consider a caller who gives a name that the AI mishears and confirms incorrectly. What does the stored record show? If a booking is created under the wrong name, the downstream problem lands on staff, not on the AI system. Test this scenario with a name that is commonly mispronounced or has an unusual spelling, then inspect the calendar entry, the transcript, and the confirmation the caller received.

Consider a caller who asks to book outside available hours and pushes back when told no slots exist. Does the AI hold the boundary clearly, offer a next available time, or loop in a way that extends the call without resolving it? The transcript and the staff escalation note, if any, will show you whether the system handled disagreement constructively.

Consider a caller who switches from one language to another mid-call. Where a multilingual capability is offered, the real test is not whether the system handles each language independently but whether the record it produces after a mixed-language call is coherent. Inspect the full transcript and any data fields populated from that call.

These scenarios are not designed to find failure for its own sake. They are designed to show you what the system hands to your staff when it reaches its boundary, so that your staff protocols and fallback routes are built around observed behaviour rather than assumptions drawn from capability descriptions.

Before completing any evaluation, document in writing which call types the AI will own completely, which will require a handoff, and which your team will continue to handle directly. That document becomes the operating agreement your staff work from on day one, and reviewing it at the end of the first full billing cycle gives you a grounded basis for deciding whether to continue, adjust the configuration, or reconsider the plan.

Sources

See how connected call workflows can link voice, customer context, and follow-up in Sysevo Voice.

Zoom AI Receptionist cost scenarios

Zoom currently offers two routes with different economics and capabilities. Receptionist with Any Phone lists $29.99 monthly or $25 per month when billed annually for 100 minutes. Receptionist with Zoom Phone lists $0.30 per minute plus the cost of Zoom Phone. On the public comparison, Any Phone works with an existing phone system but does not include SMS engagement or warm handoff to Zoom Phone users; those are listed for the Zoom Phone path. Verify the current offer and terms before you buy.

For a 250-minute month, the Any Phone license starts at $29.99 before additional-minute charges; the page describes add-on minutes but you should obtain the current rate rather than assume one. Zoom Phone’s AI component would be 250 × $0.30, or $75, plus the phone plan. These examples do not include taxes, optional services or call-routing charges. If you are comparing annual Any Phone pricing, compare the monthly equivalent with the upfront commitment and cancellation terms.

The two options should be compared against your desired caller journey. If an external carrier must remain in place, Any Phone can reduce migration work, but verify how calls are forwarded, what caller ID the receptionist sees and how a human takes over. If your team already has Zoom Phone or needs warm transfer and SMS, calculate the full Zoom Phone account cost rather than focusing on the AI per-minute rate.

Confirm calendar, scheduling and language requirements

Zoom’s current page lists appointment scheduling with Google Calendar, Microsoft Outlook/Exchange and Zoom Scheduler for both receptionist paths. A buyer should still test the precise workflow: appointment type, working hours, buffers, time zone, cancellation rules, double-book prevention and what confirmation is sent. If different teams offer different services, confirm that the correct calendar and duration are selected from the caller’s request.

Test daylight-saving transitions and callers who describe a date conversationally, such as “next Friday afternoon.” Verify the stored time in the connected calendar and the caller-facing confirmation. If the calendar is unavailable or returns no slots, the AI should offer a safe next step rather than promise an appointment it cannot verify. For an existing customer asking to reschedule, check whether the agent can locate the original booking or whether a staff handoff is required.

For multilingual businesses, test the actual languages, accents and business vocabulary your callers use. A general multi-language claim is not enough to establish that product names, street names or specialized terms are recognized reliably. Include a bilingual caller who switches language mid-call and inspect the transcript and final record for errors.

Compare expected minutes with your routing plan

Estimate which calls Zoom will answer. If the receptionist handles every incoming call, usage may include routine calls that a staff member would otherwise answer quickly. If it is used only after hours or when a line is busy, the minutes will be different, but the forwarding and timeout configuration becomes critical. Count calls that reach the AI, average connected duration, transfers, and abandoned calls using the vendor’s current billing definitions.

For Any Phone, ask how additional minutes are purchased, what they cost, whether there are usage notifications and whether the service keeps answering when the allowance runs out. For Zoom Phone, confirm if the $0.30 rate applies to the AI portion only, how carrier/phone usage is billed, and whether transferred calls continue to incur AI or phone charges. Document answers for normal, peak and overage cases.

Use a realistic demo checklist

Prepare five test calls: a common FAQ, a booking, a request for a person, an unclear or unsupported question, and a call during a simulated system failure. Add one call that requires a warm transfer if Zoom Phone is being considered and one SMS follow-up if that feature is part of the purchase. After each call, verify the action in the calendar or business system, the caller’s confirmation, the transcript, and the staff context.

Ask an employee who did not configure the receptionist to assess the handoff. Did the call arrive at the right place? Did they know why the caller was transferred? Was the caller asked to repeat personal details? Record time spent fixing the result. This makes the comparison useful to operations, not just the person evaluating the voice interface.

Finish with a total-cost table: license or annual amount, AI minutes, phone subscription, forwarding, overage, SMS, numbers and any implementation support. Then compare cost per confirmed outcome with your current call path. The official Zoom Receptionist pricing page is the current source for package details; take a dated copy of the relevant quote for procurement.

Choose Zoom Receptionist with a migration checklist

If the business keeps its existing phone provider, document how calls reach the Any Phone receptionist: forwarding method, ring timeout, caller ID, number ownership and the route back to a human. Test whether the current carrier supports the needed forwarding behavior and whether forwarding charges apply. Ask how to return to the old route if the test is unsuccessful.

If you are considering Zoom Phone, include migration work in the total cost: number porting, user licenses, emergency calling setup, devices, training, voicemail changes and other phone-system features. Confirm whether all staff need a Zoom Phone license or only the users who receive transfers. A lower AI rate may not outweigh the cost or effort of changing the surrounding phone service.

Check which plan supports your actual handoff

Zoom’s public comparison distinguishes warm transfer and SMS support between the Any Phone and Zoom Phone paths. Write down which team members receive transfers, whether they need to speak before accepting, and what the caller should hear while waiting. If SMS confirmations are essential, test the exact message, sender number and opt-in process. Do not assume an Any Phone plan includes a Zoom Phone feature.

Ask what happens if the receptionist cannot reach a person, the phone account is unavailable or the call comes from a number the system cannot identify. Test after-hours and overflow behavior. A deployment is ready when the caller has a clear next step in both the success path and the failure path.