What AI Receptionist Works With MyCase for Estate Planning Law Firms?

By Attorney Michael Brunman, Co-Founder and CEO of Clerx

An AI receptionist for an estate-planning firm using MyCase should answer inquiries promptly, identify the type of planning or administration help requested, collect firm-approved preliminary details, route exceptions, schedule the appropriate consultation, and place a usable record into the firm's MyCase workflow. Clerx provides this first-response and intake layer while MyCase remains the firm's practice-management system.

That division matters. Estate-planning intake is rarely one generic conversation. A caller may want a first will, a trust review, an update after marriage, help after a death, guidance about incapacity planning, or an appointment for an aging parent. If every inquiry receives the same questionnaire and calendar link, the firm creates work for its staff and friction for the family.

What does an AI receptionist add to MyCase?

MyCase can organize leads, contacts, matters, documents, calendars, communications, and billing. An intake layer handles the live moment before those records are complete: the call, chat, or text in which a person explains why they reached out and expects a useful next step.

The Clerx integration with MyCase connects these roles. Clerx can answer the inquiry, use the firm's approved questions and rules, qualify the request at a preliminary level, schedule when appropriate, and send the resulting intake information into MyCase. The lawyer and staff continue to control conflicts analysis, legal judgment, matter acceptance, and the client relationship.

This is different from simply forwarding a voicemail. A structured intake record should tell the team who contacted the firm, what broad service was requested, what relevant timing was mentioned, which consultation path was offered, and what must happen next.

Why estate-planning intake needs separate paths

Estate-planning firms often serve several related but operationally different needs. A practical first-response workflow should distinguish at least:

• new lifetime planning;
• review or amendment of an existing plan;
• trust administration after a death;
• probate or estate administration;
• elder-law or long-term-care planning, if offered;
• guardianship or incapacity-related inquiries, if offered;
• current-client questions;
• professional referrals.

The questions, urgency indicators, appointment type, preparation instructions, and responsible attorney may differ across those paths. The firm's estate-planning intake questions should therefore be modular, not a single exhaustive script.

The purpose of the first interaction is not to gather every asset, beneficiary, medical fact, or family dispute. It is to collect enough information to route the inquiry safely and make the next conversation productive.

A practical Clerx and MyCase workflow

1. Answer and identify the caller

The workflow begins with a prompt response through the channel the firm supports. On an inbound call, a law-firm AI receptionist can greet the caller using the firm's name and explain that it will collect preliminary information for the team.

Start with identity, contact details, preferred language, and whether the person is a new inquiry, current client, family member, or professional referral. Current clients should enter the firm's current-client route rather than repeating new-lead screening.

2. Classify the service requested

Use a plain-language question such as: “Are you looking to create or update a plan, or are you contacting us because someone has died or can no longer manage their affairs?”

The answer determines the next branch. A person requesting a will and trust consultation should not receive the same sequence as a successor trustee asking about administration. The law-firm intake form framework is useful here: ask only what the next decision requires.

3. Collect limited preliminary facts

For lifetime planning, the firm may approve questions about residence, marital status, minor children, whether a prior plan exists, broad planning goals, and whether a deadline or major life event prompted the inquiry.

For probate or trust administration, the workflow may ask the caller's relationship to the deceased person, date and place of death, county, whether a will or trust is known to exist, whether a court matter has started, and whether the caller is aware of an upcoming deadline.

These are routing facts, not a legal analysis. The system should not decide whether probate is required, interpret a trust, predict tax consequences, or advise the caller about rights.

4. Capture names for the firm's conflicts process

The intake may collect the names the firm has determined are necessary for a preliminary conflict search, such as the prospective client, spouse, deceased person, fiduciaries, or other involved parties. It should explain why limited names are being requested and avoid inviting a detailed confidential narrative before the firm is ready to receive it.

Automation can collect and normalize names. It should not make the final conflicts decision. That responsibility remains with the firm's lawyers and approved staff.

5. Apply firm-approved fit rules

Preliminary qualification can check operational criteria such as service type, geographic coverage, minimum consultation requirements, and whether the inquiry fits a service the firm offers. It can also detect an exception that requires staff review.

Qualification should not become legal judgment. A system may route “existing trust administration” to the correct team. It should not conclude that a person has a viable contest or that a proposed plan will achieve a legal or tax result.

6. Offer the right consultation

Once the request follows an approved path, offer the correct calendar, duration, attorney, location, language, and fee. If the firm charges for consultations, its paid-consultation workflow should define when payment is collected, what happens when payment fails, and whether an appointment is held or confirmed.

Avoid the vague ending, “Someone will call you.” A qualified prospect should receive a specific next step during the same interaction whenever the firm's rules permit it.

7. Create a clean MyCase handoff

