Ruby Pricing in 2026: What Are You Actually Paying For?

Ruby pricing looks straightforward because the unit is easy to understand: receptionist minutes. The published plans start at $250 per month for 50 minutes and rise to $1,725 per month for 500 minutes. Those prices are current as of September 2026.

For a plaintiff firm, that is only the first calculation.

A new-client call may require intake. An existing client may need case context. A medical provider may be calling about records or treatment. An adjuster may need a case-specific response. A receptionist can handle the first interaction correctly and still leave another task with your team.

That is why the useful Ruby pricing question is not simply, "What does Ruby cost?" It is whether paying for receptionist minutes removes enough work from your operation to justify the model.

This guide breaks down current Ruby pricing, how Ruby counts receptionist minutes, what can make the bill move, where Ruby genuinely fits, and how to compare a live receptionist service with a plaintiff-specific AI voice-agent model without pretending they are the same product.

How Much Does Ruby Cost in 2026?

Ruby pricing currently starts at $250 per month for 50 receptionist minutes. Published plans also include $395 for 100 minutes, $720 for 200 minutes, and $1,725 for 500 minutes. Ruby says larger offerings are available for higher-volume customers.

The published Ruby pricing plans therefore give smaller and mid-volume buyers a clear rate card, while higher-volume businesses need a quote.

The pattern is simple: larger Ruby pricing plans reduce the effective price of each included minute. That does not mean every call literally costs $3.45 to $5.00. Ruby sells a monthly allowance. Your realized Ruby receptionist cost depends on how much of that allowance you use, how long the receptionist spends on each interaction, and whether your usage crosses into overage.

A firm with 100 short routing calls can consume fewer receptionist minutes than a firm with 60 longer intake and existing-client calls. The call count is lower, but the Ruby pricing requirement can be higher.

If you are sizing a plan from call count alone, ask one more question:

How long does each caller type actually stay with the receptionist before transfer, voicemail, or completion?

Ruby Pricing in One Direct Answer

Ruby pricing starts at $250 per month for 50 receptionist minutes, then moves to $395 for 100 minutes, $720 for 200 minutes, and $1,725 for 500 minutes. Larger-volume plans are available by quote.

How Does Ruby Pricing Work per Minute?

Ruby pricing uses receptionist minutes rather than call count, and those minutes include more than raw talk time.

Ruby's current terms say receptionist time is billed in 60-second increments. Calls are rounded up to the next 60-second mark.

For inbound calls, usage starts when the receptionist receives the call and continues until the receptionist transfers the caller, sends the caller to voicemail, or otherwise completes the interaction. Hold time counts. Time spent finishing information after the caller hangs up can count too. Talk time after a successful transfer to your team or voicemail does not count.

For outbound calls, Ruby counts the time its outbound specialist spends on the call plus the time spent sending the follow-up email that reports the outcome.

That makes Ruby pricing more sensitive to call complexity than a simple per-call model.

Consider two illustrative firms:

Both firms had the same call count. Their likely Ruby pricing plans would be very different.

The same variation appears inside one PI firm. A solicitor may be screened quickly. A prospective client may need several intake questions. An existing client may require identification, a matter-specific message, and a transfer. A provider may need to reach the correct case team.

Minute rounding also matters more as volume grows. A call that runs just over one minute can consume two receptionist minutes. Across a few calls, the difference is minor. Across hundreds of calls, especially when usage sits near the top of a Ruby pricing tier, the effect is easier to see.

What Happens When You Exceed Your Ruby Minutes?

Ruby applies overage charges when usage exceeds the receptionist minutes included in your plan. Ruby also gives customers usage alerts at 85% and 100% of the monthly allowance.

The current public pricing page does not show a full overage-rate table. If your normal month sits close to the plan ceiling, ask for the exact overage rate attached to the plan you are considering before you build a budget.

This is where Ruby pricing can look predictable until the high-volume month arrives.

Suppose your firm usually uses 470 minutes. The 500-minute plan may work most months. A marketing campaign, staff absence, unusually busy intake period, or spike in existing-client calls can push the same account beyond the allowance.

The better test is simple: What does your busy month cost, not just your average month?

What Else Can Change the Invoice?

Ruby's current terms contain a few commercial details worth checking alongside the Ruby pricing table.

The customer agreement runs on a 30-day cycle and renews automatically. New customers have a 90-day calibration window in which plan changes are easier to make. Outside that window, plan-change rules become more restrictive.

