Ruby Review 2026: Are Live Receptionists Worth the Premium Over AI?

What Ruby Actually Is — And Why It’s the Odd One Out in This Category

Ruby is the only service in our AI call answering category that doesn’t use AI to talk to your customers. Real humans pick up the phone. Real humans have the conversation. Real humans take the message, schedule the appointment, and send you the summary.

That distinction matters a lot more than it sounds like on paper.

Every other answering service we cover — Rosie, Upfirst, Smith.ai, Goodcall — runs your calls through AI voice models, speech synthesis, or some combination of the two. Ruby takes the opposite approach entirely. They have roughly 700 US-based receptionists who answer calls for over 14,000 small businesses across the country. When your customer calls, they get a warm, professional person on the other end who already knows your company name, your services, and exactly how you want calls handled.

Ruby has been doing this since 2003. They started in Portland, Oregon with four receptionists and a handful of clients, and grew into one of the most recognized virtual receptionist brands in the US. They were at this for nearly two decades before AI answering services even existed as a category.

So why are they in our AI call answering roundup at all? Two reasons. First, they do use AI behind the scenes — for transcription, sentiment analysis, and feeding receptionists real-time information during calls. The humans talk, the AI assists. Second, any contractor comparing their call answering options needs to see Ruby side-by-side with the AI alternatives to make an informed decision. The question isn’t whether Ruby is a good product. The question is whether Ruby is worth 5-10x more than the AI competition.

That’s what this review is going to answer honestly.

Full disclosure: I haven’t run my business lines through Ruby’s service yet. This review is built from detailed research of their help center documentation, pricing pages, Zapier integration specs, customer reviews across Trustpilot (834 reviews), G2, and Capterra, and direct analysis of their platform capabilities. Where I’m drawing conclusions from research rather than personal experience, I’ll tell you.

How Ruby Handles Your Calls From Start to Finish

Here’s the actual call flow when you sign up.

Setup and onboarding. You tell Ruby how you want your calls handled — your company greeting, what questions to ask, how to prioritize different call types, when to transfer and when to take a message, and any specific instructions for different scenarios. For a roofing company, that might mean: always ask about roof type, always ask if it’s insurance work, transfer emergency leak calls immediately, take a message for everything else. For HVAC: ask about system type and age, transfer “no heat” calls directly to the on-call tech, schedule routine maintenance requests.

This setup process is more involved than AI competitors. Rosie scans your Google Business Profile and has you live in minutes. Upfirst takes about 15 minutes. Ruby’s onboarding typically takes longer because you’re training real people, not configuring a bot. Some users report it taking a week or two to get the call handling dialed in. That upfront investment is the tradeoff for having actual humans who understand context and nuance.

When a customer calls. Your business number forwards to Ruby. A live receptionist picks up within a few rings and greets the caller by your company name — “Thanks for calling Apex Roofing, this is Sarah, how can I help you today?” The receptionist handles the conversation based on your call handling instructions, asks the intake questions you defined, and takes the appropriate action: transfers the call to you, takes a detailed message, schedules an appointment, or even collects a payment.

During the call. This is where the human advantage shows up. A homeowner calls your HVAC company at 7 PM, clearly stressed because their furnace just died in January. An AI agent handles the information capture just fine. But a human receptionist hears the worry in their voice, reassures them that you have on-call technicians, and transfers the call with context: “I have Mrs. Johnson on the line, her furnace just stopped and she has two small kids in the house. She’s at 1247 Oak Street.” That warm handoff with situational awareness is something AI still doesn’t do well.

Ruby can also make outbound calls on your behalf — confirming appointments, following up with leads, or returning missed calls. They’ll call from your business number so the customer sees your company name on their caller ID, not some unfamiliar number.

After the call. You get a notification via the Ruby mobile app, email, or text. The notification includes who called, what they needed, the receptionist’s notes, and what action was taken. Full call recordings and AI-generated transcripts are available in the app. Every call is documented with searchable records.

Ruby’s Complete Feature Set: What Your Money Actually Buys

24/7 Live Human Answering

Every call answered by a US-based receptionist, 365 days a year, including weekends and holidays. No hold music, no phone trees, no “press 1 for scheduling.” A real person picks up. For contractors in trades where emergency calls happen at all hours — HVAC, plumbing, electrical — having live humans available at 2 AM on Christmas Day is a genuine differentiator that none of the pure AI services can claim to match on call quality.

