Ruby Receptionists Review 2026: Pricing & Billing Traps

Pros and cons at a glance

The short answer

Ruby is a live virtual receptionist service built around US-based human receptionists rather than an AI voice bot, and it has been selling that pitch for more than 20 years. The company answers calls for law firms, healthcare practices, home services companies, and other small businesses that want a caller to reach a real person even when nobody is at the front desk. In 2026 Ruby has layered AI tools on top of that human core, call transcripts, sentiment tagging, and a robocall filter, but the receptionists themselves are still people, and Ruby prices itself accordingly.

The catch is the price and the way it is measured. Ruby bills by the receptionist minute, rounds every call up to the next full 60 seconds, and starts its cheapest plan at $250 a month for just 50 of those minutes. That combination, a premium live-agent price plus a rounding rule most competitors do not advertise up front, is the single biggest driver of the negative reviews below. This review walks through Ruby's actual 2026 billing-plan schedule pulled directly from its own help center, what verified users on three different review platforms say once the novelty wears off, and who actually gets their money's worth.

Ruby pricing in 2026: the full billing-plan ladder

Ruby publishes ten standard Call Ruby plans, each defined by a base monthly fee, an included block of receptionist minutes, and a per-minute overage rate that gets cheaper as the plan gets bigger. The numbers below come directly from Ruby's own billing reference page, last updated December 11, 2025.

[Ruby Help Center, "Am I on the right billing plan?", updated December 11, 2025]

The pattern is consistent across every tier: committing to more minutes upfront buys a lower rate on whatever you go over. A business on the entry Call Ruby 50 plan pays $5.40 for every minute past its included 50, while a business on Call Ruby 500 pays $4.00 for the same overage minute, a 26 percent discount for committing to ten times the volume. Ruby also sells a separate Chat Ruby product line for website live chat, priced independently, and offers a 20 percent bundle discount when a customer buys both receptionist and chat service together.

Every new account gets a 21-day money-back guarantee, capped at the first 500 billable minutes or 50 billable chats, whichever comes first, so a business that signs up for a small plan and burns through its guarantee window quickly loses that safety net faster than one on a larger plan. Ruby also builds in a three-billing-cycle calibration window at the start of an account during which plan changes are unrestricted; after that window, upgrades can happen anytime but downgrades require three consecutive billing periods on the same plan first [Ruby Help Center, "Am I on the right billing plan?", updated December 11, 2025].

The 60-second rounding rule, and what actually gets billed

The detail most comparison articles skip is how Ruby defines a "receptionist minute" in the first place, and it changes the real cost of a plan. Per Ruby's own billing documentation, receptionist time starts the moment a receptionist picks up the call and continues until the receptionist transfers the caller, sends them to voicemail, or otherwise ends the interaction, including any time the receptionist spends afterward logging notes about the call. Hold time counts too: if a receptionist puts a caller on hold to check something, that hold time is billed the same as active talk time [Ruby Help Center, "Ruby Billing Basics", updated February 9, 2026].

Ruby does not bill by the second. Every call is rounded up to the next full 60-second mark, so a call that lasts eleven seconds is billed as a full minute, and a call that runs one minute and five seconds is billed as two minutes [Ruby Help Center, "Ruby Billing Basics", updated February 9, 2026]. For a business that gets a steady stream of short calls, wrong numbers, quick scheduling confirmations, callers who hang up after a few seconds, that rounding adds up faster than the headline per-minute rate suggests. Ruby does carve out clear exceptions: calls under ten seconds are not billed at all, and neither are calls that arrive outside your configured live-answering hours, calls made through the Ruby mobile app, or calls to Ruby's own Customer Happiness team.

This is also the mechanic behind one of the more common complaints in Ruby's own review history: businesses getting nudged toward a plan upgrade because their minute usage crept past what a small plan can absorb, often driven by call volume the business itself did not generate, like automated spam or robocalls that get forwarded into the account before anyone screens them out.

What verified reviews actually say

Ruby's review profile looks different depending on which platform you check, and the gap is wide enough that it deserves its own explanation, not a single blended average.

