I Switched from Ruby Receptionists to an AI Receptionist — Here's What Happened

This is the story of a switch. Not a hypothetical comparison table — a real, week-by-week account of what happens when a mid-size HVAC and plumbing company moves from Ruby Receptionists to Capta's AI receptionist, Maria.

We're not going to pretend Ruby is bad. They're not. Their human receptionists are professional, friendly, and have served thousands of businesses well. But after 14 months on Ruby's 200-minute plan at $780/month, the math stopped working. Here's what happened when we made the change.

The Setup: Why We Were Looking

Let's start with the numbers that made us start shopping.

Our Ruby bill for the previous six months averaged $943/month. The base plan was $780 for 200 minutes, but we consistently ran over. Our average call is about 4 minutes — booking a service appointment, answering a question about whether we service their area, handling an after-hours emergency. At roughly 80-100 calls per month during normal season, we were burning through 200 minutes fast.

Then summer hit. June: $1,247. July: $1,389. August: $1,156. Three months where our phone costs exploded because business was good. We were being punished for our busiest, most profitable season.

The other issue: after-hours coverage. Ruby's standard plan covers business hours. We added extended hours, which bumped our base cost. But even with extended hours, we were missing calls at 10 PM, 11 PM, midnight — exactly when emergency plumbing calls come in. A burst pipe at midnight is worth $800-$1,500 to us. A missed midnight call is worth $0.

The final push was a Spanish-speaking customer who called three times, couldn't communicate with the Ruby receptionist, and eventually called our competitor instead. We found out because the customer later told our neighbor they'd tried to call us first. That job was a $2,200 water heater replacement.

Week 1: The Switch

Monday morning. We signed up for Capta at 6:47 AM before heading to a job site. The 8-step setup wizard took about 5 minutes. Business name, services we offer (HVAC and plumbing), service area, business hours, emergency protocols. We forwarded our number to Capta's line.

Maria started answering calls at 7:02 AM.

The first surprise: no training period. With Ruby, we'd spent two weeks going back and forth on scripts, call handling preferences, and FAQs before the receptionists were comfortable. Maria already knew HVAC and plumbing terminology. When a caller said "my AC is blowing warm air," Maria knew to ask about the model, how long it's been happening, and whether all vents were affected. We didn't program those questions. She just knew them.

First call: A homeowner needed a faucet repair. Maria booked the appointment, confirmed the time slot, and sent an SMS confirmation to the customer. We got a notification. Total time from ring to confirmed booking: about 90 seconds.

With Ruby, the receptionist would have taken the customer's info, emailed us, and we'd have called back to confirm. That loop usually took 2-4 hours, and sometimes the customer booked with someone else in the meantime.

Tuesday: 11 calls. Maria handled all of them. We spotted one issue — she offered a Wednesday morning slot that conflicted with an existing job. We adjusted the availability settings in the dashboard. Took 30 seconds. The rest of the week was seamless.

Friday night, 10:47 PM: A caller reported a burst pipe in their kitchen. Maria flagged it as an emergency, offered to transfer the call live, and sent us an urgent alert. We called back within 3 minutes. The customer later told us they'd almost called someone else but were impressed that "someone" answered on a Friday night.

Week 1 stats: 47 calls, 12 appointments booked, 1 emergency handled. Cost: $0 extra (covered by the $497 flat rate). What those same 47 calls would have cost on Ruby: approximately $752 in minutes alone, before overages.

Week 2: The Spanish Calls

Here's where things got interesting.

We serve a part of town with a large Hispanic community. On Ruby, we'd occasionally get Spanish-language calls, and they'd go poorly. The receptionist would try to help, sometimes transfer to us (interrupting a job), or the caller would just hang up.

Wednesday, Week 2: Maria answered a call in Spanish from a homeowner whose water heater wasn't producing hot water. The conversation was entirely in Spanish. Maria asked the right diagnostic questions, booked a same-day appointment, and sent the SMS confirmation in Spanish. We showed up, diagnosed a failing thermocouple, and completed the repair for $450.

That's $450 in revenue from a single call that Ruby couldn't have handled.

Over the next two weeks, we received 9 Spanish-language calls. Maria handled all 9. Four became booked jobs totaling $2,100 in revenue. That's $2,100 that, for the past 14 months on Ruby, we'd been leaving on the table.