The MyCase record should be concise enough to scan and complete enough to act on. A practical handoff includes:

• verified contact information;
• caller type and preferred language;
• broad service category;
• relevant preliminary facts;
• names collected for conflicts review;
• stated timing indicators;
• qualification outcome;
• consultation details or assigned task;
• source and original channel;
• any escalation or exception.

The firm's configuration should define whether the information enters as a lead, contact, activity, note, task, appointment, or matter-related record. Confirm the exact mapping during implementation rather than assuming every firm uses MyCase in the same way.

Build an exception path before launch

Estate-planning intake becomes risky when the normal script is used for an unusual situation. Define what happens when:

• the caller reports an immediate safety issue;
• a person appears to lack capacity to participate;
• family members disagree about who the client would be;
• a current client asks for legal advice;
• the caller will not provide a name;
• a possible adverse party contacts the firm;
• no appropriate consultation time is available;
• the requested service is outside the firm's scope;
• payment cannot be completed;
• the caller needs a language the scheduled attorney does not speak.

The AI should recognize the firm's observable trigger and follow the approved transfer, alert, message, or review path. It should not decide capacity, representation, urgency, or legal rights.

Coordinate calls, chat, and text

Many prospects begin on one channel and finish on another. A person may call from work, request a link by text, and later use website chat for a law firm to confirm the appointment. Another may start with structured SMS intake because discussing a family matter aloud is inconvenient.

The goal is one intake journey. The firm should avoid creating a new lead each time the channel changes. Identity matching, clear system ownership, and consistent disposition labels help MyCase remain the reliable record.

Protect the client experience

Estate planning is personal even when the legal task is routine. The intake tone should be calm, patient, and direct. Do not make elderly callers navigate a long phone tree. Do not ask grieving families to provide a complete history before explaining what happens next. Do not describe automation as a lawyer.

The firm's script should state that the interaction is preliminary, that the firm has not yet agreed to representation, and that legal advice comes from an attorney. The workflow should also avoid sensitive details in text previews or appointment reminders that may appear on shared devices.

Test the workflow with real scenarios

Before launch, test at least:

1. a first-time will and trust inquiry;
2. a plan-update request from an existing client;
3. a probate inquiry after a recent death;
4. a successor trustee requesting help;
5. a caller seeking a service the firm does not offer;
6. a Spanish-speaking prospect;
7. a possible conflict;
8. a caller with an imminent date;
9. no calendar availability;
10. a failed payment;
11. an unanswered transfer;
12. a duplicate contact already in MyCase.

Then review the record created in MyCase. The intake checklist for law firms can help verify ownership, routing, scheduling, record quality, and exceptions.

Measure the workflow after launch

Do not measure success only by calls answered. Review completed-intake rate, qualified inquiry rate, consultation-booking rate, time to appointment, show rate, payment completion, staff correction rate, duplicate records, escalation response, and lead-to-client conversion.

The law-firm intake metrics that matter should be segmented by service type and source. If probate inquiries book at a lower rate than planning inquiries, the issue may be a confusing path, limited attorney availability, or a weak handoff rather than lead quality.

Frequently asked questions

What AI receptionist works with MyCase for estate-planning firms?

Clerx integrates with MyCase to provide a first-response and intake layer for calls and other supported channels. It can collect firm-approved details, qualify at a preliminary level, schedule, and pass structured information into the firm's MyCase workflow.

Does an AI receptionist replace MyCase?

No. MyCase remains the practice-management system. Clerx handles live intake and communication before and around the structured handoff.

Can it distinguish estate planning from probate?

Yes, when configured with the firm's approved routing questions. Each branch can use different questions, calendars, instructions, and escalation rules.

Can it conduct a conflict check?

It can collect involved names and support the firm's preliminary search process. Lawyers and authorized staff should retain responsibility for conflicts analysis and clearance.

Can it book a paid consultation?

Yes, if the firm's workflow and connected systems support the approved calendar and payment process. The firm defines the fee, confirmation, failure, and exception rules.

Can it give estate-planning advice?

No. It should not recommend documents, interpret a will or trust, predict tax treatment, or replace attorney judgment.

What information should the first intake collect?

Identity, contact details, caller type, broad service category, limited routing facts, involved names required by the firm, timing indicators, and the next action.

How should current clients be handled?

Identify them early and route them to the firm's current-client process rather than repeating prospective-client screening.

Can the workflow support more than phone calls?

Yes. Clerx supports intake across calls, website chat, text messaging, and other configured channels so the firm can preserve one consistent journey.

How should firms evaluate the integration?

Test normal and exception scenarios, inspect the resulting MyCase records, confirm calendar and payment behavior, and review conversion and correction metrics after launch.

Book a demo with Clerx today.