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

11/19/2026

Lawcus Intake Pipeline Stages: Separate Contacted, Booked, and Hired

A stage change can activate work, so each label should represent an event the team can verify.

Small Law FirmsLaw Firm OperationsPipeline ManagementLawcusLegal Intake
An envelope icon, a calendar, and a folder stand on three rising platforms.

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

A Lawcus intake pipeline should show what has actually happened to an inquiry and what the team must do next. Contacted, consultation booked, consultation completed, and hired are different outcomes. Treating them as one broad "qualified" stage can hide work and activate the wrong follow-up.

Lawcus lets firms manage lead stages and build workflows around stage movement. That makes stage design an operating decision, not simply a choice of labels for a board. For a small firm, a few clearly defined stages can be more useful than a detailed pipeline that staff interpret differently.

This guide explains how to design those boundaries for a Lawcus-using practice receiving inquiries through a receptionist, forms, or its own staff. The examples are proposed firm policies, not automatic Clerx settings or legal conclusions.

Start with the business event behind each stage

Lawcus's lead-stage guide describes configurable progression through the intake pipeline. The exact labels in your account may differ. Before changing them, write a plain-language meaning for each stage your team uses.

A useful definition includes the evidence required to enter, the person responsible for the next action, and what should happen if progress stops. "Contacted" might mean a useful conversation occurred, while "attempted contact" should not suggest the person answered.

The existing Lawcus intake overview explains the broader path from inquiry to legal work. This article addresses the narrower control point: how pipeline movement should reflect real events and govern the next operational step.

Separate captured from contacted

A new lead record tells the firm that information exists. It does not prove anyone held a useful conversation or that the person understood the next step.

For example, a form submission with a name and phone number may be captured but not contacted. A telephone inquiry answered by an approved receptionist may include a meaningful conversation, but the team should still decide whether that counts as contacted for its reporting purpose.

Lawcus's official Clerx integration guide documents inbound lead, contact, and summary handling. It does not establish that every firm should move a record into a particular pipeline stage after every call.

Use the Clerx-Lawcus integration as the capture connection, then verify any intended stage action separately. A successful synchronization label should not substitute for a meaningful business definition.

Separate contacted from ready to book

A person can speak with the firm without being ready for direct scheduling. The request may be outside the ordinary service category, may involve an existing client, or may need attorney review before a meeting is offered.

The intake process should preserve that distinction. A caller who asks whether the firm can handle an unusual immigration issue may need a review request rather than a standard consultation link. The assistant should not make a legal eligibility decision to clear the booking gate.

Define operational criteria using the intake question framework. Ask enough to choose the approved route, while keeping legal assessment with attorneys.

If the term "qualified" remains in the pipeline, explain precisely what it means. It may mean the inquiry meets preliminary firm-defined routing criteria, not that an attorney has accepted the case or assessed its merits.

Separate booked from attended

An appointment on the calendar means time has been reserved. It does not mean the prospect attended, the attorney completed a consultation, or the firm offered representation.

For firms using consultation scheduling, define the booking event and the later attendance update separately. Decide who records a no-show, a cancellation, and a completed meeting. Do not let all three outcomes remain indefinitely in the same active booking stage.

Lawcus's appointment-scheduled trigger guide describes native booking-page events. If that event updates a stage in your process, verify the source and configuration. Do not extend it automatically to every externally created calendar event.

The no-show reduction guide addresses attendance communication. Stage design adds a related discipline: report the result that actually occurred rather than assuming every booking becomes a consultation.

Separate consulted from hired

A completed consultation is an important intake outcome, but it is not interchangeable with acceptance of representation. The firm's attorneys must define the engagement process and the evidence staff need before recording a hired outcome.

Lawcus's lead-to-matter guide describes the software conversion operation. That is a product action. Whether the firm should perform it in a specific situation depends on its approved business and legal process.

Avoid telling a prospect that the firm represents them merely because a matter object exists. Software terminology and legal relationships are not identical. The team should know when a record is an intake container and when the firm's engagement requirements have been completed.

For a three-attorney estate-planning firm, the consultation lawyer may own the decision, while an assistant records the result once the authorized instruction is received. That is a proposed ownership model, not a required Lawcus configuration.

Use stage triggers deliberately

Lawcus's Lead Moved to Stage trigger guide documents workflows initiated by changes to an existing lead's stage. It allows firms to select a stage scope and apply entry conditions before actions run.

The practical implication is straightforward: a stage change can have consequences. Moving a card to tidy the board may activate communications or tasks if the workflow has been configured that way.

Before enabling an action, ask what evidence supports entry to that stage. If a person was merely sent a booking link, a workflow intended for a confirmed consultation should not run unless that is the firm's deliberate design.

