Smokeball Probate Intake: From First Call to a Reviewable Lead

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

The direct answer

Smokeball probate intake connects an initial conversation with a lead record that staff can review before opening or accepting legal work. Clerx can handle the configured conversation and send supported information into Smokeball. The firm still decides whom it represents, whether it can accept the engagement, and what happens next.

Smokeball’s official Clerx integration guide documents leads, contacts, call summaries, and consultation scheduling. That supports a concrete intake handoff. It does not make an AI conversation a legal assessment of probate rights or authority.

For a solo estate practice, the useful result is a reviewable inquiry rather than another message requiring the attorney to start again. The Clerx and Smokeball integration should be evaluated by inspecting that resulting record.

Separate the caller from the proposed client

A probate call may come from a surviving spouse, beneficiary, nominated executor, sibling, or someone simply trying to understand which office to contact. These roles should not collapse into one client identity.

Ask who is calling, whom the inquiry concerns, and how the caller describes their involvement. Preserve uncertainty. A person saying they were named executor is reporting information, not establishing that the firm has verified an appointment or authority.

Use the estate-planning intake question guide as a starting point for concise questions. Add only the probate distinctions that affect routing. An intake conversation does not need a complete asset inventory to determine that the attorney should review the request.

Avoid asking the receptionist to choose between family members or decide who controls an estate. A helpful first response can identify the right next conversation without answering those questions.

Capture the facts that change the next step

The first record usually needs contact details, the general reason for calling, the relevant location as reported, whether another attorney is involved, and any date the caller believes needs attention. The attorney should approve the actual questions.

Keep caller-reported dates separate from confirmed deadlines. If someone says a hearing is next week, preserve their words and send the inquiry through the approved review route. Do not calculate a filing deadline or assure them that the firm has time.

The intake-form design guide explains why more questions do not automatically improve intake. Ask what changes the destination, preparation, or urgency review. Defer detailed documents and legal conclusions to the firm’s approved process.

Decide what a lead means in your account

A lead is a business record describing an opportunity for review. It should not silently imply that the firm has accepted representation. The firm should define when staff may advance that record and what approval is required.

Clerx’s Smokeball page uses broader matter-creation language, while Smokeball’s support guide specifically describes leads, contacts, and summaries. Use the narrower demonstrated behavior as your acceptance standard. Ask the implementer to show which objects your configuration creates and whether any matter-creation action is enabled.

The guide to intake and practice-management responsibilities helps explain the boundary. Capturing an inquiry and managing accepted legal work are connected tasks with different decisions.

Make the summary useful to an attorney

A good summary should identify the caller, reported role, person whose estate is involved, broad request, relevant location, reported time concern, and agreed next step. It should clearly label what remains unknown.

For example: “Caller reports being the decedent’s daughter and a named beneficiary. Seeks help understanding whether the firm can review an estate administration issue. No documents reviewed. Requests a private callback Wednesday afternoon.” That is operational context, not a conclusion about standing or entitlement.

The intake and conflict-review framework supports the next stage. Collecting names can assist review, but a lead record should never claim that conflicts have been cleared merely because names were captured.

Route appointments according to the firm’s policy

Some firms allow an introductory consultation after a short screen. Others require staff review before offering time. Either can work if the caller is told accurately what has happened.

If direct booking is approved, verify the attorney, appointment type, length, format, time zone, and confirmation. Smokeball’s partner guide documents calendar-connected scheduling; it does not establish every appointment rule or payment arrangement in your account.

Use Clerx scheduling and payments to discuss the available configuration. Do not assume a payment integration follows from calendar access. Demonstrate booking and payment separately where a fee applies.

A request awaiting review should stay a request. Avoid an apparent confirmation that obliges staff to explain later that the attorney never accepted the meeting.

Keep other channels from restarting the inquiry

The same person may call, use the website, and send a text. The team needs an agreed way to recognize the existing inquiry and preserve the caller’s role.

Clerx website chat can support the initial conversation, while Clerx text messaging can support configured written communication. Confirm what information each channel sends into Smokeball. The partner’s documented call workflow does not independently prove identical behavior for every written channel.

Where matching is uncertain, have staff review before combining records. A household phone may be shared by people with different interests. The objective is a dependable history, not automatic consolidation at any cost.

Work through one realistic probate example

Consider a fictional Michigan solo practice receiving a Saturday call from an adult son. He wants to discuss his mother’s estate, says a sister has already contacted another lawyer, and asks whether he can book immediately. He does not know whether proceedings have started.

The intake should preserve those facts without selecting a legal theory. It should identify his preferred contact route and apply the firm’s booking rule. If the practice requires attorney review for disputed family situations, the next step is review rather than a general consultation slot.

