7 Questions About DocketWise Case Creation to Ask Before Buying AI Intake

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

Before buying AI intake for DocketWise, ask seven questions about case creation: what triggers it, which information is required, whose identity is recorded, how the inquiry source is preserved, where the context lands, who reviews the case, and what happens when the person contacts the firm again.

These questions turn a broad integration claim into a practical buying conversation. The goal is a usable record for a small immigration firm's next step. Creating a software case is not the same thing as accepting representation, completing a questionnaire, or making a legal assessment.

Start with the documented connection

The official DocketWise Clerx guide describes inbound multilingual screening, new case creation after screening against firm criteria, and intake information plus a call summary delivered to the case.

That establishes a useful baseline for the Clerx DocketWise integration. Your demonstration should then show the configuration being proposed for your firm. Do not infer additional actions, such as updating an existing case or calculating a deadline, from the fact that new case creation is supported.

Use fictional information during evaluation. One ordinary new inquiry, one incomplete inquiry, and one repeat caller are more revealing than an ideal demonstration alone. Ask the employee who will review intake to participate and locate the information without coaching.

1. What triggers case creation?

Ask the provider to describe the trigger in ordinary language. Which conversation reaches the case-creation step, and which takes a different route? What happens if the person does not meet the firm's operational criteria or leaves before the conversation is complete?

The answer should refer to the firm's approved service and routing rules. A broad immigration inquiry, an existing-client message, and an unrelated professional call need not produce the same record.

Do not accept an unexplained statement that everything is automatic. Ask for one fictional inquiry that should create a case and one that should not. Observe the actual outcome and ask who changes the rule when the firm's service mix changes.

The new-lead and existing-client routing guide offers a useful starting taxonomy. The firm decides its process; the receptionist should implement it without deciding legal eligibility or accepting a client.

2. What minimum information is required?

A caller may provide a phone number but not an email, know the broad request but not its legal name, or be unsure how to spell another person's name. Decide which information is essential for the next step and which staff can clarify later.

Ask the provider to demonstrate incomplete information. Does the setup preserve a useful inquiry, request clarification, or take another approved route? Which fields are required by the connection, and which are requirements your firm has chosen?

Those are implementation questions, not facts to infer from a general integration listing. A system can only be evaluated fairly when the parties agree on what a useful preliminary record means.

The intake forms guide explains progressive collection. For the first call, avoid requesting an entire immigration history simply because a later questionnaire will need more detail.

Record uncertainty faithfully. A summary should distinguish a date the person confirmed from one they approximate. The receptionist should not fill missing facts with a plausible guess to make the case look complete.

3. Whose identity will the record describe?

An immigration inquiry can come from the prospective client, a spouse, an adult child, an employer, or another person. The caller and the person seeking legal help are not always the same individual.

Ask where the proposed setup preserves the caller's role and the subject of the inquiry. Can the reviewing employee understand who spoke, who may attend a consultation, and whom to contact? Which relationships are structured and which appear in the summary?

Do not assume a single phone number identifies one person. Family members may share a number, and a relative may call on someone else's behalf. The workflow should preserve that distinction for staff instead of silently converting the caller into the client.

The safe callback instructions guide is relevant here. A number, contact preference, and permission to leave a particular message answer different questions.

Ask the demonstration caller to say, “I am calling for my father.” Then inspect the record. If a staff member cannot see that relationship, identify a supported way to preserve it before relying on the workflow.

4. Can staff identify where the inquiry came from?

Ask what source information the firm wants and what the proposed setup can actually capture. A tracking phone number, a website entry, a referral name, and the person's own explanation are different evidence.

Do not assume the receptionist can infer all marketing sources or populate every attribution field. Show the proposed field or summary location. If the firm wants the caller's answer to “How did you hear about us?”, confirm the approved wording and how an uncertain response is preserved.

The lead-attribution guide explains why interactions and opportunities should remain distinct. A repeat call may continue an earlier inquiry rather than represent a new campaign result.

Use available source information to support an operating decision, not to manufacture precision. A caller saying they found the firm online may not know whether the route was an advertisement, organic search, a directory, or an AI answer. Preserve what is known and avoid inventing the rest.

5. Where do the answers and summary land?

Open the resulting DocketWise case. Ask the reviewing employee to locate the reason for the call, key screening information, unresolved questions, and the intended next action. A demonstration is incomplete if it ends when the phone conversation ends.