Credit-card payments can also carry a 3% surcharge, while debit card, ACH, and check payments do not. On a $1,725 monthly plan, 3% is $51.75 before overage or applicable taxes.

These details do not make Ruby pricing high or low by themselves. They simply belong in the cost model if they apply to the way your firm will pay and use the service.

What Do You Get for Ruby Receptionist Pricing?

Ruby receptionist pricing buys a staffed virtual reception service with a broader feature set than basic message-taking.

Ruby currently advertises 24/7 live answering, personalized call handling, screening and routing, lead qualification and intake, appointment scheduling, payment collection, outbound call assistance, voicemail options, robocall filtering, phone hosting, app access, transcripts, and bilingual call handling.

For a firm that wants live people answering its mainline, that breadth matters. Ruby pricing pays for more than a person taking a name and number.

Ruby also supports legal-software integrations, including Clio, Filevine, MyCase, Law Ruler, Lawmatics, and Rocket Matter.

That is a genuine Ruby strength, and it is why a fair comparison should not claim that Ruby simply emails a message while another vendor "integrates."

The better procurement questions are more specific:

• Context: What can the receptionist see while the call is happening?
• Write-back: What information is written back into the legal system after the call?
• Handoff: Does the next employee have enough context to act without reconstructing the conversation?
• Follow-up: Does the workflow continue, or does a new task return to the firm's queue?

An integration can create a lead, a message, a task, or a matter update. Those are different levels of operational depth.

Ruby Also Makes Outbound Calls

Any current Ruby pricing comparison should state this clearly: Ruby supports outbound calling.

Customers can submit outbound-call requests, and Ruby also supports batch requests. Ruby says standard outbound requests are generally made within 30 minutes during service hours, while larger batches can take longer. Current outbound assistance runs Monday through Friday from 5 a.m. to 6 p.m. Pacific.

The more useful distinction for a plaintiff firm is the type of outbound work being handled.

"Call this person and relay this information" is a discrete request.

"Keep following up on this open records request according to our SOP, capture the result, update the matter, and continue until the defined next step is reached" is a workflow.

Both involve outbound calling. They require different persistence, context, documentation, and staff involvement.

Confirm Bilingual Coverage for Your Exact Use Case

Ruby's public materials currently contain inconsistent language around bilingual service hours.

Its pricing and bilingual-service pages advertise 24/7 inbound bilingual answering, while the current FAQ still says bilingual service is available Monday through Friday during specified hours.

If after-hours Spanish coverage matters to your intake or client-service model, confirm the current operating window in writing before you rely on it.

That is a procurement check rather than a reason to rule Ruby in or out. Feature availability should match the exact workflow you intend to run.

Test #1: Do Your Calls Fit a Minute-Based Model?

Ruby pricing is easiest to forecast when call volume and handling time are reasonably predictable.

Plaintiff firms rarely receive one type of call. Prospective clients, active clients, medical providers, insurance adjusters, referral sources, vendors, wrong numbers, and solicitors can all reach the same mainline.

Those callers do not consume receptionist minutes evenly.

Here is an illustrative PI call mix:

These are illustrative figures, not Ruby customer data. They show why 300 calls do not equal 300 receptionist minutes, which is easier to size once you know your realPI call volume.

At 670 illustrative minutes, the firm would sit above Ruby's largest publicly listed 500-minute plan and would need a higher-volume quote or an arrangement that accounts for overage.

The same exercise becomes much more useful when you separate callers by what happens after the interaction.

A prospective-client call may need automated or human lead follow-up. An active client may need a case manager to check treatment status. A provider call may create a medical records task. An adjuster may need a matter-specific response.

If you can predict both call length and downstream work, Ruby pricing becomes much easier to judge.

Test #2: Does the Call End When Ruby Hangs Up?

For plaintiff firms, the largest hidden cost can be the work that returns to staff after the receptionist portion is complete.

Consider an existing client calling about treatment. Ruby may identify the caller, take the message, and route or transfer the call according to the firm's instructions. That may be exactly what you want from a legal answering service.

It may also leave another workflow behind:

1. The case manager opens the matter.

2. They read the message and rebuild the context.

3. They check the latest treatment information.

4. They return the call or contact the provider.

5. They document what happened.

6. They create another reminder if the task is still open.