Bilingual English/Spanish Support

Ruby provides bilingual receptionists who can handle calls in English and Spanish. This matters for contractors in markets with substantial Spanish-speaking populations — painting, landscaping, general construction, and roofing crews in the South and Southwest especially. One thing to know: bilingual availability may not be 24/7 on all plans. AI services like Rosie offer bilingual support on every plan at all hours, and Upfirst goes further with 35+ languages.

Appointment Scheduling and Calendar Integration

Receptionists can book appointments directly into your calendar. Ruby integrates with Google Calendar and Microsoft Outlook natively. The receptionist checks your availability, proposes times to the caller, and confirms the booking — all during the call. No phone tag, no “I’ll have someone call you back.” For a contractor whose pipeline depends on getting estimates scheduled fast, this closes the gap between “interested caller” and “appointment on the books.”

Payment Collection (PCI Compliant)

Ruby receptionists can take credit card payments over the phone — deposits, invoice payments, service fees. They’re PCI DSS compliant, so card data is handled securely. This is a feature none of the AI answering services in our category offer. If you’re a contractor who collects deposits before scheduling work or takes final payments over the phone, Ruby can handle that call-to-cash workflow without you being involved.

HIPAA Compliance

Ruby is HIPAA compliant at no extra charge. You sign a Business Associate Agreement, and messages for HIPAA-covered calls get delivered through secure channels rather than standard email or text. This matters for contractors doing work in medical facilities, or for any scenario involving sensitive patient or insurance information. None of the pure AI competitors advertise HIPAA compliance.

Call Recording, Transcription, and Voicemail

Every call gets recorded with AI-powered transcription. Recordings and transcripts are searchable in the Ruby app. You also get unlimited voicemail boxes with custom greetings and voicemail transcription. If a call comes in outside your live answering hours (if you’ve set limited hours instead of 24/7), it goes to voicemail — and you still get a transcription delivered to your phone.

Spam and Robocall Filtering

Robocalls get automatically routed to voicemail rather than answered by a live receptionist. That means spam calls don’t eat into your paid minutes. On a per-minute billing plan where every second counts, this matters.

The Ruby Mobile App: Managing Calls From the Job Site

Ruby has a dedicated mobile app for iOS and Android — the “Ruby 2.0” app. For contractors who live on their phones between job sites, this is meaningfully better than the web-dashboard-only approach that Upfirst, Smith.ai, and Goodcall offer.

What the app does:

• Set your availability status — Toggle between available and unavailable so receptionists know whether to transfer calls to you or take messages. Heading into a client meeting? Set to unavailable. Back in the truck? Toggle back.
• View all call activity — Full call records, messages, voicemail transcriptions, and call recordings in one place. Searchable. Need to find what that customer said about their crawlspace access yesterday? It’s in the app.
• Make outbound calls showing your business number — Call a lead back from your cell, but they see your business number on their caller ID. Professional. No “who’s calling from this random number?” confusion.
• Send and receive SMS from your business number — Text a customer a scheduling link, your license number, or a photo of something without giving out your personal cell.
• Track minute usage — See how many minutes you’ve used and how many remain in your billing period. Critical for avoiding bill shock on a per-minute plan.
• Request outbound call assists — Ask Ruby to make a call on your behalf — confirming an appointment, following up with a lead, returning a missed call.

The app also includes push notifications for every call, so you see who called and what they needed in real time. One tap calls them back. That’s the same workflow Rosie offers in their app, but with the added functionality of outbound calling and SMS.

Ruby’s Live Chat: A Separate Product Worth Knowing About

Beyond phone answering, Ruby offers a live chat service — human chat specialists (not chatbots) who respond to website visitors within about a minute. They capture leads, qualify visitors, answer questions, and schedule appointments, all through a chat widget on your site.

Chat pricing is separate from the phone plans:

If you bundle chat with a phone plan, you get 20% off chat pricing. The bundled Chat Ruby 10 drops to $114.40/month. Bilingual chat (English/Spanish) is available during business hours.

For contractors whose websites get decent traffic, live chat can capture leads that would otherwise bounce. But at $143/month for just 10 chats, the economics are steep. A tool like Tidio starts free and handles basic chat with AI. Rosie’s Website Texting add-on is $50/month for 25 AI text conversations. Ruby’s chat product is the premium human option — effective, but expensive.

