🎉 Top 5 AI Agent for Law Firms | Read the article →
Clerx
All Posts

11/13/2026

7 Records and Actions to Check in a Smokeball Receptionist Demo

Before choosing a Smokeball receptionist, ask to see the real lead, contact, summary and appointment from a fictional call.

Software IntegrationsSmokeballLaw Firm OperationsAI ReceptionistLegal Intake
Row of white folder tabs marked with shapes, the center hexagon tab highlighted in blue above a blue check mark.

By Michael Brunman, Co-Founder & CEO of Clerx, Former Litigator

A Smokeball receptionist demo should end with more than a convincing voice. Your team should see the lead, contact, summary, appointment, and unresolved request it will actually use. The most useful test follows one fictional inquiry from the conversation through the staff's next action.

Use these seven checks to evaluate the proposed configuration. They are buying questions, not a claim that every receptionist supports every action. When a function is outside the current scope, ask for a clear answer and decide whether the remaining staff step is acceptable.

Start with your firm's required outcome

For a solo or small consumer-facing firm, a useful outcome might be a qualified inquiry ready for review, a correctly booked consultation, or an existing-client message routed to the right employee. These are different results, even when all three begin with a phone call.

Bring a fictional scenario based on the firm's real service mix. An estate-planning firm can use an existing-document review request. A mixed probate and real-estate practice should choose an inquiry that reveals which team should respond. Keep the facts fictional and avoid exposing private client information in a sales demonstration.

The Clerx Smokeball integration provides the relevant product relationship. Smokeball's official Clerx support guide documents leads, contact creation or matching, summaries, and scheduling with calendar sync. Those documented functions are a starting point for proof, rather than a substitute for seeing your proposed setup.

1. The new lead appears with useful information

Ask the provider to handle an eligible fictional new inquiry and then show where it appears in Smokeball. Have the employee who normally reviews inquiries locate it, rather than relying entirely on the salesperson's navigation.

Check the name, contact details, service request, and relevant screening information. The record should preserve what the person actually said, including important uncertainty. A polished summary that changes the substance of the request is less useful than a clear record of incomplete information.

Also ask what triggers lead creation. Is it every completed conversation, a particular disposition, or another configured rule? What happens to an inquiry outside the firm's services? The right answer depends on the firm's process, but it should be explicit.

Do not equate a lead record with a retained client or accepted legal matter. The software organizes the inquiry. The firm controls conflicts review, consultation decisions, engagement terms, and acceptance.

2. The contact action is clear for new and returning callers

A new contact and a returning caller should not be treated as the same demonstration. Ask to see both. Then use a fictional shared household number or a different spelling of a name to expose uncertainty.

Inspect whether the proposed configuration creates, matches, or asks staff to review the contact. Ask which information supports the match and what happens when the system cannot confidently select a record. Do not infer a universal deduplication capability from one successful match.

The new-lead versus existing-client routing guide explains the operational reason for this distinction. Existing clients should not have to repeat new-prospect screening simply because they called the public number.

At the same time, matching a telephone number does not establish who is speaking or authorize disclosure of case details. For the demonstration, focus on identifying and routing the request without assuming access to confidential information.

3. The call summary supports the next staff action

Read the resulting summary alongside the fictional facts used in the call. Does it capture who called, what they want, relevant context, what the receptionist communicated, and what should happen next?

Inspect the location of the summary, its association with the contact or lead, and the available call details. Ask staff whether they could act from the record without listening to the whole interaction. A summary should reduce reconstruction work while preserving the information that matters.

Clerx AI Receptionist is relevant here because it connects the conversation with structured intake and handoff. The test should examine the output of that configured conversation, not an unrelated sample summary prepared in advance.

Include one correction during the call, such as a changed telephone digit or an updated preferred contact time. Check whether the final record preserves the correction clearly. This is a practical accuracy test, not a demand for an artificially difficult trick call.

4. The right consultation reaches the right calendar

Ask for a booking under the firm's actual rules: consultation type, attorney, duration, location, availability, and any required screening. Then inspect the appointment in the destination calendar.

The demonstration should distinguish a completed booking from an appointment request awaiting review. Have the caller ask for an unavailable time. The response should describe an approved alternative or staff route rather than inventing capacity.

For paid appointments, Clerx Scheduling & Payments lets prospective clients schedule and pay for their consultation in one booking flow. Confirm the exact calendar and payment connection included in the proposed Smokeball setup.

Appointment creation does not prove that the system can edit or cancel an existing event. If those actions matter to the firm, request separate evidence. It is better to know that staff own a specific change than to discover the boundary after a client relies on an inaccurate confirmation.

5. An existing-client request has an appropriate destination

Use a current-client scenario that does not require legal advice: someone wants to reach their assigned employee or ask how to submit a document through the firm's approved route.