The Ruby receptionist cost covers the receptionist's part. It does not automatically tell you what the firm spends completing the rest of the work, which is the documentation problem an answering service can quietly create.

The same issue appears with providers and adjusters. A provider call can create a records follow-up. An adjuster can require a substantive response from the case team. A prospect can require another intake attempt.

This is why the more useful question is: What percentage of your outsourced calls are actually finished when reception finishes?

If the answer is "most of them," Ruby may fit the job very well, and Ruby pricing can map closely to the value received.

If the answer is "not many," the firm is buying reception while still carrying much of the operational queue behind it.

Test #3: Is Human Reception the Outcome You Actually Want?

Ruby is strongest when live human reception is the service you deliberately want and the work after reception is already handled well inside the firm.

That point matters more than a generic pros-and-cons list.

A firm may prefer a live receptionist because it wants a person on the mainline, because sensitive first interactions are better kept human, or because its internal process after the call is already efficient. In that operating model, Ruby pricing is attached to a service the firm has intentionally chosen.

The problem changes when the phone workload extends well past reception.

Case managers may still be returningroutine status calls, sitting through provider hold queues, chasing open record requests, coordinating treatment updates, documenting interactions, or following up with insurers. Adding reception capacity reduces one part of that workload. It does not necessarily remove the rest.

That is the operating problem we focus on at HelloCounsel. Our AI voice agents for plaintiff firms are built around plaintiff call and operational workflows across office-hours reception, after-hours attendance, intake, automated lead follow-up, active-case communication, medical-record follow-up, treatment workflows, insurer-related work, call documentation, and supported outbound follow-up. HelloCounsel also explicitly covers inbound calls, outbound calls, caller identification, and CMS note logging.

The system is designed to identify who is calling, use relevant matter context, follow the firm's defined workflow, capture notes during the conversation, write supported outcomes back into the case-management system, and escalate exceptions to the team. Current case-management integrations are Filevine, SmartAdvocate, Litify, Lead Docket, and Clio.

The human boundary stays visible. Sensitive conversations, unusual exceptions, attorney judgment, strategy, settlement decisions, and legal advice remain with the firm.

Where Ruby Is Genuinely Strong

Ruby has real strengths, particularly for firms that want staffed reception and prefer a human on the front line.

First, a live person answers. If that is a requirement rather than a preference, Ruby immediately narrows the field.

Second, the service goes beyond answering and message-taking. Intake, scheduling, routing, payment collection, outbound assistance, bilingual handling, and legal integrations give firms room to build a more capable front-desk workflow.

Third, Ruby pricing becomes relatively easy to budget when the firm's call volume and handling time stay within a stable range. You buy a set amount of receptionist capacity and monitor usage against it.

Current review data shows a mixed rather than one-sided picture. G2 lists Ruby at 3.8 out of 5, while Capterra lists it at 3.9 out of 5. Both are small samples, so they are better used as prompts for due diligence than as a verdict.

Positive reviews mention call coverage, screening, and taking interruptions off internal staff. Critical reviews raise issues around price, routing, call-handling quality, or the amount of follow-up still required.

That is useful evidence because it points back to the same buying test: Does the service boundary line up with the work you actually want removed?

Where Ruby Pricing Can Work Against the Workflow

Ruby pricing becomes harder to justify when the thing consuming staff capacity is not answering the phone, but completing what the call creates.

Four patterns are worth watching.

High or Variable Volume

Minute-based pricing becomes less predictable as call volume and call duration move. A larger Ruby pricing plan lowers the effective included-minute rate, but the relationship between usage and cost remains.

If your busiest month matters more than your average month, model the busiest month.

Context-Heavy Calls

Longer intake calls, active-client questions, provider traffic, and adjuster conversations can consume more receptionist time than simple screening. If those calls dominate your mix, Ruby virtual receptionist pricing should be modeled from actual handle-time data rather than a generic average.

Repeated Post-Call Work

A message that becomes another callback still creates work. So does a provider call that becomes a records task. So does an adjuster call that needs a case-specific response.

If those handoffs happen constantly, Ruby pricing is only measuring the front of the process.

Recurring Outbound Work

Ruby's outbound capability is real. The question is whether your firm needs individual outbound assists or task-driven follow-up that persists across attempts.

Medical records follow-up is a useful example. The actual conversation may take only a few minutes. The workflow can include an IVR, hold time, a voicemail, another attempt, a status update, a case note, and another follow-up date.