On G2, Ruby Receptionists holds 3.8 out of 5 across just 12 reviews (3 five-star, 6 four-star, 3 three-star, and no ratings below that) [G2, checked 2026-08-11]. On Capterra, the aggregate is 4.2 out of 5 from 10 reviews, but the category breakdown is the more useful number: Ease of Use scores 4.2, Customer Service 4.1, Features 4.2, and Value for Money trails the rest at 3.8, the same pattern showing up independently on a completely different platform [Capterra, checked 2026-08-11].

Trustpilot tells a more favorable story at much larger scale: 4.6 out of 5 across 848 reviews, rated "Excellent," with 84 percent five-star, 8 percent four-star, 3 percent three-star, 1 percent two-star, and 4 percent one-star, and 35 of those reviews posted in the last 12 months [Trustpilot, checked 2026-08-11]. That skew toward five-star ratings is common on Trustpilot for companies that actively solicit reviews from their full customer base, not just from people motivated enough to seek out a review site on their own, and Ruby's own profile confirms it invites customers to review whether the feedback is positive or negative.

The satisfied reviews tend to describe a real cost tradeoff against hiring in-house. Kevin Conrad, a Trustpilot reviewer, put it plainly: "I used to pay my secretary $110,000 a year to answer my business line. Now i pay Ruby about $6000 a year for 24/7 answering service" [Trustpilot, review posted Jul 18, 2026]. That comparison only holds for businesses with light call volume relative to a full-time hire, since Ruby's per-minute pricing scales up fast once volume grows past what a low tier covers. Cathi Foster, another Trustpilot reviewer, described Ruby as consistently routing callers "to the correct individual" and called it the best customer support service her business has used [Trustpilot, review posted Jul 9, 2026].

Where it falls apart: robocalls, plan-upgrade pressure, and Ruby's response

The clearest negative pattern in Ruby's own review history is the interaction between the rounding rule above and calls a business never wanted answered in the first place. Tara Melling, a Trustpilot reviewer, wrote that Ruby "tell[s] you to move your call plan up when you reach your threshold of time" while she was "getting lots of robo calls that they do nothing about until you confront them with the issue," and argued Ruby should not profit from minutes spent on spam calls forwarded to its receptionists [Trustpilot, review posted Aug 1, 2026].

Ruby replied directly to that review, and the reply explains the actual policy rather than leaving it to guesswork: "we cannot prevent or eliminate robocalls made to your business telephone number that are subsequently forwarded to our service. Those calls originate outside of our control. To help minimize their impact, we provide all clients with a robocall blocking feature at no additional charge" [Ruby, reply to Tara Melling review, Trustpilot, checked 2026-08-11]. In other words, the free robocall filter exists and can be turned on, but it is opt-in rather than the default, and a business that skips setting it up during onboarding can end up paying overage minutes on calls it never wanted answered.

The plan-upgrade mechanic compounds this. Ruby proactively monitors usage and recommends a bigger plan once a business consistently runs over, which the company frames as helping customers avoid a high per-minute overage rate. From the customer's side, though, that recommendation can arrive because of call volume the business did not create, and the three-consecutive-billing-period rule for downgrading means a business that upgrades during a temporary spike, robocalls, a seasonal rush, a marketing campaign, is committed to the higher base fee for at least three months before it can step back down.

Who it is best for, and who should skip it

Ruby fits a business that wants a warm, consistent, US-based human voice answering the phone, has HIPAA or client-confidentiality requirements that make a signed Business Associate Agreement valuable (Ruby offers one), and has predictable, moderate call volume it can match to one of the ten published tiers without guessing. Law firms, healthcare practices, and professional services firms that show up repeatedly in Ruby's own case studies and reviews match that profile well.

Skip it if your monthly budget is tight and your call volume is low. At $250 a month for 50 minutes with a $5.40 overage rate, Ruby is priced well above budget-focused live answering services, and our answering service pricing comparison lays out how that overage rate stacks up against PATLive, Smith.ai, and AnswerConnect once you do the math on your average call length. Skip it too if your call volume swings unpredictably month to month, since Ruby's tiers are built around a stable average rather than rolling unused minutes forward; our best answering services roundup covers alternatives with lower entry points and different billing units to compare before committing.

Most Ruby customers connect the service the same way: forwarding their existing business number to Ruby and skipping a full number port, so calls route to a live receptionist without changing the number printed on a business card or Google listing. If you have not set up call forwarding before, our guide to business call forwarding covers the setup, testing, and overflow rules to check before going live with any answering service, Ruby included.

Frequently asked questions