Check whether the conversation follows the firm's existing-client path and whether the message identifies the intended recipient. Inspect where staff will find it. If the proposed configuration does not create a task or notification automatically, identify the manual step and owner.

Do not assume the receptionist can read live matter status or update an existing case merely because it can create a lead or match a contact. Each read or write action needs its own evidence and appropriate boundaries.

For a small firm, the important result is a usable service request without disrupting the new-inquiry process. A receptionist should help organize communication while attorneys and staff retain judgment about what may be disclosed or answered.

6. A failed transfer leaves a recoverable request

Ask the provider to transfer a call while the designated recipient is unavailable. Observe what the caller hears and inspect the record left behind.

For Clerx, the retry and fallback sequence is configured for the firm, followed by a message if nobody answers. Confirm which recipients, hours, and fallback instructions are in scope. Do not assume that a transfer feature includes a staffed provider-side human answering team.

The warm-transfer guide helps frame the difference between transferring, booking, and taking a structured message. In a demo, the failed transfer is as informative as a successful connection.

Staff should be able to identify the unresolved request and the next action. If the caller disconnects, ask what information remains available and how the firm would follow up under its contact policies. Avoid promises about callback timing that the firm has not approved.

7. The quoted channel produces the promised handoff

If the proposal includes only calls, finish the demonstration by confirming that scope. If it also includes website chat or text messaging, test the selected channel separately.

Use the same fictional service request and inspect the actual destination. Confirm which details move, which remain in another system, and what staff must do. Do not extend documentation about inbound calls to every communication channel by assumption.

This check also keeps the commercial comparison fair. A multi-channel quote should identify the selected channels and their real workflow, while a phone-only proposal should be judged on its stated scope.

The point is not to demand every possible connection. It is to establish that the feature the firm is buying produces the staff result the quote describes.

Turn the demonstration into a clear purchasing decision

Record each result in plain language: shown successfully, needs configuration, outside scope, or awaiting evidence. Avoid an inflated numerical score that gives minor cosmetic details the same weight as a missing booking or unusable record.

Decide which gaps are acceptable staff tasks. A small firm may be comfortable reviewing an uncertain contact match but unwilling to re-enter every new inquiry. Another may want staff approval for all consultation requests. The service should support the operating choice, rather than silently making it.

Ask for the required Smokeball subscription, integration prerequisites, selected channels, setup responsibilities, and complete commercial terms. Current Clerx pricing is tailored to the firm's scope and volume. A demonstration and a written proposal should describe the same service.

Repeat the critical checks before launch

A sales demo establishes whether the proposed approach is worth pursuing. It does not replace testing the firm's final configuration. Names, service descriptions, consultation fees, routing recipients, and hours can change the behavior materially.

Use the AI receptionist go-live testing guide with the approved configuration. Include the person responsible for review and ask them to complete the actual next action.

After launch, sample completed conversations and records together. If a record is missing or unclear, preserve the original interaction and ask the provider to help identify the gap. Do not blindly recreate records without checking what may already exist.

The best purchasing evidence is practical: the prospective client reaches a suitable next step, and the firm's employee can find and use the result. Those seven checks make that evidence visible before the firm relies on the service.

Frequently asked questions

What should a Smokeball receptionist demo show?

The conversation and its resulting lead, contact action, summary, appointment, service request, transfer fallback, and any selected additional-channel handoff.

Is a marketplace listing enough evidence?

It establishes a documented relationship and advertised scope. Demonstrate the exact actions the firm intends to rely on.

Should every call create a new lead?

Not necessarily. The firm should define how new prospects, returning callers, existing clients, and unsuitable inquiries are handled.

Does contact matching authenticate the caller?

A match supports record organization but should not automatically authorize disclosure of confidential information. Apply the firm's identification and access rules.

Can a lead record mean the firm accepted representation?

No. The firm retains legal assessment, conflict review, engagement, and acceptance decisions.

How should paid consultation booking be tested?

Show the consultation selection, available time, payment during scheduling, and resulting appointment. Confirm the proposed calendar and payment system.

Should we test website chat separately from calls?

Yes, if it is included. Each selected channel's record actions should be verified rather than inferred from phone documentation.

What if a required action is outside the current scope?

Identify the staff step and decide whether it is acceptable. Ask for clear evidence of any proposed extension before depending on it.

Book a demo with Clerx today.

About the author

Michael Brunman is Co-Founder & CEO of Clerx, helping law firms improve client intake and communication. A former litigator, software engineer, and McKinsey consultant with an MBA from Harvard Business School, he brings legal, technical, and business experience to the challenges of running a law firm.

Share this article:


We use cookies to ensure you get the best experience on our website. For more information, please see our Privacy Policy.