A Ruby Receptionist alternative for contractors and home service companies

What does Ruby do?

Ruby is a virtual receptionist company. Your calls forward to Ruby's team of live receptionists, who answer in your company's name and handle the call the way you have set up. Its website lists 24/7 live answering, lead qualification and intake, appointment scheduling, payment processing, outbound calling, call forwarding and robocall filtering, with English and Spanish service available around the clock. Ruby also sells a managed live chat service for websites, and it has a mobile app.

Ruby is clear about where AI fits. Its site says an AI receptionist that independently picks up and conducts the call "isn't how Ruby works." Instead, Ruby uses AI behind the scenes for things like transcription and gathering information, and the pricing page says optional AI enhancements come with every plan at no extra cost. The person on the phone is a person.

Ruby says it has more than 20 years of experience with small businesses, and its homepage names roofers, plumbers, HVAC companies, landscapers and contractors among the businesses it serves, alongside law firms and healthcare.

How does Ruby price its plans?

Ruby bills receptionist service by the minute. Ruby's pricing page listed the following receptionist plans as of October 2026:

The per-minute column is our arithmetic on Ruby's listed prices, not a rate Ruby quotes. The page says there are no added fees for activation, onboarding, setup, customization or coverage at certain times. Live chat was listed separately, starting at $143 a month for 10 chats, with a discount for bundling chat and calls.

Ruby's FAQ and its billing help article cover the terms. Ruby counts receptionist time, not the whole call: the clock runs from when a receptionist picks up, includes hold time and any notes typed after the caller hangs up, and stops once the call is transferred to you. Each call is rounded up to the next full minute. There is no long-term contract; outside the money-back period, a cancellation takes effect at the end of the monthly billing period, and first-time customers can get their money back within 21 days or before using 500 minutes, whichever comes first. Minutes past your plan are billed at that plan's overage rate, and unused minutes do not roll over. Ruby did not print those overage rates anywhere we looked, so get yours in writing. That number decides what a busy month really costs.

How many calls do the minutes cover?

That depends on your calls, so look at your phone log before you guess. Pull last month's inbound calls and the average length. Then do the arithmetic.

A made-up example: if your average handled call bills at three minutes, 100 minutes covers about 33 calls a month. If calls bill at five minutes because callers describe a leak or a roof problem in detail, the same plan covers 20. Because Ruby rounds each call up, a call that lasts 2 minutes and 10 seconds counts as 3, so use billed minutes rather than raw talk time. Service businesses often see call spikes, too. The first hot week of summer or the first hard freeze can bring a wave of calls in a few days, and a minute-based plan feels that right away.

None of this makes per-minute billing wrong. It means the plan size should match your busiest month, and you should know what happens when you go over.

What should you ask before signing with any answering service?

Whether you pick Ruby, another live service or an AI provider, get these answers in writing:

• Overage. What does each minute or call past the plan cost, and is there a cap?
• Counting. When does the clock start and stop? Are transfers, hold time and spam calls counted?
• Your number. Do calls forward from a number you own, and can you take it with you if you leave?
• Your records. How do call details reach your CRM or job software, and can you export the full history?
• Leaving. What notice is required to cancel or change plans?

The answers matter more than the headline price, because they decide your bill in a heavy month and how easy it is to switch later.

Who is Ruby a good fit for?

Ruby suits businesses where a human voice is part of the service.

• Callers who expect a person. Some callers, such as a property manager or a homeowner calling about something that went wrong, want to talk to a human.
• Calls that need judgment. A trained receptionist can handle an upset or confused caller in ways a script can't predict.
• Bilingual coverage. English and Spanish service 24/7 is built into Ruby's offering.
• Owners who want no setup project. Forward your calls, agree on how to handle them, and you are running.
• Moderate, predictable call volume. If you know your monthly minutes, plan pricing is easy to budget.

Where it may fit less well: high call volume with short, routine calls, heavy after-hours traffic, or a need to book straight into a field-service calendar with your own rules. Those are the cases where an AI receptionist is worth a look.

What does an AI receptionist alternative look like?

An AI receptionist greets callers as your business, works through your intake questions, handles routine questions from the material you supply, and puts the job on the calendar once it has access. You get a summary and transcript by text or email. It can be set up to take several calls at the same moment, so a storm or a heat wave doesn't have to mean busy signals.

It has limits, and we say so up front. Its knowledge is limited to your written rules: the services and towns you cover, the work you turn down, your pricing approach and your definition of urgent. Escalation rules for gas smells, flooding or no heat in winter must reach a person right away. And some callers simply want a human, so they need a path to one. For the full tradeoff between the two models, read AI receptionist vs answering service.

The ownership piece matters as much as the voice. When we set up an AI receptionist, it runs on a business number you control, inside a phone system with ring groups and missed-call text back, and every call lands as a record in your CRM with the caller, the job and the source. If you ever change providers, the number and the customer history stay with you. Our own service companies take their calls this way too.

How do you choose between them?

1. Pull your call log. Count inbound calls by hour and day, and note the average length. That tells you how many minutes you need and when calls actually come in.
2. Sort calls by type. Routine booking, quote questions, emergencies, existing-customer issues. Routine calls suit AI; emotional or complex calls may suit a person.
3. Write the one-page call rules. Services, area, emergencies, who gets alerted. Any receptionist, human or AI, needs this page.
4. Price both against your busiest month. Include overage, add-ons and setup.
5. Test before you commit. Call your own line at 7 a.m., noon and 10 p.m. Ask a hard question. Pretend it's urgent.

Some companies end up with a mix: a person during business hours, AI for overflow and nights. Our guide of questions to ask an AI receptionist provider helps with the last two steps, and the missed call calculator puts a rough figure on calls going unanswered today.

Frequently asked questions