To be fair to Ruby: bilingual reception isn't their core offering. They serve all industries, and their English-language service is genuinely good. But for our market, the bilingual gap was costing us real money.

Week 3: The Dashboard Effect

Something we didn't expect: the CRM and analytics dashboard changed how we thought about our business.

Ruby sent us call summaries by email. They were fine — caller name, number, reason for calling. But they were just messages. There was no trend analysis, no patterns, no big picture.

Capta's dashboard showed us things we'd never known:

• 34% of our calls came after 5 PM. We'd always assumed our phone was busiest during business hours. It wasn't. Over a third of our inbound calls were coming in the evening and on weekends — exactly when Ruby's standard coverage was limited or absent.

• Drain cleaning was our most-requested service. We'd been spending our marketing budget emphasizing AC repair. But the data showed drain cleaning calls were outpacing AC calls 3-to-1 in the shoulder season. We shifted some ad spend and picked up 6 more drain jobs the following month.

• Our average response time to voicemails had been 3.2 hours. We didn't have this metric before. With Maria booking directly, response time became zero — the appointment was confirmed during the call itself.

These insights didn't come from Capta's marketing materials. They came from actually using the dashboard. Ruby simply didn't offer this level of visibility into our phone operations.

Week 4: What I Miss About Ruby (Honest Assessment)

A month in, here's what Ruby did better:

Complex, emotionally charged conversations. We had one caller who was upset about a previous job (not ours — a different contractor had done poor work, and she called us for a second opinion). She was frustrated, venting, and needed to feel heard before she'd trust anyone new. A human receptionist would have handled the emotional nuance better. Maria was professional and empathetic, but the caller later mentioned she "could tell it was a computer." For 95% of our calls, this doesn't matter. For this 5%, it does.

Highly unusual requests. One caller wanted to know if we could install a commercial-grade exhaust system in a residential kitchen for a home bakery. That's a niche question that required back-and-forth about local codes, ductwork modifications, and whether we even offer that service. Maria captured the request accurately and flagged it for our review, but she couldn't have the improvisational conversation a human would.

These are real limitations. If your business gets a high volume of complex, emotionally sensitive calls, human receptionists still have an edge. But for our business — where 90% of calls are "I need service X at my address, when can you come?" — the tradeoff is overwhelmingly in AI's favor.

The Numbers After 30 Days

The cost savings alone were $446/month — $5,352 annually. But the revenue captured from after-hours calls, Spanish-language calls, and instant booking was worth far more than the savings.

A conservative estimate: the 4 Spanish-language jobs ($2,100), 8 additional after-hours jobs (~$4,800), and reduced no-shows from SMS confirmations (3 saved appointments worth ~$1,200) added roughly $8,100 in revenue during the first month that we wouldn't have captured on Ruby.

Would I Switch Back?

No. And I say that while genuinely respecting what Ruby built. Their human receptionists are professionals. If I ran a law firm or a medical practice — somewhere calls are complex, sensitive, and low-volume — I'd probably choose Ruby.

But I'm a contractor. My phone rings 20-30 times a day. Calls come at midnight. A third of my customers speak Spanish. And every missed call is a missed job worth $200-$1,500.

For that reality, Capta is the clear choice. The flat $497/month means my busiest months are my cheapest months per call. Maria speaks my customers' language. She books appointments before I even check my phone. And she never calls in sick.

If You're Considering the Same Switch

Here's my advice:

Stay with Ruby if your call volume is under 15 calls per month, you don't need after-hours coverage, your customers are exclusively English-speaking, and you value human voice above everything else. Ruby is excellent at what they do. They're just not built for the trades.

Switch to Capta if you're missing calls, missing jobs, or missing an entire segment of your market because of language barriers. The 30-day money-back guarantee means you can try it with zero risk — run both services in parallel for a month if you want to compare them directly.

The setup takes 5 minutes. I did it from my truck before a 7 AM job. Maria was answering calls before I finished my coffee.

Ready to make the switch? Capta offers a 30-day money-back guarantee. Maria answers every call, books appointments, speaks English and Spanish, and never charges you extra for a busy month. Get Capta →