If you have shopped virtual receptionists lately, Ruby is probably on the list. Owners we talk to put it next to Smith.ai and Posh as the live-person option.
Ruby is good at that job. US-based receptionists. 24/7 coverage. A polite pickup instead of voicemail.
Restoration is a different job. A water loss at 1am is not a dental office trying not to miss a new-patient call. The next sixty seconds decide whether a crew is rolling, a CRM job exists, and a TPA assignment is even recognized.
That is the comparison that matters. Not who sounds friendlier on the first ring.
What Ruby actually is
Ruby Receptionists is a live virtual receptionist company. They have been doing this for more than twenty years, mostly for small businesses that want a human at the front desk without hiring one.
Their own site is clear about the product. 24/7 live answering, including weekends and holidays. Optional bilingual coverage. Scheduling. Lead intake. AI-powered transcripts and sentiment analysis as add-on enhancements, not the core service.
Pricing is per minute. As of mid-2026 on ruby.com, plans start at $250 a month for 50 receptionist minutes, then $395 for 100, $720 for 200, and $1,725 for 500. The 200-minute plan is the one they mark as most popular.
That model works for a law firm or a clinic with a handful of inbound calls. A restoration shop in a storm week will chew through those minutes before lunch on Saturday. And every extra minute is still just a receptionist minute. It does not become a job file.
Why restorers shop Ruby in the first place
The search terms that already bring people to Hank tell the same story. Queries like restoration answering service and best phone answering service for emergency restoration show up in Search Console with impressions and almost no clicks. People are shopping coverage. They are not shopping a CRM workflow.
Ruby looks like the answer to that shopping trip. A real person. After hours. No voicemail.
The owners who later replace that setup rarely complain that nobody picked up. They complain that the pickup did not know water from mold, dumped a paragraph into email, and left someone on the team to retype it into Dash or Albi in the morning.
If you already read our post on why generic answering services miss restoration jobs, this is the branded version of that gap. Ruby is one of the better generalists. The gap is still the industry.
Where a live receptionist stops on a restoration call
None of this is a knock on Ruby's receptionists. It is a list of things their product is not built to do.
- Tell active water from old mold growth without a restoration script you have to maintain yourself.
- Recognize a TPA or carrier caller and capture claim number, policy number, and program rules.
- Write a structured job into Albi, DASH, Proven, or Xcelerate instead of an email summary.
- Live-transfer a true emergency into your on-call chain without burning the homeowner in a slow handoff.
- Turn a Contractor Connection assignment email into a CRM job at 11pm.
- Keep a timestamped recording that matches what the TPA scorecard thinks happened.
The side-by-side
Two products that both answer the phone. Completely different outputs.
Capability
Ruby Receptionists
Hank
- Built for
- Small businesses across many industries
- Insurance-backed trades, restoration first
- Who answers
- Live US receptionists, with optional AI extras
- Voice AI trained on water, fire, mold, and storm calls
- Core deliverable
- A handled call, message, or transfer
- A qualified job, routed and documented
- Pricing
- Per-minute plans from $250/mo for 50 minutes
- Platform relationship, not metered receptionist minutes
- CRM output
- Notes and notifications, not a restoration job file
- Job written into restoration CRMs in real time
- TPA / insurance intake
- Only if you train a generalist script
- Program-aware capture and assignment handling
- Storm week
- Minutes run out. Overage is still receptionist time.
- Same intake at 2am as at 2pm. Volume does not degrade the script.
The minute math restorers skip
Ruby's 100-minute plan is $395 a month. That is the tier owners often quote when they are comparing options.
A restoration company does not get 100 polite check-in calls. It gets fewer calls that last longer, plus the after-hours ones that actually pay the bills. A handful of water losses, a mold consult that turns into a twenty-minute Q and A, and a storm Saturday will blow a 100-minute bucket.
Then you are paying for more minutes of the same thing: a generalist receptionist doing their best with a script.
Hank is not cheaper because it talks faster. It is a different unit of work. You are buying the job getting created, not the minute getting consumed.
When Ruby is still the right tool
If you run a business that needs a warm human greeting and a clean message, Ruby is a legitimate product. Plenty of companies should use it.
If your inbound line is insurance-backed emergency work, you need more than a greeting. You need the loss type, the urgency, the address, the on-call transfer, and a record that will survive a TPA audit.
A lot of shops start with overflow anyway. Try your coordinator first. If they miss it, the system that picks up should still produce a job, not a voicemail-shaped email.
Hank vs. Ruby: common questions
Is Ruby a good answering service?
Yes, for the job it was built for. Live receptionists, 24/7 coverage, and a polished small-business experience. Restoration companies outgrow it when the call has to become a mitigation job, not a message.
Does Ruby integrate with restoration CRMs?
Ruby can notify you and capture intake you configure. It does not write structured jobs into tools like Albi, DASH, Proven, or Xcelerate the way a restoration intake layer does.
How is Ruby priced?
Per receptionist minute. Published plans in 2026 start at $250 a month for 50 minutes, $395 for 100, $720 for 200, and $1,725 for 500. Restoration volume, especially after hours, tends to outgrow the smaller buckets quickly.
Does Hank use live receptionists like Ruby?
No. Hank is a voice AI built for restoration and other insurance-backed trades. It can still try your humans first and live-transfer true emergencies. The default is that every call still becomes a documented job.
We already compared Hank to Moneypenny. Is Ruby different?
Same category, stronger live-receptionist brand. The restoration gap is identical: pickup is not the product. The job file is.
The Bottom Line
Ruby will answer your phone. For a lot of businesses, that is the whole requirement.
Restoration is not those businesses. The money is in what happens after the pickup: qualify the loss, route the crew, write the CRM record, and keep the TPA file clean.
If you are comparing Hank and Ruby on who sounds more human, you will pick Ruby. If you are comparing who turns a 2am water call into a job your team can run, you are no longer shopping receptionists.
Book a demo at dialhank.com and we will show you that call becoming a CRM job, not a message waiting in the morning.
