Ruby receptionist vs LLDTEK: pricing, booking and when to use both

Ruby is a live virtual receptionist service. A US-based person answers every call, and Ruby uses AI only to support that person. Its published plans run from $250 a month for 50 receptionist minutes to $1,725 for 500, billed in 60-second increments rounded up, and its help center lists overage of $4.00 to $5.40 a minute on those plans. LLDTEK takes the other approach: AI agents that answer calls and texts and write bookings into the system you already run. Choose Ruby when callers need a person's judgement. Choose an AI agent when most calls end in a fixed-length slot. Run both when your calls split cleanly by type.

LLDTEK makes AI agents for appointment businesses and competes with Ruby for some of these calls. Ruby's prices and terms below are as of November 2026 and change, so confirm before you sign.

What Ruby is, in its own words

Ruby is explicit that it is not an AI receptionist. Its homepage FAQ says "Ruby uses live, human receptionists" and that an AI receptionist that independently picks up and conducts the call "isn't how Ruby works". Its FAQ describes the receptionists as US-based and says Ruby serves businesses anywhere in the United States, Canada and the US Caribbean.

The AI sits behind the receptionist. Ruby's AI page names four features: Call Nav, an assistant that pulls up information the receptionist can reference during a call; verbatim call and voicemail transcripts; caller sentiment analysis; and robocall filtering. Ruby says all of them are included in every plan at no extra cost, and that it designed them "to serve our team" rather than replace people.

Coverage runs 24/7, including weekends and holidays. Receptionists answer and transfer calls, take messages, answer common questions, book appointments, make outbound calls and process payments on your behalf.

One detail to settle before signing: Ruby's language coverage is described two ways. Ruby's FAQ says "Optional 24/7 Spanish bilingual service is included with every receptionist service account at no additional cost." Another answer on the same page says "bilingual service and outbound call assists are only available Monday to Friday, 5am to 6pm Pacific / 8am to 9pm Eastern." If Spanish-speaking callers ring your spa on Sunday evenings, ask Ruby which statement applies to your account.

Ruby receptionist pricing and cost

Ruby's pricing page shows four receptionist plans and says "The only difference between our plans? The number of receptionist minutes." It does not show an overage rate. Ruby's help center does, in an article last updated in December 2025 that lists ten plans with their overage rates:

The help center also lists plans the pricing page leaves out, including Call Ruby 350 at $1,210 with $4.25 overage, and larger tiers up to 2,500 minutes for $7,875. Chat is priced separately, from $143 for 10 chats, or $115 for 10 when you add it to a receptionist plan.

Ruby states plainly that there are no extra fees for activation, onboarding, setup, customization or coverage at particular times. Smith.ai, by contrast, bills each answered call regardless of length, as the Smith.ai pricing breakdown walks through.

What counts as a Ruby receptionist minute

The minute is where the bill is decided, and Ruby's billing basics article sets the rules:

• Calls are billed in 60-second increments and rounded up, so a ten-second call costs a full minute.
• The clock starts when a receptionist receives the call and includes time the caller spends on hold.
• It stops when the receptionist transfers the call to you or to voicemail, so your own talk time after a transfer is not billed.
• Time a receptionist spends completing information on your call after the caller hangs up is billed.
• Unused minutes do not roll over, and you are not moved to a bigger plan automatically when you go over.
• Overage is billed after the month ends, and Ruby's FAQ says you get an alert at 85% and 100% of your plan's minutes.
• Credit card payments carry a 3% processing fee.

Plan changes have their own rhythm. New customers can move up or down at any time during their first three billing cycles. After that, upgrades apply immediately and, under Ruby's terms of use, for at least the next two cycles, while downgrades need three consecutive periods on the same plan. The terms also say debit, ACH and check payments carry no surcharge. Ruby's FAQ offers first-time customers a money-back guarantee within 21 days or 500 receptionist minutes, whichever comes first; its terms say the exact window is stated at signup.

Ruby's own tips for keeping costs low suggest letting calls ring twice at your desk before they roll over, and note that calls routed to your after-hours voicemail are never billed.

