Ruby receptionist pricing 2026: Ruby cost per minute, plans and live chat rates

Read on 31 August 2026, Ruby publishes four virtual receptionist plans and prices all of them, which already puts it ahead of most of US legal software. The plans are $250 a month for 50 receptionist minutes, $395 for 100 minutes, $720 for 200 minutes and $1,725 for 500 minutes. Ruby labels them by fit rather than by name: 50 minutes is described as good for startups, 100 for one person businesses, 200 for small businesses of all kinds and 500 for larger and growing businesses. Above 500 minutes the page stops publishing and asks you to talk to sales.

Divide each plan by its allowance and the cost per included minute is $5.00, $3.95, $3.60 and $3.45. That spread is the first thing worth holding onto, because it is smaller than most buyers expect. Going from the smallest plan to the largest is a ten times increase in commitment and it buys a 31 percent discount per minute. Ruby is not running a steep volume ladder; it is running a fairly flat one, which means there is little pricing reward for buying more than you need.

Live chat is sold as a separate product on its own three step card: $143 a month for 10 chats, $335 for 30 and $520 for 50. Per included chat that is $14.30, $11.17 and $10.40. Add chat onto an existing receptionist plan and the same allowances cost $115, $268 and $416, which Ruby advertises as a 20 percent saving. We checked it: the 30 and 50 chat bundles are exactly 20 percent below the standalone rate, and the 10 chat bundle is 19.6 percent below. The advertised claim is accurate, and the bundled per chat rates come out at $11.50, $8.93 and $8.32.

One caution about the minute allowances. A minute on Ruby is billed in rounded increments rather than in seconds, so short calls are more expensive than the headline rate suggests. Ruby publishes the increment on its own comparison page, and it publishes it twice with two different values, which is covered further down this page because it materially changes what a short call costs.

The most important thing about Ruby pricing is not a number. Ruby states it in one sentence on its own pricing page: the only difference between its plans is the number of receptionist minutes and chats, meaning you always have access to the same comprehensive set of features at no extra cost. We have priced this category vendor by vendor since July 2026 and Ruby is the only clean exception we have found to the pattern that runs through everything else.

That pattern is worth naming so you can see what Ruby is opting out of. Jotform puts HIPAA compliance behind its Gold plan, which is a 2.9 times jump from the tier below it. Formstack sells HIPAA as an add on with no published price at all, on both of its self serve plans, so there is no rate at which a Formstack buyer can plan to collect protected health information. Clio Grow, the intake product most firms are shopping for, is included on Elite and Elite Work and sold as an add on for Core and Signature. Smith.ai includes intake but caps it at five short questions and prices every question after that. Ruby does none of this.

Ruby is also unusually specific about the fees it does not charge. Its pricing page states there are no additional or hidden fees for activation, onboarding, setup, customization, or coverage during certain periods. That last clause is the one to notice: it means no after hours, weekend or holiday premium, which is a live cost variable at a large part of the answering service category. Ruby states that number porting is free and that local or toll free number hosting is included.

Two inclusions deserve particular attention because they cost money almost everywhere else. HIPAA compliant services are listed as available on every plan, receptionist and chat alike, with no tier gate and no separate price. And Ruby states that optional AI enhancements are available on all its plans at no extra cost, listing AI powered transcripts, sentiment analysis and AI assisted call flows in the standard feature set. The clean split between a human answering service and an AI one has stopped being clean, and Ruby is charging nothing to blur it.

For a vendor this transparent, there are exactly two gaps, and they happen to sit on the most expensive part of a metered plan.

The first is the overage rate. Ruby publishes four plan prices and four minute allowances and no rate at all for the minutes past them. We checked the pricing page and Ruby own pricing explainers on 31 August 2026 and found no figure. This matters more on Ruby than it would elsewhere, because Ruby has removed every other variable from the decision. When all the features are identical on every tier, sizing the plan is the entire choice you are making, and the cost of getting that choice wrong is the one number you cannot look up. There is a mild irony in it: Ruby own blog criticises competitors for layering overages, weekend fees and holiday fees on top of a plan, and it is right to, but it then leaves its own overage rate unstated.

The second is the billing increment, and here Ruby contradicts itself in a way that is easy to verify. On Ruby own page comparing per minute against per call pricing, the desktop version of its comparison table describes Ruby pricing as per minute, rounded up in 60 second increments. Further down the same page, the stacked version of the identical table describes it as per minute, rounded up in 30 second increments. Both appear on the same URL, read on 31 August 2026.

That is not a nitpick on a per minute meter. Take a 61 second call on the entry plan at $5.00 a minute. Rounded up in 60 second increments it bills as two minutes and costs $10.00. Rounded up in 30 second increments it bills as 1.5 minutes and costs $7.50, which is 25 percent less. Property managers, clinics and firms whose inbound is mostly short calls will hit that difference on nearly every call of the month. Ask Ruby which increment applies to your contract and get the answer in writing before you sign.

The plan price is not the number to compare. A discovery conversation that actually qualifies someone runs five to ten minutes, and on the entry plan at $5.00 a minute that is $25 to $50 per conversation. The $250 allowance holds five to ten of them in a month. On the 500 minute plan at $3.45 a minute the same conversation costs $17.25 to $34.50. Those are the figures to put next to any other vendor quote, and almost no comparison page computes them.

That immediately tells you where the per minute meter wins and where it loses. Ruby is excellent value on short calls: a caller confirming an appointment, asking your opening hours or dialling a wrong number costs you a minute or two rather than a full call charge. Ruby is expensive on long ones, because the meter never stops. Smith.ai, the closest comparison, bills the other way at $10.00, $9.00 and $7.00 per included call regardless of length. Run the crossover and the two models break even at almost exactly two minutes on every tier pairing: $10.00 against $5.00 a minute is 2.0 minutes, $9.00 against $3.60 is 2.5 minutes, $7.00 against $3.45 is 2.0 minutes. Below two minutes Ruby is cheaper; above it, per call billing is.

There is a wrinkle that cuts back toward Ruby, and it is only visible if you have both rate cards in front of you. Smith.ai per call price buys an answered call with up to five short intake questions, and prices nearly everything else separately: extended intake $1.50, booking $1.50, payment $1.00, conflict check $0.50. A fully worked intake call on Smith.ai Starter costs about $16.75 rather than $10.00, which pushes the crossover out to roughly three and a half minutes. Ruby charges nothing for any of those actions. So the honest summary is that Ruby is cheaper for short transactional traffic, Smith.ai is cheaper for long conversations, and Ruby wins back ground whenever the conversation has to actually do something.

One more thing you can only see with both cards side by side. Ruby own comparison page sets its model against an unnamed column headed Others, and that column matches the current published Smith.ai rate card almost line for line: extended intake at $1.50 for six additional questions then $0.25 each, transfer lines at $15 per line per month, additional CRM integrations at $0.50 per call per integration, bilingual answering at $1.00 per call, payment collection at $1.00 per call, ad tracking lines at $5 per line per month. Seven of the nine rows match Smith.ai published rates exactly. Two do not, and both understate the competitor: Ruby column says the other service offers three simple intake questions for free where Smith.ai now publishes five, and it says the other service is closed after hours and on holidays where Smith.ai publishes 24/7 answering with no after hours premium. Ruby comparison is largely accurate and worth reading, but check those two rows yourself rather than taking them from either of us.