On Monday, staff should find a lead containing the son’s reported role, his question, the uncertainty about proceedings, and the promised next action. They should not find an accepted matter with the son described as the estate representative unless someone actually verified and approved that status.

Now change the scenario. The caller is an existing client asking where to send a document. That should follow the existing-client route rather than produce another probate sales lead. Test both paths using new-inquiry and existing-client routing.

Michigan is the setting for this illustration, not a claim about state probate requirements. The workflow should use the firm’s own jurisdiction-specific instructions.

Inspect the handoff before launch

Use fictional calls involving an unknown role, shared phone number, missing email, uncertain date, and caller who cannot use an online form. Inspect what appears in Smokeball and what staff receive outside it.

The pre-launch testing guide provides a useful record of expected and observed behavior. Include a failed handoff and a repeat contact. A successful greeting proves little about the destination record.

Assign someone to review exceptions during the initial operating period. If staff must repair every summary, count that work and simplify the questions or record mapping. The right measure is usable reviewed inquiries, not the number of objects created.

Measure the record rather than assume the benefit

Track how many inquiries reach the correct review destination, how many require clarification, and how often staff repeat questions already answered. Sample summaries for role accuracy and next-step clarity.

These are proposed operating measures, not published Clerx customer outcomes. A firm may find that clearer summaries help more than adding another screening question. Another may discover that appointment rules are the main source of repair work.

The commercial benefit should be demonstrated through your own baseline and pilot. Better structure can support a lean team, but no intake system guarantees signed engagements or correct legal decisions.

Specify the review queue staff can maintain

Decide where the probate reviewer finds new requests and how they mark the next action. A useful queue might distinguish awaiting initial review, awaiting contact, consultation offered, and closed without further action. These are proposed business categories, not assumed Smokeball controls.

Keep the categories few enough that staff can apply them consistently. If the practice cannot explain the difference between two statuses, combining them may make the record easier to maintain. The owner should know which inquiries remain unresolved at the end of the day.

Agree how a weekend inquiry becomes Monday work. An email copied to several people does not establish ownership. Choose the reviewer and backup before launch, and ask them to perform the demonstration using their normal account access.

Evaluate the information staff still have to reconstruct

During the pilot, ask the reviewer what they had to find outside the lead record. Repeated searches for the caller’s role, preferred contact method, or requested service may reveal a mapping problem rather than a need for more questions.

Review a small set of inquiries together and compare the conversation with the summary. Look for legal conclusions that were never stated, reported facts presented as verified, and missing uncertainty. Correct the instruction or handoff that caused the problem.

Keep a record of the change and repeat the affected scenario. The acceptance standard is whether the next reviewer can act with appropriate context. A polished summary that confidently misstates the caller’s role is less useful than a shorter record that preserves what is unknown.

This gives the firm a concrete buying criterion: the integration should reduce avoidable reconstruction while leaving professional decisions where they belong.

Bring a record-level requirement to the demonstration

Ask the implementer to create a fictional probate inquiry in front of the reviewer. Specify which information must arrive, where uncertainty should appear, and what action the reviewer should take. This is more useful than asking whether the integration is comprehensive.

Include a caller with no email address and a person who does not know their formal role. The summary should remain usable without filling those gaps with invented information. If a required field prevents delivery, agree how the workflow handles it before live inquiries arrive.

Keep the demonstration result with the written scope. That gives the firm a concrete reference when it later adds another intake branch. A new practice-area script should preserve the same acceptance boundaries even when its questions differ from probate.

Frequently asked questions

Does Clerx work with Smokeball?

Smokeball publishes a Clerx integration guide covering leads, contacts, call summaries, and scheduling. Confirm plan availability and show the specific workflow in your account.

Should every probate call create a matter?

The firm should decide. A reviewable lead is often the appropriate initial destination while representation, conflicts, and acceptance remain unresolved.

Can AI establish an executor’s authority?

No. Record what the caller reports and route verification to the firm. The receptionist should not decide legal authority or entitlement.

Can the caller and proposed client be different people?

Yes. Preserve their separate identities and reported roles, and let the attorney determine representation and information-sharing boundaries.

Can probate consultations be booked automatically?

Where the firm approves direct booking and the integration is configured, scheduling can be supported. Test the exact appointment and exceptions.

Does scheduling establish payment support?

No. Calendar access and payment handling are separate capabilities. Verify any proposed payment route independently.

What if the caller does not know the case status?

Preserve the uncertainty. Gather the approved minimum information and assign review instead of inventing the missing status.

What should a Smokeball demo show?

A fictional new lead, existing client, uncertain caller role, correct summary, approved booking path, and recovery when the record does not arrive.

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.