How a Ruby receptionist books an appointment

Ruby's receptionists book through the same online booking page your clients use. Ruby's scheduling guide asks for the URL of your online calendar, reviews it against Ruby's guidelines, and sets out what the page needs:

1. Receptionists "should not be required to log in or create an account in order to schedule an appointment."
2. Required fields must be clearly marked. If a caller will not give required information, the receptionist takes a message or transfers the call instead of booking.
3. Each appointment's duration and location should be clearly defined so the receptionist can tell the caller.
4. The receptionist must be able to set the time zone to the caller's, because Ruby's team works across several US time zones.

Two limits matter more for an appointment business. Ruby says "We are not able to schedule recurring appointments." And it cannot change a booking once made: the guide says "we won't be able to manage your calendar to make that update," and offers two options instead. The receptionist can point the caller to the confirmation email, where most booking platforms allow changes, or take a message for your team. Ruby's integrations page says receptionists can "schedule and reschedule appointments" in Calendly, but its Calendly help article says Ruby is "unable to cancel appointments or modify existing appointments" there either, so assume no changes unless Ruby confirms otherwise in writing.

The scheduling guide also says Ruby has no insight into your availability "other than what you have setup in your scheduling platform". In practice, a Ruby receptionist can book anything your public booking page allows, and nothing it hides. If your page already enforces therapist skills, room types and service length, the receptionist inherits those rules. If it does not, neither does the receptionist.

The calendars Ruby names are Calendly, which the guide says it has "had a lot of success with", and Google Calendar, plus "20+ other scheduling tools" it does not list. The integrations page does not mention Vagaro, Square, Booksy, Mindbody or Zenoti. That does not mean Ruby cannot use their booking pages. It means you should open your own online booking page in a private browser window, try to book a 90-minute massage as a guest, and note whether it asks you to sign in or create an account before confirming. That is the first thing Ruby's review will check.

What a receptionist minute buys at a day spa

Take a four-room day spa that sells 60- and 90-minute massages, facials and a couples room. Its desk is busy checking guests in and out, so it forwards overflow and after-hours calls to Ruby. Its online booking page passes Ruby's review. In a typical month Ruby answers 120 calls. The billed minutes per call below are assumptions that include rounding up and after-call notes, so replace them with your own call log:

Priced against Ruby's help-center rates:

Paying the Call Ruby 350 bill by credit card adds 3%, which brings it to $1,268.19. Paying by ACH avoids that.

Three things come out of this.

The right plan may not be on the pricing page. The cheapest fit here is the 350-minute plan, which appears in Ruby's help center but not on its main pricing page. The "most popular" 200-minute plan costs $170.75 more this month because of overage, and the 500-minute plan wastes 145 minutes that do not roll over. Ask Ruby for the full plan list before choosing.

One call in five ends as a message. The 25 move and cancel calls use 50 minutes, about $173 at this plan's blended rate of roughly $3.47 a minute. Because Ruby does not change existing bookings, each one becomes a message for the desk the next morning, or a caller sent to find their confirmation email. Until someone at the desk processes the message, the 90-minute slot stays booked and nobody can be offered it. Whether that matters depends on how often your cancellations could have been refilled. The guide to refilling spa cancellations without double-booking covers the room and therapist checks involved.

The cost per booking is about $27, before no-shows. $1,231.25 divided by 45 bookings is $27.36 per booking made. It is not a cost per attended visit, because some of those guests will cancel or not show. Compare it with the margin on your average treatment, not with the price of a receptionist hour.

None of this says Ruby is poor value. A caller who wants reassurance about her first massage, or who is buying an anniversary gift card and has questions, gets a patient human voice at any hour. That is what the minute buys, and some spas will gladly pay $3.45 to $5.40 for it.

How LLDTEK handles the same calls

LLDTEK sells AI agents for appointment businesses. Its front desk agent answers calls, texts and web messages the team cannot get to, and its homepage describes the agents as booking, moving or cancelling appointments in the calendar the business already uses. Other agents fill cancelled slots, book the next visit, send one review request after a good visit and show the live floor. A guest who calls and then texts stays in one conversation. The agents answer in the language the guest used.