A somewhat longer interaction that completes the supported workflow may be more valuable than a short one that creates three more staff touches. Call duration by itself is not the operating metric.

Ruby Pricing vs. HelloCounsel for Plaintiff Firms

Ruby and HelloCounsel both handle phone work, but they are built around different service boundaries and different units of value.

HelloCounsel publishes this comparison, so we have an obvious commercial bias. The fair way to handle it is to give Ruby credit where it fits and compare both models against the same operational questions. If you want the wider field, our roundup ofRuby receptionist alternatives covers where each option fits.

Ruby sells staffed virtual receptionist capacity. Ruby pricing is therefore tied to receptionist minutes.

HelloCounsel provides AI voice agents purpose-built for plaintiff firms. Pricing is custom-scoped around expected usage, licenses, and supported workflows, then fixed monthly within an agreed tolerance of roughly 20% either way. The model is designed around completing supported outcomes rather than charging for receptionist talk time.

The strongest HelloCounsel argument is not "Ruby, only cheaper." That would flatten two different products into the same category.

Ruby pricing pays for receptionist capacity. HelloCounsel pricing is tied to the supported work the firm wants carried through.

The difference becomes clearer after the phone rings.

For a supported HelloCounsel workflow, the agent can identify the caller, connect that caller to the relevant matter context, handle the defined interaction, capture notes in parallel, complete the supported next step, write the outcome into the case workflow, and continue the required follow-up according to the firm's SOP. Exceptions and judgment-heavy issues are escalated to the team.

That reduces relay time. Staff do not have to read a message, rebuild the context, document the second interaction, and create another reminder simply because the first call ended.

Case-management integrations include Filevine, SmartAdvocate, Litify, Lead Docket, and Clio. For SmartAdvocate deployments, HelloCounsel covers the platform's $1,000 vendor integration fee. There is no setup fee under the current approved model. Onboarding is framed as one one-hour setup call, 17 multiple-choice questions, and agents working inside SmartAdvocate in roughly one week. The timeline is approximate rather than guaranteed.

Case opening should also be treated carefully. That workflow remains beta under the current approved product guidance. HelloCounsel can support demand-stage client communication, while valuation, demand drafting, negotiation, litigation strategy, and trial remain with the legal team.

When Ruby Is the Better Fit

Ruby may be the stronger fit when:

• Human first touch is the priority: You deliberately want a person answering sensitive first interactions.
• Most outsourced work ends at reception: Screening, routing, intake, scheduling, and message-taking solve the main problem.
• Your call volume is predictable: Usage sits comfortably inside a Ruby pricing tier.
• Your internal follow-up process already works: Reception does not create a meaningful relay or re-entry problem.
• Ruby's integration depth is sufficient: The information reaching your systems is enough for the team to take over efficiently.

When HelloCounsel Is the Better Fit

HelloCounsel may be the stronger fit when:

• You run a plaintiff firm with dedicated case or intake teams: The product is deliberately narrow rather than generic legal AI.
• The workload continues after the initial call: Case managers or intake staff still absorb routine follow-up.
• Outbound work consumes meaningful staff capacity: Records follow-up, treatment checks, insurer workflows, and other defined tasks repeat across many matters.
• Caller identification and matter context matter: The workflow depends on knowing who is calling and which case is involved.
• Documentation creates rework: Notes and supported outcomes need to land in the case workflow without a second documentation step.
• Follow-up has to persist: One attempt does not complete the task.
• Predictable monthly spend matters: You prefer a custom-scoped fixed model over receptionist-minute metering.

A smaller general-practice firm without a production case-management system or dedicated case staff may not be the right HelloCounsel fit. The product is built for plaintiff-side operations, especially personal injury firms with enough workflow volume to make automation meaningful.

Test #4: What Should You Measure Before Choosing Ruby?

The most useful Ruby pricing calculation starts with one month of your own phone operations. Do not begin with the plan table. Begin with the work.

1. How Many Calls End at Reception?

Separate calls that are effectively complete after screening, routing, scheduling, intake, or message-taking from calls that create another task.

If most calls end there, Ruby pricing maps cleanly to the outcome.

If many calls create provider follow-up, records work, client callbacks, insurer tasks, or case-file updates, receptionist cost is only one layer.

2. What Is Your Real Receptionist-Minute Requirement?

Break calls down by caller type and average handling time. Include post-call work and the effect of 60-second rounding.