The partner guide supports intake information and a call summary on the new case. Confirm the precise fields, note location, and permissions in the configuration offered to your firm. A broad claim that records synchronize does not replace inspecting them.

The DocketWise intake workflow article gives wider context for the first-call handoff. For buying, focus on whether staff can continue the inquiry without listening to a recording simply to discover the next task.

A transcript can be useful evidence, but length alone is not quality. A concise summary should preserve the person's request and uncertainty. The firm can then define what belongs in structured fields, what belongs in a note, and what needs further review.

Also verify channels separately. Documentation for Clerx AI Receptionist and its inbound DocketWise workflow does not automatically establish the same case action for website chat, SMS, or outbound calls.

6. Who reviews a newly created case?

Assign a person or role responsible for the first review. Specify what they check and how they decide the next operational action. Automation can make a record available; the firm's process makes it useful.

The reviewer may need to clarify contact information, assess whether the appropriate consultation route was followed, or request attorney review. These are different tasks from legal analysis and should have clear ownership.

If the inquiry reaches a consultation, confirm that journey independently. Clerx lets prospective clients schedule and pay for their consultation in one booking flow. Clerx Scheduling & Payments addresses that experience; case creation alone does not establish every booking or payment action inside DocketWise.

Detailed immigration information may belong in a later questionnaire. DocketWise Smart Forms support that native stage. Ask who selects the appropriate questionnaire and reviews its response. Do not assume the first-call integration automatically completes those steps.

Make software status and legal status understandable to the team. A newly created case is not a completed conflicts review or engagement. The receptionist supports response and structure, while attorneys retain professional judgment.

7. What happens when the person calls again?

Repeat the fictional inquiry with the same phone number, then try a family member using that number. Ask which identifiers the configuration uses and what happens when they are ambiguous.

The official case-creation guide does not establish every possible matching or existing-case update action. Request documented or demonstrated behavior instead of assuming the system will append correctly or never create another record.

An uncertain repeat contact should have an understandable staff-review route. The goal is to preserve the conversation without attaching information to the wrong person or treating an existing-client request as a new intake opportunity.

Our DocketWise case-status calls guide covers service requests separately. Keep that distinction in the demo: asking to reach an assigned team is different from asking the firm to consider new work.

If a second case appears under the proposed configuration, ask how staff will recognize and handle it. New case creation can still be useful when its limits and review responsibilities are clear. An unsupported promise of perfect matching makes the buying decision less reliable.

Turn the demonstration into a concise buying record

Record each tested action, the resulting destination, prerequisites, configuration owner, and unresolved question. A short written scope should describe the setup the firm is buying rather than reproduce every feature on a website.

Compare quotes against that scope. Clerx pricing is tailored to the firm's needs, so include the required record actions and selected channels when requesting a proposal. Setup and ongoing changes belong in the commercial conversation as well as the technical demonstration.

The strongest result is a conversation and case that staff understand. The seven questions help an immigration firm judge that result without confusing technical case creation with legal acceptance or relying on a generic integration logo.

Frequently asked questions

Does automatic case creation mean the firm accepted the client?

No. A DocketWise software record and a decision to accept representation are different events. The firm continues its approved conflicts, consultation, and engagement process.

Should every caller become a new DocketWise case?

Define the creation trigger and exclusions under the firm's process. New inquiries, existing-client requests, and unrelated calls can require different routes.

Which Clerx DocketWise actions are publicly documented?

DocketWise documents inbound screening, new case creation after screening against firm criteria, and delivery of intake information plus a call summary to the case.

Can we assume an existing case will be updated?

No. Verify that action separately. New case creation does not establish matching rules, duplicate prevention, or updates to an existing case.

What if the person cannot answer every question?

Test the proposed incomplete-information route. Distinguish connection requirements from your firm's chosen requirements and define what staff will clarify later.

Can the caller and prospective client be different people?

Yes. The demonstration should show how the proposed setup preserves the caller's role and the person who may need help, including shared contact details.

Does a call-created case complete a Smart Form?

Not by itself. Questionnaire selection, invitation, completion, and review are distinct actions. Confirm any proposed automation of those steps separately.

What should the reviewer be able to find quickly?

The person's request, relevant screening information, identity and contact context, unresolved questions, and intended next action. Inspect the actual case with the employee who will use 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.