9/2/2026
Clerx and Ruby can both answer law firm calls, qualify potential clients, schedule consultations, and connect with legal software. Compare their AI-first and human-first service models, channels, integrations, languages, and pricing.
Clerx and Ruby Receptionists can both answer calls 24/7, collect prospective-client information, schedule consultations, route callers, and send information into legal software. But they use fundamentally different operating models.
Ruby is a human-first virtual receptionist service. Its trained receptionists conduct the calls and website chats, while AI works behind the scenes to assist them and produce features such as transcripts and sentiment analysis.
Clerx is an AI-first legal intake and client-communication platform. It completes the law firm's approved workflows across phone and written channels, then escalates exceptions directly to the firm's own staff.
The short answer:
This comparison is published by Clerx. We reviewed Ruby's public product, pricing, integration, and support materials and identified areas where Ruby may be the stronger choice. Those sources are listed at the bottom of this article. Features and pricing can change, so firms should confirm current terms and test their required workflows directly with each provider.
Both services can help law firms:
The decision should not be based on a checklist showing that both companies answer calls or integrate with Clio. It should be based on who or what performs the work, how deeply the workflow reaches into the firm's systems, how consistently it can be repeated, and how the complete service is billed.
The simplest way to understand the comparison is this:
Ruby primarily provides an outsourced human front desk supported by technology. Clerx provides a legal intake and client-communication system that escalates exceptions to the law firm's own humans.
Ruby's public materials are explicit that its AI is designed to support its receptionists rather than replace them. Ruby's Call Nav tool can surface information for a receptionist during a conversation. Ruby also uses AI for call and voicemail transcripts, sentiment analysis, and robocall filtering. The receptionist remains the person speaking with the caller.
That model may be valuable when:
Clerx uses AI to conduct the approved interaction itself. Clerx can qualify the inquiry, follow branching intake logic, schedule a consultation, collect an online payment, update connected systems, and take the appropriate next step without requiring a receptionist for each interaction.
When Clerx cannot confidently complete the request, it can:
This model may be valuable when:
Neither model removes the need for testing. Human receptionists can bring empathy and adaptability, but execution can vary between people and calls. AI can bring consistency and capacity, but the workflow and escalation rules must be designed carefully. Ask both providers to demonstrate the same realistic situations before deciding.
Ruby charges for receptionist time rather than a fixed number of calls. According to Ruby's billing documentation, billable receptionist time starts when the receptionist receives the call and ends when the call is transferred, sent to voicemail, or completed. It also includes hold time and time the receptionist spends finishing information after the caller hangs up.
Ruby bills in 60-second increments and rounds each billable call up to the next minute. Calls lasting fewer than 10 seconds are not billed, and time after a completed transfer to the firm is excluded.
Ruby says a typical inbound call averages approximately two receptionist minutes across its business base. It also cautions that lengthy intake forms, frustrated callers, questions, and talkative callers can make calls longer. That distinction matters for law firms because detailed intake often requires more questions than a simple message or transfer.
Using Ruby's company-wide two-minute average only as an illustration:
These examples are not a quote and should not be treated as a prediction of a particular firm's usage. They show why firms should compare the cost of completing their actual intake workflow, not merely the lowest advertised monthly price.
Clerx prices a customized package around expected call volume, selected channels, integrations, and workflows rather than metering each minute spent by a receptionist. Before purchase, the firm receives its included usage, package price, overage rate, and applicable add-ons.
Ruby's receptionists can listen, respond naturally, and adapt when a conversation does not follow a predictable path. For a distressed caller who wants reassurance or an unusual caller whose request does not fit a defined workflow, that human presence can be a real advantage.
Clerx's advantage is repeatability. Once a workflow is approved, Clerx can consistently ask the required questions, apply the firm's qualification rules, write information into the designated fields, and trigger the approved follow-up. It does not rely on each individual receptionist remembering every branch of the firm's process while also listening, taking notes, and moving the call forward.
This distinction becomes important when a firm needs more than a friendly greeting. Examples include:
Ruby can customize call handling, gather intake information, and use firm-provided forms. Clerx is more likely to be the stronger fit when the desired result is a multi-step legal workflow rather than a human taking a message, completing a form, scheduling, or transferring the call.
Ruby's serviced communication products center on live phone reception and managed website chat. Its app also lets a firm's users call and text from a Ruby-hosted business number. Ruby can pass receptionist messages and communication data into other tools through native integrations or Zapier.
Clerx is designed to conduct intake and client communication across:
Clerx can apply connected qualification, scheduling, routing, and CRM rules across these channels. A potential client can begin on website chat, continue through text, book and pay for a consultation, and have the resulting information sent to the firm's legal CRM.
Ruby may be the better fit when the primary need is for humans to answer calls and website chats. Clerx may be the better fit when the firm's intake problem spans several communication channels and those interactions need to become one structured workflow.
Both companies offer 24/7 website chat, but the experience and pricing model are different.
Clerx website chat uses AI to respond immediately and includes unlimited website chats in every package. It can:
Ruby's website chat is handled by live receptionists. Ruby says a human responds within 60 seconds. Its chat specialists can answer firm-approved questions, collect lead information, provide transcripts, and connect a website visitor to the firm by phone.
Ruby bills chat by engaged conversation. As of September 2, 2026, its published standalone plans include:
Ruby defines an engaged chat broadly enough to include leads, actionable support, non-actionable support, and recruitment conversations. Unused chats do not roll over.
Ruby may be the better fit if the firm specifically wants a live human typing each website response. Clerx may be the better fit if the firm expects substantial chat volume, wants immediate responses, or wants website chat connected to the same legal intake operation used across its other channels.
Clerx includes hands-on legal workflow design for every client, regardless of call volume. Clerx's standard implementation includes:
Ruby includes the same core feature set across its standard receptionist plans. It advertises custom greetings, personalized call handling, scheduling, bilingual answering, lead intake, payment collection, and optional AI enhancements. Ruby also says it does not charge separate activation, onboarding, setup, customization, or holiday-coverage fees.
Ruby customers can update call-handling preferences through its app and portal, and Ruby's Customer Happiness and Integrations teams can help with instructions and connections. This is a mature, standardized onboarding model designed to serve many types of small businesses.
Ruby may be attractive to firms wanting a proven human receptionist operation with straightforward setup and no setup fee. Clerx may be attractive to firms wanting senior product and technical leaders involved in designing a more customized legal intake operation.
Ask both companies:
Clerx focuses on detailed read-and-write workflows inside legal systems. Depending on the connected platform and approved configuration, Clerx can:
Firms can review the Clerx and Clio integration, the Clerx and 8am MyCase integration, or the complete Clerx integration directory.
Ruby has genuine legal-software integrations. Its public integration directory includes Clio Manage, Clio Grow, 8am MyCase, Filevine, Lawmatics, Law Ruler, Rocket Matter, and other tools. Ruby also offers Zapier-based connections to thousands of applications.
The published Ruby workflows vary by system. For example:
Do not evaluate either provider only by checking whether a logo appears in an integration directory. Ask each company to demonstrate the exact workflow your firm needs:
What information can the integration read during the interaction?
Both prospective clients and existing clients call law firms, but their needs are different.
Ruby can answer approved questions, take messages, recognize saved or VIP contacts, route calls, and use firm-provided information through its receptionist tools. A human receptionist may also be helpful when an existing client is emotional, confused, or needs a conversation that does not fit a standard path.
Clerx can be configured to recognize an existing client using CRM data, identify the relevant matter or assigned staff member, answer approved case-status questions, create a message or task on the matter, route the caller, and schedule an existing-client appointment.
The difference should be tested, not assumed. Ask both providers to demonstrate an existing client who:
Both companies can schedule appointments and support payment collection, but the underlying processes differ.
Clerx can:
Clerx is not limited to one payment provider. The exact workflow depends on the systems and payment methods used by the firm.
Ruby receptionists can use a firm's web-accessible scheduling system to book appointments. Ruby's published scheduling guidance says the calendar should be accessible in a browser without requiring a receptionist login. It also states that Ruby cannot schedule recurring appointments and generally cannot cancel or reschedule an existing appointment directly. In those cases, the receptionist can explain how to use the confirmation email or take a message for the firm.
Ruby also offers PCI-compliant service for collecting sensitive information or accepting payments. Its receptionists can enter payment information into the firm's secure payment link when the service is appropriately configured.
Ask both providers to demonstrate the entire process from qualification through payment and CRM update. A statement that both companies can "schedule and collect payments" does not show which steps are automated, which require a human, where the data is stored, or how exceptions are handled.
Clerx supports more than 40 languages across calls and written channels. This may be especially valuable for immigration, family law, criminal defense, estate planning, and other practices serving multilingual communities.
Ruby provides 24/7 human answering in English and Spanish. That can be a strong fit for firms that need callers in those two languages to reach a live person.
Before choosing, test:
Ruby may be the better fit for firms prioritizing live English-Spanish human reception. Clerx may be the stronger fit for firms needing broader multilingual intake across voice and written channels.
Ruby publishes pricing for both phone reception and live website chat. As of September 2, 2026, its principal receptionist plans include:
Ruby also publishes plans through 2,500 receptionist minutes. It says there are no separate activation, onboarding, setup, customization, or holiday-coverage charges. Ruby offers a money-back introductory period subject to time and usage limits.
Important billing details include:
Clerx does not publish standard pricing online. Clerx provides a customized quote based on expected call volume, selected channels, integrations, and workflow requirements. Before purchasing, the client receives its package price, included usage, overage rate, and applicable add-ons.
Clerx is month-to-month, with no required long-term commitment. Volume discounts are available.
The tradeoff is straightforward:
For either provider, calculate the complete configuration rather than comparing only the starting price. Include:
Ruby is the larger. It says it has served small businesses for more than 20 years. It serves law firms as well as healthcare, home services, financial services, agencies, and other small businesses.
That scale, operating history, and human workforce may appeal to firms that prioritize a proven virtual receptionist provider and want every caller to speak with an outside person.
Clerx is an AI-first, founder-led company built exclusively for law firms. Every client works directly with senior Clerx leaders, including CTO-led onboarding, founder access, and quarterly strategy reviews.
That model may appeal to firms that prioritize legal workflow depth, faster access to technical decision-makers, consistent automation, and a longer-term intake and client-communication layer rather than a general-business answering service.
Clerx may be the better choice when:
Clerx is the intake and client-communication layer connecting inquiries with the people and systems already running the law firm.
Ruby may be the better choice when:
Ruby's human service is a genuine differentiator. If a law firm believes that every caller should reach an outside person, replacing that person with AI would defeat the reason for choosing Ruby.
Choose Clerx when the deciding requirement is a customized, legal-exclusive intake system that completes repeatable work across channels, connects deeply with legal systems, and escalates exceptions directly to the firm's own staff.
Choose Ruby when the deciding requirement is that every caller or website visitor interact with a trained outside human receptionist.
Before deciding, ask each provider to demonstrate the same workflows using your firm's actual criteria. Listen to calls, inspect the resulting CRM records, test what happens when nobody answers a transfer, and calculate the complete monthly cost using realistic call length and website-chat volume.
That will tell you more than a generic AI-versus-human debate.
To see how Clerx would handle your firm's calls, messages, scheduling, payments, and CRM workflows, book a live Clerx demonstration.
Yes. Both can answer calls 24/7, gather lead information, schedule consultations, transfer callers, support payments, provide website chat, and connect information with legal software. Clerx uses an AI-first, legal-exclusive model, while Ruby uses live human receptionists supported by AI tools.
Ruby is primarily a human virtual receptionist service. Ruby uses AI to assist its receptionists through Call Nav, transcripts, sentiment analysis, and robocall filtering. Ruby's public materials state that these tools support rather than replace its human receptionists.
Clerx is generally the better fit for firms prioritizing legal-exclusive workflows, omnichannel intake, more than 40 languages, detailed CRM actions, existing-client automation, and unlimited AI website chat. Ruby may be better for firms that want every caller to speak with an outsourced human receptionist.
Clerx does not maintain a separate outside receptionist pool. Clerx can complete the firm's approved workflow, warm-transfer a caller to the firm's staff, create a task or message, alert the firm, or follow another approved escalation rule. Clerx does not charge an additional warm-transfer fee.
Ruby bills by receptionist minute. Billable time includes the period from answering through transfer or completion, hold time, and after-call information entry. Billable calls are rounded up in 60-second increments. Plans include a monthly allowance, and additional minutes are charged at the plan's overage rate.
It depends on the firm's call volume, call length, website-chat volume, channels, and required workflows. Ruby publishes minute-based phone pricing and per-engaged-chat pricing. Clerx provides a tailored monthly quote based on the firm's configured intake operation. Firms should request written estimates using the same realistic usage assumptions.
Ruby offers 24/7 live-staffed chat and charges by engaged chat. Clerx provides immediate AI website chat with unlimited chats in every package, legal qualification and scheduling workflows, CRM synchronization, online payment support, and an optional attorney video greeting.
Yes. Both advertise integrations with Clio and 8am MyCase. Ruby's published workflows include sending calls and messages into communication logs or lead inboxes and using intake forms. Clerx can be configured for detailed read-and-write actions involving contacts, leads, fields, notes, transcripts, tasks, alerts, appointments, payments, clients, and matters. Firms should ask each provider to demonstrate the exact actions they require.
Yes. Ruby receptionists can use supported web-accessible calendars and secure payment links. Clerx can qualify a prospective client, schedule free or paid consultations, collect through supported processors or payment links, record the result in connected systems, and track consultation revenue in the Clerx dashboard.
Ruby offers 24/7 human answering in English and Spanish. Clerx supports more than 40 languages across calls and written channels.
Ruby may be better when the firm prefers an existing client will speak with a virtual receptionist who can take a message, or route the call. Clerx may be better when the desired workflow requires using CRM or matter data, providing an approved status response, creating a task on the matter, or routing according to the assigned staff member.
9/1/2026
Estate-planning firms do not need every family and asset detail on the first call. They do need enough information to identify the right next step and give the attorney a usable handoff.
8/28/2026
DocketWise can organize immigration work after a matter enters the system, but the firm still needs a reliable way to answer, structure, and route the inquiry that comes first.
We use cookies to ensure you get the best experience on our website. For more information, please see our Privacy Policy.