The booking does not go through the public booking page. LLDTEK's list of supported booking systems says the agents "read real availability in your system, book it there," and has guides for Vagaro, Square Appointments, Booksy, Zenoti and Mindbody among others. For a spa, the agent can check which therapist and, where your system tracks rooms as resources, which room is free for a 90-minute treatment before it books. Confirm your own system and the actions you need, including moves and cancellations, on a demo against your real book rather than taking the integration list on trust.

The trade-offs run the other way from Ruby's:

• No live person on LLDTEK's side. When the agent reaches something it should not decide, such as a VIP, a dispute or an off-menu request, it stops and passes the full thread to your own team. After closing time, that means a callback, not a human voice on the line.
• No price to calculate. LLDTEK does not publish a price. It quotes after a 30-minute demo once fit is confirmed, and its team watches a live day with you before billing starts. You cannot put LLDTEK into the table above today, and that counts against it.
• Setup work is shared. LLDTEK configures the rules with you: which treatments need a question first, which therapists take new guests, and which requests always go to a person. Ruby also sets up call-handling instructions with you, so neither is self-serve, but the AI agent needs more of your rules written down.

Ruby and LLDTEK side by side

Where a human voice is worth the minute

Ruby's receptionist brings judgement and warmth but books only what your public page allows. An AI agent brings direct access to the book but should stop wherever a rule has not been written down.

Ruby is the better buy for a spa when:

• A meaningful share of callers are buying gifts, planning a group or bridal party, or asking open questions that do not end in a fixed slot.
• You want a person on the line at 2 a.m. and are willing to pay per minute for it.
• Your booking page already enforces your rules, so a receptionist booking through it cannot create a problem the page would not.

Running Ruby and an AI agent together

A hybrid works when your calls split by type and both types are common. If nearly every call is a booking, a second vendor adds a seam you rarely use. The guide to live, AI and hybrid virtual receptionists shows how one booking call plays out under each model. For a spa, three setups are realistic:

1. Split by number. Put the AI agent on the main booking line, SMS and web, and publish a separate number for events, groups and corporate bookings that forwards to Ruby. Ruby's minutes then go only to calls that need a conversation.
2. Split by hour. Your own desk answers during opening hours with the AI agent taking overflow, and Ruby covers the hours when you want a human voice. The weakness is that a move or cancel request after hours still ends as a message.
3. A person behind the agent. The agent takes every call and hands VIPs, disputes and off-menu requests to a human. LLDTEK's public pages describe that handoff going to your own team. If you want it to reach an outside service such as Ruby after hours, ask whether that is possible before you plan around it.

Whatever the split, test the seam. Call in, trigger a transfer, and check that the person who answers can see what was already said and booked.

Questions to settle before you sign either one

• Which of your calls end in a fixed-length booking, which are moves and cancellations, and which need a person? Two weeks of call logs answer this.
• Does your online booking page ask a guest to log in or create an account? If yes, it does not meet Ruby's scheduling guideline as it stands, so raise it with Ruby first.
• Does the booking land with the right therapist, in the right room, at the full treatment length? Watch a test booking and then open it in your own system.
• Who handles a request to move a visit, and how fast is the freed slot offered to someone else?
• What is the overage rate on your plan, and which plans exist beyond the four on Ruby's pricing page?
• Which hours does each vendor cover in Spanish or any other language your guests use?
• What does a handoff look like, and does the person receiving it see the whole conversation?

What to test on an AI receptionist demo turns the AI side of this list into a call script you can run on any vendor.

Choosing between a live minute and a written booking

Ruby sells the voice on the call: a trained person at any hour, priced openly by the rounded-up minute, booking only what your public page allows. LLDTEK sells the result in the book, with a person from your own team behind it.

The deciding number for a spa is the share of calls that end in a fixed-length treatment slot or a change to one. Sort two weeks of calls into those and the rest. If bookings and changes dominate, pay for write access and keep human minutes for what is left. If gift questions, group plans and reassurance dominate, Ruby's minute is the better buy.