Ruby Pricing: What You’ll Actually Pay (And Why It Gets Complicated Fast)

This is where the conversation about Ruby gets real for contractors.

Phone Plan Breakdown

Plans scale up to 2,500 minutes ($7,875/month) for high-volume operations. Month-to-month billing, no long-term contracts.

The Billing Details That Matter

60-second rounding. Every call is rounded UP to the nearest 60 seconds. A 10-second call — someone dialing the wrong number, a quick “I’ll call you back” — costs you a full minute. On the 50-minute plan, that’s $5.00 gone. This rounding adds up fast, especially for contractors who get a lot of short calls.

What’s billable. You’re charged for: time from when the receptionist picks up until the call ends, any post-call documentation time, hold time (including time the caller spends on hold), and outbound call assists plus follow-up emails. You’re NOT charged for calls under 10 seconds, calls outside your live answering hours, calls made through the Ruby app itself, or calls to Ruby’s support team.

No rollover. Unused minutes at the end of your billing period are gone. If you buy 200 minutes and use 130, those 70 minutes don’t carry forward. This is a meaningful cost issue for contractors whose call volume varies month to month — slow in winter, slammed during storm season.

New customer calibration. For your first 3 billing cycles, Ruby lets you upgrade or downgrade plans freely so you can find the right fit. After that, downgrades require you to stay on your current plan for 3 consecutive billing periods before you can move down. Upgrades are always immediate.

What This Actually Costs a Typical Contractor

Let’s run the numbers for a few scenarios.

Solo roofer, 5-8 calls per day: Average call length of 3-4 minutes means you’re burning through 15-32 minutes per day. That’s 300-640 minutes per month. You need the Call Ruby 350 ($1,210/mo) minimum, and during storm season you’ll likely hit overages. Realistic monthly cost: $1,200-$1,800.

Small HVAC crew, 10-15 calls per day: At 3-4 minutes average, that’s 600-900 minutes per month. You need the Call Ruby 500 ($1,725/mo) or higher. Realistic monthly cost: $1,725-$2,500+.

Compare that to the AI alternatives:

• Upfirst: $24.95-$159.95/mo for 30-300 calls
• Rosie: $49-$299/mo for 250-2,000 minutes
• Smith.ai AI Receptionist: $95/mo Starter (~60 calls included)
• Smith.ai Hybrid (AI + human): $292.50/mo for 30 calls
• A full-time in-house receptionist: $3,000-4,000/mo with benefits

Ruby sits in an awkward middle ground — significantly more expensive than AI, but less expensive than hiring someone full-time. The question is whether the human quality premium justifies the 5-10x cost increase over AI.

A Note About Ruby’s Billing History

In 2021, Ruby settled a class action lawsuit for $12 million over billing practices. The core allegations: Ruby was charging clients for hold time (time callers spent waiting, caused by Ruby’s own understaffing) and rounding minutes up in their favor without adequate disclosure. Neither practice was clearly communicated to customers before they signed up.

Ruby has presumably addressed these specific practices since the settlement. But it’s worth knowing about when you’re evaluating a service that bills per minute with rounding. Track your minutes carefully during any trial period, and compare your billed minutes against your actual call activity.

Ruby Integrations: Where the Contractor Gap Is Real

This is Ruby’s biggest weakness for contractors specifically. Their integration ecosystem was built for law firms and general small businesses, not for the trades.

What Connects Natively

• Clio — Deep legal CRM integration. Great if you’re a lawyer. Not relevant for contractors.
• Salesforce — Contact and communication sync. Overkill for most contractor operations.
• HubSpot — Marketing CRM connection. Some contractors use HubSpot, but it’s not trade-specific.
• Grasshopper — Phone system partnership for call routing.
• Nextiva — Another phone system integration.
• Google Calendar — Appointment scheduling.
• Microsoft Outlook — Calendar integration.

What Connects Through Zapier

Ruby’s Zapier integration is notably limited. You get:

• 1 trigger: “Message” — fires when a receptionist takes a message
• 2 actions: “Create Contact” and “Create Email Assist”