Keep the entry rule readable. A new staff member should be able to understand why the workflow ran without reconstructing several undocumented exceptions. More automation is not automatically better control.

Decide who can move a lead and why

Stage changes can come from staff activity or configured automations. List the expected source for each important transition and identify who reviews unusual results. Do not assume the receptionist connection itself owns every movement.

Clerx's inbound receptionist can capture the conversation and support configured next steps. A specific Lawcus stage update, native trigger, or downstream action still needs verification in the proposed deployment.

If a staff member corrects the record after a call, preserve the distinction between the caller's account and the firm's reviewed conclusion. A summary should not silently turn an uncertain fact into a verified one because the lead moved forward.

The intake quality-assurance guide offers a broader review framework. Apply it to recurring stage corrections rather than treating every correction as an isolated employee mistake.

Give stalled leads a visible next action

An active stage should not become a storage location for inquiries nobody intends to handle. Define the next action and owner, and distinguish waiting for the prospect from waiting for the firm.

For instance, an immigration inquiry may be waiting for a safe callback time supplied by the prospect. Another may be waiting for an attorney to review whether the firm offers the requested service. The underlying reasons differ even if both have no consultation booked.

The lead-recovery guide explains follow-up more broadly. Within Lawcus, use a manageable policy that stops or changes communication when the inquiry progresses, declines, or requires human judgment.

Do not continue a generic booking sequence after someone has asked for a person or declined further contact. Confirm the actual conditions and channel policies in the configured workflow rather than inventing a universal automatic stop.

Preserve appropriate closed outcomes

Not every inquiry should become a client. A firm may decline, refer, lose contact, or close an inquiry after the prospect chooses another route. Accurate closed outcomes protect the usefulness of both the pipeline and its reporting.

The declined-inquiry guide explains how to close a conversation without leaving the person uncertain. Stage design should support that explanation instead of making a closed record appear as a still-active prospect.

Avoid recording every non-retained inquiry as the same loss reason. A service mismatch, an unanswered callback, and a completed consultation followed by a decision not to hire require different operational improvements.

These are reporting recommendations. They are not claims that every suggested category exists as a default Lawcus field or that Clerx automatically assigns them.

Review a small sample rather than redesigning everything

Choose recent fictional or appropriately protected examples from several outcomes: a new inquiry, a booking, a completed consultation, and a declined request. Ask whether the stage accurately describes what happened and whether the next action is clear.

Then inspect the automation behind each transition. A mismatch may come from an unclear stage definition, an incorrect staff action, or an unexpected workflow condition. Changing all the labels at once can conceal the original cause.

Use the intake metrics guide to keep denominators consistent. Captured leads, contacted people, booked consultations, and retained matters should not be mixed into one conversion percentage without explanation.

The result should be a pipeline that helps the team act. A modest board with truthful states and owned exceptions is more valuable than an elaborate funnel that reports progress nobody can verify.

Keep stage names understandable to the next employee

Write a short internal note for each important transition using a real operating example. A new employee should be able to distinguish an unanswered outreach attempt from a conversation, or a requested consultation from a confirmed one, without asking the owner to interpret the board.

Review those definitions when the firm changes reception coverage or adds a booking route. The meaning of an event can shift even when the label stays the same. Keep the workflow instructions aligned so a new automation does not silently change the firm's reporting denominator. This is basic operating documentation, not a promise that software will resolve ambiguous records without review.

Frequently asked questions

What should a Lawcus intake stage represent?

A defined business event and next action, supported by evidence. Avoid labels that mean different things to different staff members.

Is a captured lead the same as a contacted prospect?

No. A record may exist before any useful conversation occurs. Decide how the firm counts receptionist conversations, form submissions, and contact attempts.

Should a booking automatically mark someone as hired?

No. Booking and engagement are different events. Follow the firm's attorney-approved engagement process before recording a retained-client outcome.

Can Lawcus trigger workflows when a lead changes stage?

Yes. The official stage-trigger guide documents that capability. Verify the specific stage scope, entry rules, and actions before using it.

Does Clerx automatically move every Lawcus lead through the pipeline?

Do not assume that from the inbound integration overview. Confirm any proposed stage action and downstream automation separately.

Can converting a lead to a matter establish representation?

Software conversion is a product action, not a substitute for the firm's engagement decision or applicable legal obligations. Keep the distinction clear in staff instructions and client communications.

What should happen to stalled inquiries?

Assign an owner and identify whether the firm or the prospect owes the next action. Use an approved follow-up and closure policy rather than leaving the lead active indefinitely.

Which metric should the owner review first?

Start with whether stages accurately reflect contact, booking, attendance, and hiring. Consistent definitions make later conversion analysis more useful.

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.