RingCentral AI Receptionist pricing depends on whether you buy it on its own or add it to RingEX. RingCentral’s current pricing page lists the standalone plan from $49 per month with 100 minutes, and the RingEX add-on from $39 per month, also with 100 minutes. It lists $0.50 per minute for usage above the included allowance, billed in 30-second increments. Prices are shown in USD and may vary by region, billing term, taxes, and product availability.
These amounts are a starting point, not a full comparison. The RingEX add-on price assumes the customer also has the underlying RingEX service; include that subscription when calculating total cost.
Standalone AIR vs RingEX add-on
Standalone AIR may be relevant if you want RingCentral’s AI receptionist without adopting its full business phone system. RingCentral says AI Receptionist works with any phone system. Confirm which connection method applies, how your existing number routes calls, and how staff receive a transferred call.
RingEX add-on is the lower listed receptionist starting price for existing RingEX customers. Add the RingEX plan cost, user or number licensing, and any needed features to the AI fee. In return, teams may value using their existing RingCentral environment and connected call handling. Compare specific included features against your current subscription rather than relying on the “add-on” label.
How to estimate AIR usage
At the published $0.50 per-minute overage rate, 40 minutes beyond the included 100 would add $20 before other charges. If RingCentral rounds up and bills in 30-second increments, as its pricing FAQ states, a 61-second call may not be charged as exactly 61 seconds. Ask the sales team to illustrate billing with a few representative calls and explain whether rounding applies to every call.
Build a forecast from recent call records: monthly calls the AI will answer × average duration. Make a separate peak-period estimate, and consider the calls that transfer to staff or require a longer conversation. Check if additional 100-minute bundles have a different unit cost, whether the system gives usage notifications, and what happens when included minutes run out.
What AIR is designed to handle
RingCentral describes AIR as able to answer common questions, capture leads, send texts, schedule appointments, and route callers with context. Its pricing page says it can work with any phone system. The exact feature set and integrations depend on plan and deployment, so validate the workflow you need with a demo instead of treating every capability as automatically included.
Prepare a short call test: a new lead requesting a quote, an existing customer asking for an update, an urgent call that must reach a person, and a caller whose request the AI cannot resolve. Review whether the system captures the right fields, sends the right message, avoids inventing unavailable details, and gives the employee useful context.
RingCentral AI Receptionist checklist
- Is the quote standalone AIR or AIR added to RingEX?
- What is the total monthly bill including RingEX if required?
- Are 100 minutes pooled across several assistants or assigned per license?
- Does the 30-second rounding apply to every call, and what happens on transfers?
- Can we add minute bundles, set a cap, or enable alerts?
- Which CRM, calendar, SMS, and human-transfer features are included for our country?
- How are transcripts, recordings, access, and retention configured?
Who may find it a fit?
RingCentral AIR is worth a closer look for businesses that want a 24/7 front desk, need to preserve a current phone system, or already use RingEX. It may be particularly interesting where lead capture, appointment scheduling, and context-rich handoff are more valuable than simple message taking. Whether it is the right option depends on the call paths, languages, data controls, support, and total usage cost in your specific deployment.
Frequently asked questions
How much is RingCentral AI Receptionist?
RingCentral currently lists standalone AIR starting at $49 per month and an add-on to RingEX from $39 per month, each with 100 included minutes. Above the allowance, the page lists $0.50 per minute, billed in 30-second increments. Verify your quote and region.
Does AIR work with an existing phone system?
RingCentral advertises compatibility with any phone system. Ask how your number, transfers, and business-hours routing will work in practice.
Is RingEX included in the $39 add-on?
No. The listed $39 is the AIR add-on starting price; RingEX is the underlying phone service and should be included in your total-cost estimate.
Does RingCentral offer a free trial?
RingCentral’s current pricing FAQ describes a 14-day trial for its standalone and RingEX add-on plans. Check current eligibility when requesting a trial.
Evaluating Call Ownership and Responsibility Before You Sign
One practical gap that surfaces during any AI receptionist evaluation is the question of who owns a caller interaction at each stage. When a human receptionist answers a call, responsibility is clear: that person hears the request, decides how to respond, and either resolves it or hands it off with a verbal summary. With an AI layer in the path, ownership becomes distributed across the system, the caller, and whichever staff member receives the transfer. Before committing to any plan, map that chain explicitly for your most common call types.
Start by listing the decisions that currently happen inside a single phone call. These might include verifying whether a caller is an existing customer, deciding whether a request is urgent, choosing which department or person should receive a transfer, and determining what information the receiving employee needs to act without calling back. For each decision, ask whether an AI system could make it reliably given the training data you can provide, or whether a human judgment is genuinely required. That analysis shapes your routing rules before any demo, rather than after problems appear in production.
Caller identity deserves its own row in that analysis. A caller who says they are an existing customer may or may not be, and the consequence of treating an unverified caller as verified varies widely by business type. A medical practice, legal office, or financial services firm carries different obligations around caller identity than a retail appointment business. Evaluate what information the AI would collect, how it would be stored, and who would correct a record if the caller provided inaccurate details. These are administrative design questions you can settle before a trial, not after a mis-routed call creates a correction workload.
A Fictional Enquiry Traced from Receipt to Completion
Consider a worked scenario to make these decisions concrete. A caller named Petra contacts a small landscape design firm outside business hours. She wants a quote for a new residential project and mentions she spoke with the firm once before, though she is not sure the previous enquiry was logged. Trace that call forward.
The AI receptionist answers, greets her, and attempts to capture her name, contact number, project type, and preferred callback time. At this point, two separate records may exist: the current call record and any prior enquiry record. The design team needs to know whether those records link automatically, manually, or not at all. If Petra gives a slightly different phone number than last time, how does the system handle the mismatch? Who reviews it, and by when?
The call continues. Petra asks whether the firm handles commercial projects in addition to residential work. If the answer is in the system's knowledge source, she receives it. If it is not, the system may say it cannot help, transfer her, or give a vague response. Each of those outcomes has a different effect on whether Petra stays on the line or calls a competitor. During a trial, test this exact type of edge question with wording that does not match your FAQ phrasing precisely, because real callers rarely phrase questions the way a business writes its own answers.
Suppose the AI captures her details correctly and schedules a callback for the following morning. The relevant designer arrives the next day, opens the record, and finds the name, number, project type, and callback window. They do not have the part of the conversation where Petra mentioned she had spoken with someone previously. That missing detail changes how the designer opens the call. Build a review of what the handoff record actually contains into your trial evaluation, not what you assume it contains.
Criteria for Comparing Call Handling Paths
When assessing whether an AI receptionist plan suits your business, the following criteria give you a structured basis for comparison. Each carries a distinct reason it matters operationally rather than just commercially.
- Routing logic transparency: Can a non-technical staff member read the routing rules and understand why a call went where it did? Opaque routing makes exception diagnosis slow.
- Caller identity handling: Does the system distinguish between an identified returning customer and an unverified caller making the same claim? The distinction affects data accuracy and staff preparation.
- Knowledge update latency: When your hours, pricing, or services change, how quickly does the AI reflect that change, and who is responsible for updating it? Stale answers damage caller trust.
- Transfer context completeness: What does the receiving employee see before speaking? Context that arrives only after the conversation starts creates repetition for the caller.
- Exception escalation path: When the AI cannot resolve a request, what happens next, and does that path work when no staff member is available? A dead end at escalation is worse than a voicemail.
- Record correction process: If a caller provides wrong information, who corrects it, when, and through which system? A process that relies on a staff member noticing a discrepancy later is worth accounting for in your workload estimate.
Staff Readiness as a Deployment Variable
A pricing decision is partly a staffing decision. If the AI handles routine enquiries but transfers complex ones, the staff receiving those transfers will encounter a higher proportion of difficult calls than before. That shift in call mix deserves explicit acknowledgment. A receptionist who previously handled a blend of simple and complex calls may find that the remaining transferred calls demand more sustained attention per interaction. Build that into your assessment of how the tool changes workload rather than simply reduces it.
Equally, someone in the business needs to own the ongoing knowledge management for the AI: updating service descriptions, adjusting routing rules when staff change, reviewing flagged calls, and responding when a caller complains that the system gave incorrect information. That role may fall to whoever currently manages the phone system, or it may be new. Identify the owner before the trial ends, not after the first complaint.
For businesses where calls occasionally involve sensitive requests, consider in advance how staff will handle a caller who reached the AI but needed a human immediately. Have a clear internal protocol for what staff do when they receive a transferred call with incomplete context. A short internal briefing before go-live is more effective than troubleshooting individual failures after they occur.
An Acceptance Exercise Before Full Commitment
Toward the end of any trial period, run a structured acceptance exercise rather than simply reviewing a summary report. Assign one team member to make several calls in the role of a new enquirer, one in the role of a returning customer, and one in the role of a caller with an unusual or incomplete request. Do not tell the caller what the AI should do; observe what it actually does and record the outcome in plain language.
Observable evidence worth recording includes whether the greeting matched your business name correctly, whether the system asked for information the caller had already provided, whether the handoff record was complete when the receiving staff member opened it, and whether any confirmation message sent to the caller contained accurate details. Collect these observations in a simple shared document. Where the outcome fell short of your standard, note whether the gap is a configuration issue you can address or a capability boundary you need to accept as a constraint.
That document becomes your decision record. Combined with the actual usage figures from the trial, it gives you a factual basis for choosing a plan, negotiating terms, or deciding the tool is not yet the right fit for your call volume and complexity. Keep it alongside your written quote so that when usage grows or call types change, you have a baseline to compare against rather than relying on memory of how the trial felt at the time.
Sources
Compare how an AI receptionist can connect calls to customer records and next actions with Sysevo Voice and Sysevo CRM.
RingCentral AIR cost examples with overage
RingCentral currently lists AIR as a standalone plan from $49 per month with 100 minutes, or as a RingEX add-on from $39 per month with 100 minutes. Its pricing FAQ says usage beyond the allowance is $0.50 per minute, call time is rounded and billed in 30-second increments, and both plans include a 14-day free trial. Confirm current terms for your account because the standalone plan and RingEX add-on are different purchase paths.
Using those published starting prices, a simple 200-minute example would be $49 plus 100 overage minutes at $0.50, or $99 for the standalone AIR license before any phone plan, taxes or other charges. The RingEX add-on example would be $39 plus $50 in overage, or $89, but that is not the full communications bill because the RingEX plan itself is additional. A 250-minute standalone example would be $49 plus $75 in overage, or $124, again before other account costs. These are transparent arithmetic illustrations, not quotes.
Because the vendor rounds in 30-second increments, short interactions near a billing boundary may consume more billable time than a calculation based on exact seconds would imply. Ask whether the 30-second increment applies to each call independently and how transferred calls are measured. Review actual call records after the trial rather than extrapolating solely from a stopwatch.
Standalone AIR or a RingEX add-on?
Standalone AIR may be relevant if you want an AI receptionist with an existing phone system and do not want to move the rest of the business calling environment. The RingEX add-on can be attractive if your team already uses RingCentral and the included AI actions work with its current numbers, routing and account setup. The practical comparison is not simply $49 versus $39: it is the total incremental cost, transfer path, number ownership and administration effort for your specific phone environment.
Ask whether standalone AIR supports your current carrier and whether calls need forwarding, a new number or porting. For a RingEX add-on, confirm which RingEX plan is required, whether the license is per business or per receptionist, and how multiple locations or languages are handled. Verify what happens to the AI receptionist if your RingEX subscription changes or if a number is moved.
Test routing and booking, not only FAQs
Build a trial around the calls that currently interrupt your team. Include a new lead, an existing customer, a caller asking for a named employee, an appointment request, an after-hours call and a question that requires information from an uploaded document. RingCentral describes website, FAQ and document-based training; your test should check whether the exact source is interpreted correctly and remains current when the underlying business information changes.
For each call, check the final record and human handoff. If AIR captures a lead, confirm the contact fields and CRM destination. If it schedules an appointment, verify the calendar, time zone, duration, service and confirmation. If it transfers, ensure the receiving employee receives enough context. Test a failed transfer and a caller who declines to provide a requested detail. Do not count a task as complete if staff must reconstruct the conversation afterward.
Decide whether the allowance fits your call pattern
Take several weeks of call logs and estimate which portion would reach AIR. Separate calls answered by staff, abandoned calls, calls that go to voicemail and internal transfers. Then estimate how many of those calls AIR could realistically handle, based on the tasks it supports and your escalation rules. Use the median duration by call type, not the overall average alone; a small number of long calls can materially change monthly use.
Compare three possible usage totals: a quiet month, a typical month and a seasonal peak. Include time spent on transfers and calls that continue after an AI handoff according to the vendor’s billing definition. Set a usage alert owner and a threshold for reviewing consumption before the 100-minute limit. During the trial, compare projected minutes with the usage dashboard and adjust your estimate.
Assess value per completed outcome. If the purpose is to capture new business, divide full AIR cost by qualified leads that enter the CRM correctly. If the goal is appointment booking, use confirmed bookings that required no correction. Add the cost of RingEX, staff exception handling and any setup effort to make the calculation comparable with your existing process.
Use RingCentral’s current AIR pricing page and the written quote as the source for final pricing. Keep the date, product path, included minutes, overage, billing increments, trial end and connected phone-system fees together in your decision record.
What to keep after the 14-day RingCentral AIR trial
Before the RingCentral trial expires, export or record the test outcomes and actual usage. Note the number of calls, minutes consumed, overage estimate, successful bookings, qualified leads, transfers and corrections. Compare the observed workload with the 100-minute allowance and decide whether standalone AIR or the RingEX add-on is the intended purchase. Do not let an auto-renewal or a trial end date make the decision by default.
Confirm how to cancel or convert the trial, what number remains active, and whether test data and call recordings are retained. If you decide not to proceed, restore the previous phone routing and verify it with a test call. If you proceed, document who owns the license and how usage alerts are monitored.
Make the handoff measurable
For each transfer, record whether the call reached the right person, whether the receiving employee had enough context, and whether the caller had to repeat details. Also track calls where a human was requested but not reached. These measures reveal whether AIR is acting as a front desk or simply inserting another step before staff.
Compare the AIR route with your current phone flow using the same business hours and call categories. Review a sample each week and classify issues as routing, knowledge, calendar, caller identity or transfer availability. Assign an owner to update the source information or call rules, then retest. This builds a practical improvement loop around the agent rather than treating launch as the finish line.