That’s it. Compare that to Rosie, which offers 3 Zapier triggers (new call, new booking, updated call). Ruby’s single trigger means you can push new messages to downstream apps, but you can’t trigger automations on appointment bookings, call transfers, or other call events separately.

Through Zapier, you could route Ruby messages to Slack, Google Sheets, or any of 8,000+ apps. But the single trigger severely limits what you can automate.

What’s Missing for Contractors

No native integration with any contractor CRM. ServiceTitan, Jobber, Housecall Pro, JobNimbus, AccuLynx — none of them connect to Ruby directly. Every contractor CRM connection requires Zapier as a middleman, adding cost ($20+/month) and limiting data flow to what Ruby’s single Zapier trigger provides.

Compare that to Upfirst, which lists native direct connections to ServiceTitan, Housecall Pro, Jobber, JobNimbus, and AccuLynx. Or Smith.ai, which has direct Housecall Pro and ServiceTitan integrations. Ruby’s integration story is genuinely behind the curve for the contractor market.

No QuickBooks integration. Not directly, and not through a clean Zapier path. If you want call data flowing into your accounting workflow, it’s a multi-step manual process.

No CompanyCam or photo documentation connection. Not relevant to call answering directly, but worth noting that Ruby exists in isolation from the rest of a contractor’s tech stack.

Can Ruby Plug Into AI Agent Workflows or Custom Automation?

Short answer: no. Long answer: really, no.

Ruby has no public REST API documentation. No native webhook system. No way to feed real-time call data into an LLM, pipe transcripts to a Claude-based agent, or build any kind of custom integration without Zapier sitting in the middle. And even Zapier gives you just one trigger and two actions — the bare minimum.

What you could technically build: A Zapier automation that pushes every new Ruby message to a Google Sheet or webhook endpoint. From there, a downstream system — maybe a Claude prompt, a custom GPT, or an n8n workflow — could read the call summary and draft a follow-up email. But you’re limited to the data Ruby’s single “Message” trigger passes (caller name, phone number, message text), and there’s Zapier latency (1-15 minutes depending on your Zapier plan) between the call ending and your automation firing.

What you can’t build: Anything that interacts with Ruby in real time during a call. Anything that pulls structured call data via API. Anything that triggers different automations for different call types. Anything resembling a modern agentic workflow where the answering service is one node in a larger automated pipeline.

If agentic integration matters to you — and for contractors building AI-automated operations, it increasingly does — Ruby is the wrong tool for that job. Smith.ai offers broader API access and more Zapier triggers. Upfirst and Rosie both provide multiple Zapier triggers that give you more granular automation options. And if you want full programmatic control over voice AI, developer-focused platforms like Bland.ai or Vapi let you script the entire call flow and feed data directly to your own systems.

Ruby is designed for business owners who want to forward their phone and forget about it. If that’s you, the lack of API access doesn’t matter. If you’re thinking about building AI workflows around your phone system, look elsewhere.

What 834 Real Customers Are Saying About Ruby

Ruby has more public review data than any other service in our AI call answering category, which makes sense — they’ve been around since 2003 while most competitors launched in 2021-2023.

The Numbers Across Platforms

What People Love

The consistent praise centers on call quality. Users describe Ruby receptionists as sounding like “internal employees” — callers can’t tell they’re talking to an outsourced service. One business owner wrote that after switching to Ruby, they achieved a 100% answer rate on their main line for the first time in the company’s history. Multiple reviews specifically praise the professionalism, friendliness, and accuracy of the receptionists.

A contractor who left a testimonial on Ruby’s site said it well: the service allows them to have phone coverage while they’re out in the field on job walks, with scripts tailored to their market. The receptionists gather all the information needed to go straight to creating estimates.

Where the Complaints Land

Price is the #1 complaint. Capterra’s Value for Money sub-rating is 3.8/5 — the lowest sub-score on the platform. One Capterra reviewer called it “unbelievably overpriced” and described paying $650/month for 200 minutes while competitors offered 350 minutes for $250-$400. Multiple reviewers report bill shock when overage charges hit.

Billing concerns persist. Beyond the class action settlement, individual reviewers report being billed for dead air, dropped calls, and hang-ups. The 60-second rounding means even non-conversations eat into your minutes. One reviewer reported that their expected $660 monthly bill ballooned unexpectedly when call volumes shifted during busy season.