Do not assume 300 calls should fit a 300-minute Ruby pricing plan.

3. How Often Will You Hit Overage?

Model a normal month and a high-volume month. If the normal month already sits near the ceiling, get the exact overage rate and higher-volume pricing before you sign.

4. Which Calls Actually Need a Person?

Sensitive client conversations, legal judgment, settlement decisions, attorney advice, unusual exceptions, and strategy belong with the appropriate people.

Repeatable operational tasks with defined rules are better automation candidates.

For more on that boundary, theHelloCounsel FAQ covers how the product is intended to fit into an existing plaintiff-firm team.

5. What Happens to the Information After the Call?

Ask every vendor the same questions:

• Caller identification: Can the system identify who is calling?
• Matter context: Can it connect the caller to the relevant case information?
• Call documentation: Are notes captured during the interaction or recreated afterward?
• Write-back: Where do supported outcomes land?
• Follow-up: Can the workflow continue after the first attempt?
• Escalation: What happens when the request falls outside the SOP?
• Human handoff: What context reaches the person who takes over?

These questions expose the operating difference between answering a call and carrying the work forward.

The broaderHelloCounsel blog covers more of these plaintiff-firm call and workflow questions.

6. What Is the Cost of Internal Reception Really?

The U.S. Bureau of Labor Statistics reports a median hourly wage of $18.27 for receptionists and information clerks as of May 2025.

That is a useful context, not a direct break-even formula.

An employee also carries payroll taxes, benefits, management time, recruiting, training, equipment, and paid non-call time. The same employee may perform useful administrative work between calls.

Ruby pricing buys flexible receptionist capacity. Internal staffing buys a broader block of labor. HelloCounsel pricing buys a defined set of supported workflows.

Compare the completed work, not just the hourly or per-minute number.

The Better Question Is Whether the Work Is Finished

Ruby pricing is transparent enough at the plan level. You can see the monthly subscription, the receptionist minutes included, and the lower effective rate on larger plans.

The harder decision is whether receptionist minutes are the right unit for your firm.

If you want live human reception and most calls are complete after screening, routing, intake, scheduling, or message-taking, Ruby can fit that requirement well.

If the same calls keep creating callbacks, provider follow-up, records work, treatment checks, insurer tasks, lead follow-up, and case-file updates, reception is only the front of the workflow.

At HelloCounsel, we build around that second problem. Our AI voice agents are designed to carry supported inbound and outbound plaintiff-firm workflows further, while the firm's people retain legal judgment, exceptions, strategy, and relationship-heavy conversations.

The useful comparison is what each model removes from your team's day.

Frequently Asked Questions About Ruby Pricing

How Much Does a Ruby Receptionist Cost per Month?

Ruby pricing starts at $250 per month for 50 receptionist minutes. Published plans also include $395 for 100 minutes, $720 for 200 minutes, and $1,725 for 500 minutes. Larger-volume options are available by quote.

How Much Does Ruby Cost per Minute?

The effective included-minute rate ranges from $5.00 on the 50-minute plan to $3.45 on the 500-minute plan. Actual Ruby receptionist cost depends on usage, rounding, post-call time, and overage.

What Counts as a Ruby Receptionist Minute?

Ruby bills receptionist time in 60-second increments. Inbound usage includes answering through transfer, voicemail, or completion, plus hold time and applicable post-call documentation. Talk time after a successful transfer is excluded.

What Happens if I Exceed My Ruby Pricing Plan?

Ruby charges overage when receptionist usage exceeds the included monthly minutes. Customers receive usage alerts at 85% and 100%. Ask Ruby for the current overage rate attached to the plan you are evaluating.

Does Ruby Make Outbound Calls?

Yes. Ruby supports outbound-call requests and batch outbound calling during its published service hours. Compare the depth of the workflow, including persistence, context, documentation, and remaining staff work, rather than treating outbound as a simple yes-or-no feature.

Does Ruby Require a Long-Term Contract?

Ruby's current agreement runs on a 30-day cycle and renews automatically. Plan-change rules vary depending on whether the customer is still inside the initial calibration period, so review the current terms before signing.

Is Ruby or HelloCounsel Better for Personal Injury Firms?

Ruby fits firms prioritizing live human reception. HelloCounsel fits plaintiff firms that want supported inbound and outbound workflows carried further through caller identification, case context, call note-taking, CMS write-back, and continued administrative follow-up.