Provider pricing review
Ruby receptionist pricing for home service teams
Ruby lists receptionist plans at $250/month for 50 minutes, $395 for 100, $720 for 200 and $1,725 for 500. These are live-receptionist minute plans; chat is separate. Published by Revo; official pricing checked October 21, 2026. Confirm your quote and excess-minute terms directly with Ruby.
Updated · Published by Revo
| Monthly receptionist minutes | Published monthly price | Confirm in the proposal |
|---|---|---|
| 50 | $250 | Billable-time definition, rounding and excess-minute rate |
| 100 | $395 | Same receptionist feature set; confirm the account scope |
| 200 | $720 | Usage review and the work delegated to receptionists |
| 500 | $1,725 | Current agreement; larger plans by consultation |
01 / Provider pricing review
Start with the receptionist price card
Ruby’s dedicated pricing page lists receptionist plans at $250 per month for 50 minutes, $395 for 100 minutes, $720 for 200 minutes and $1,725 for 500 minutes. The page says the receptionist feature set is shared across those plans and that larger plans are available by consultation.
The same page separately lists managed-chat plans. A chat allowance is not a receptionist-minute allowance. Confirm which service is in your proposal before comparing the headline monthly cost.
The pricing page describes optional AI enhancements within its receptionist offering. Do not interpret that wording as a separate, fully autonomous AI answering plan or assume it has the same operating model as Revo. Check the current product and contract directly.
02 / Provider pricing review
Reconcile the price source before relying on it
Use the dedicated pricing page as the dated reference for the figures above. Request a written quote for the account, term and services you intend to buy. If a sales page, old article or existing agreement shows a different amount, resolve that discrepancy with the provider rather than combining the lowest numbers from different sources.
Ask what starts and stops billable receptionist time, the billing increment and the rate after your allowance. Those details are not established by the headline minute counts shown here. Keep them as open quote questions until Ruby answers them for your package.
Give the office manager the accepted proposal and the process for reviewing usage. A plan should be assessed against your actual incoming call history and delegated tasks, not an assumed number of jobs per minute.
03 / Provider pricing review
Match live answering to the home-service workflow
Ruby’s site identifies home services among the industries it serves and describes live answering, scheduling, intake and outbound calling. Those are product descriptions, not proof that every office’s calendar, dispatch software or call policy is supported without configuration.
For an estimate request, identify which information the receptionist must capture and where the office will find it. For scheduling, require a demonstration of the actual booking destination. For an existing appointment change, confirm who may alter the record and how the customer receives the next step.
For a handoff, distinguish a receptionist supplied by the provider from a technician or employee receiving a transfer. Decide what the caller hears when your team cannot answer. Do not count a transfer attempt as a confirmed appointment or dispatch.
04 / Provider pricing review
Compare the total proposal with your alternatives
Use one requirements list for every seller: coverage hours, languages, intake fields, booking destination, transfer recipient and staff follow-up. Then compare the charges for that scope. Equal minute allowances do not establish equal handling rules or the same completed work.
When comparing with Revo, review Revo’s current plan inclusions directly. Ruby’s live receptionist offering and Revo’s AI answering service should be compared by the outcomes your business needs, without assuming identical staffing or supported software actions.
Keep the original phone route and an owner for rollback while you test a new setup. Review the actual captured request, appointment record and handoff outcome before changing the main number. Use your own measured results for a purchasing decision; a price card alone does not establish conversion, customer satisfaction or savings.
Common questions
Make the next step clear.
Resolve the details that matter to your team and callers.
Does every Ruby receptionist plan have a different feature tier?
The dedicated pricing page says the receptionist plans share the same feature set and differ by monthly receptionist minutes. Confirm current account-specific terms.
Can I treat chat allowances as phone-answering minutes?
No. Ruby publishes chat and receptionist services separately. Ask which service and usage unit your proposal includes.
Are excess-minute rates and rounding confirmed here?
No. Obtain those rules from Ruby for your selected plan before forecasting a bill. The listed monthly allowances do not establish every billing condition.
Sources and current terms
Resolve the quote before changing your call route.
Review Revo’s current features and plans for the workflow your business needs.
Compare plans