Quality may be declining. Some recent reviews suggest a shift in call quality, with receptionists not following FAQ guidelines or scripts as closely as they used to. One reviewer rated the onboarding and sales experience highly but gave actual call handling execution a significantly lower score. Employee review sites show declining receptionist satisfaction, which can translate to higher turnover and less experienced agents handling your calls.

The Nexstar Connection

Ruby has a partnership with Nexstar Network — one of the largest contractor training and networking organizations in North America. They have a dedicated landing page for Nexstar members, which suggests an established relationship with the contractor industry. If you’re a Nexstar member, there may be preferred pricing or features available through that channel.

Who Ruby Is Built For (And Who Should Save Their Money)

Ruby makes sense if:

• Your average job value is $10,000+ and a fumbled first impression literally costs you five-figure contracts
• Your callers frequently have complex, emotionally charged conversations — insurance disputes, multi-phase renovation discussions, warranty complaints — where human empathy matters
• You need HIPAA compliance for calls related to medical facilities or sensitive insurance documentation
• You want payment collection on calls — taking deposits or invoice payments while the customer is on the phone
• You’re a larger operation (10+ employees) with established revenue where $1,000-2,000/month for phone answering is a rounding error in your overhead
• You value phone presence as a core part of your brand — your company’s phone experience is a competitive differentiator
• You’re a Nexstar member and can access preferred pricing through that relationship

Ruby probably isn’t right if:

• You’re a solo operator or small crew watching every dollar. At $250/month for 50 minutes, you’re paying more for phone answering than most contractors pay for their CRM.
• Most of your calls are straightforward — scheduling, estimates, service area questions, hours of operation. AI handles these at $25-$49/month and your callers won’t know the difference on 80-90% of those conversations.
• Your call volume spikes seasonally. Per-minute billing with no rollover means you’ll overpay during slow months and get hammered with overages during busy months. AI services with flat-rate or per-call pricing handle volume fluctuations much more gracefully.
• You need your answering service to talk to your CRM. Ruby has zero native contractor CRM integrations. Upfirst connects natively to ServiceTitan, Jobber, Housecall Pro, JobNimbus, and AccuLynx.
• You’re building any kind of AI-powered automation around your phone system. Ruby’s API and integration capabilities are among the weakest in the category.
• You want the cheapest option that works. Upfirst at $24.95/month and Rosie at $49/month both deliver solid call answering at a fraction of the cost.

Ruby vs the Field: Live Humans vs AI Answering

The bottom line on Ruby vs AI: Ruby’s human receptionists deliver a caller experience that AI can’t match — yet. The warmth, the contextual understanding, the ability to de-escalate an upset homeowner — those are real advantages. The question is math. If you’re paying $1,200/month for Ruby and recovering 2-3 jobs per month that AI would have lost, Ruby pays for itself. If AI handles your call mix just as well and costs $49-$97/month, you’re burning $1,100/month on premium call quality your customers don’t actually need.

For most contractors, starting with an AI service and upgrading to Ruby only if AI proves inadequate is the smarter financial path.

The Bottom Line on Ruby

Ruby is the gold standard for call quality. Nobody else in this category puts a trained, empathetic, US-based human on every single call, 24/7, 365 days a year. For the right contractor — one with high-value jobs, complex caller needs, and the revenue to absorb $1,000+/month in answering costs — it’s worth every penny.

But that contractor is a minority of the people reading this review.

For most contractors — solo operators, small crews, growing businesses watching their margins — the AI answering services have caught up enough that the human premium no longer pencils out. Rosie at $49/month handles 80-90% of contractor calls just fine. Upfirst at $24.95/month with native contractor CRM integrations is the easiest first step. Smith.ai offers a hybrid model where AI handles most calls and a human steps in when it matters.

Ruby’s other challenges — the per-minute billing that punishes busy seasons, the 60-second rounding, the lack of contractor CRM integrations, the extremely limited API, and the billing history — are real considerations that compound the cost issue.

If you’re seriously considering Ruby, run their 14-day trial alongside a free trial of Upfirst or Rosie. Forward the same types of calls to both for two weeks. You’ll know fast whether the human difference matters enough for your callers to justify the premium. For many contractors, the answer will be no — and that’s $1,000+/month you can spend on marketing that generates more calls in the first place.

Frequently Asked Questions