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

11/20/2026

From Lawcus Intake to Engagement Agreement: A Staff-Approved eSign Handoff

Automate the administrative send after the authorized person approves the document and recipient.

Client OnboardingLaw Firm OperationsLawcusDocument WorkflowsLegal Intake
A folder of checked documents points through a checkmark to a signed page and a pen.

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

A Lawcus intake-to-engagement workflow should distinguish collecting an inquiry, approving the next step, sending the correct agreement, and confirming what was actually signed. An AI receptionist can help capture a prospective client's request, while the firm's authorized team controls engagement decisions and document instructions.

Lawcus offers native eSign actions and user-activated workflows. These can support a deliberate staff-approved handoff after intake, rather than sending an agreement automatically whenever a new lead appears. The right design depends on the firm's process, documents, and professional obligations.

This guide addresses the administrative sequence, not the legal terms an engagement agreement should contain or the point at which an attorney-client relationship arises. Have the responsible attorney approve those decisions under the rules applicable to the firm.

Why document delivery needs its own checkpoint

A useful intake conversation does not establish that the firm should accept the matter, that the correct agreement has been selected, or that the person contacting the office is the intended signer. Those are separate questions.

For example, an estate-planning inquiry may arrive from an adult child arranging a meeting for a parent. An immigration prospect may call on behalf of a relative. The caller's email address is not automatically the correct recipient for an engagement document.

The Lawcus intake overview explains how first response supports later work. This narrower guide focuses on the approval point between an intake record and a document sent for signature.

Treat the checkpoint as a defined responsibility. Someone should confirm the approved document and recipients before the system performs the administrative send.

What the native Lawcus tools document

Lawcus's user-activated workflow guide describes workflows that a permitted user applies manually to a lead or matter. Its purpose is on-demand action rather than an automatic trigger on every new inquiry.

The Send eSign Document action guide describes choosing a saved template, the relevant lead or matter, and configured signers. Verify the firm's current plan, permissions, templates, and any service limits before implementation.

These are native Lawcus capabilities. They do not prove that Clerx selects the agreement, approves representation, maps every signer, or executes the workflow without staff involvement. Keep the reception connection and the document process distinct.

The distinction is commercially useful: a firm can automate routine delivery while preserving an intentional approval decision. It does not need to treat every new lead as ready for an engagement agreement.

Keep the receptionist's job narrow and useful

The receptionist should capture the request, relevant contact details, caller role, and approved next step. It should not promise that a contract will be sent unless the firm's instructions support that statement for the situation.

The Clerx inbound AI receptionist can follow configured intake and routing rules. Lawcus's official Clerx guide documents the inbound lead, contact, and call-summary connection.

Use the Clerx-Lawcus integration page to understand the relationship, then demonstrate the actual information available for staff review. Do not assume every piece of conversation data is automatically mapped to every document field.

A short summary can help the team decide what to review next. It does not replace the lawyer's engagement decision or a check of the appropriate recipient.

Define the evidence needed before a send

The firm should specify what the authorized person confirms. That may include the intended service, the correct prospective client, the chosen document version, recipient details, and any firm-required preliminary review.

Use factual, operational language. "Attorney approved this document for this prospect" is more useful than "lead qualified" if the latter label does not explain what was reviewed. Avoid using an AI-generated score as a substitute for an approval decision.

The conflict-check workflow guide reinforces the broader distinction between collecting information and making a legal determination. Apply the firm's own review requirements before sending engagement material.

Do not turn this list into a universal legal checklist. The appropriate conditions vary by practice, service, jurisdiction, and firm policy. The point is to make the authorized decision visible before automating its administrative consequence.

Use an on-demand workflow when approval is case-specific

A user-activated workflow can be a sensible starting point when someone must decide whether an agreement is appropriate. After review, the permitted user applies the chosen workflow to the correct record.

This approach can reduce repetitive sending steps without hiding the decision inside a broad automatic rule. A solo lawyer might approve the document and have an assistant perform the administrative action. Another firm may restrict execution to the reviewing attorney. Choose the actual permission design in the account rather than assuming any role has access.

The native guide describes permission-based execution. It does not determine the firm's legal approval policy. The team must still understand who may approve, who may send, and what happens when the record is incomplete.

Write those roles plainly so a new employee can follow the process without guessing whether a pipeline label constitutes approval.

Check the template and signer mapping

A saved template reduces repeated work only if it is the right version for the intended purpose. Keep template names understandable and maintain an approved version process. A similar-looking title is not a sufficient safeguard against sending the wrong document.

Before enabling a reusable workflow, test the selected record, template, recipient, and any additional signer. Verify what the recipient sees in the subject line and message as well as the document itself.

The intake form design guide offers a useful general principle: collect information for a defined purpose. Do not request sensitive background at first contact solely because a later template has fields that might use it.

If a required value is unknown, route the record for review instead of filling it with a plausible guess. A confidently personalized document can still be wrong.

Distinguish sent, opened, signed, and reviewed

A document send is not a signature. A signature event is not necessarily proof that every part of the firm's engagement process has been completed. The firm's actual sequence should determine the next action.

Lawcus's eSign Document Signed trigger guide describes workflows initiated by a completed signing event and the use of entry rules for specific documents or attributes.

If a firm uses that trigger, filter it deliberately. Signing an intake disclosure should not automatically activate a workflow intended for a particular engagement agreement unless the firm has explicitly designed it that way.

Test the event with a fictional document. Confirm which record changes, who is notified, and whether the intended follow-up task appears. Do not treat every signature across the account as the same business event.

Keep payment and booking separate from engagement status

A consultation booking, a payment event, and an engagement document are related operational facts, but they should not be collapsed into one status. The firm must define what each event means in its process.

Clerx scheduling and payments describes a consultation journey. It should not be interpreted as proof that a consultation payment accepts representation or that every Lawcus document workflow runs from that event.

If the firm wants payment to be part of its native document sequence, verify the exact trigger and conditions independently. Do not invent an order of signing, payment, or representation from a generic software feature list.

The prospect should receive an accurate explanation of the current step. An appointment confirmation should not imply that the legal engagement is complete when the responsible attorney has not approved that conclusion.

Give incomplete signing a human owner

Some recipients will not finish the request. Others may ask a question, identify an error, or request a different delivery arrangement. Define who handles those situations and how automated reminders stop or change when human review is needed.

The lead-follow-up guide discusses follow-up discipline more broadly. For an agreement, avoid treating silence as a reason for unlimited repeated messages or treating a question as an objection to be overcome automatically.

If the firm uses text messaging, confirm the approved role of that channel. An assistant may record a request for help, but a message exchange should not be presented as the legal team's answer to a substantive agreement question.

Keep the document owner and communication owner aligned so the recipient does not receive conflicting instructions from different staff members or systems.

A fictional small-firm workflow

An immigration firm receives a call from a prospective client. The configured receptionist captures the broad request and contact route, and the information reaches Lawcus. Staff arrange the approved next step under the firm's intake rules.

After the firm's required review, the attorney authorizes a particular agreement. A permitted user checks the record and recipient, then applies a user-activated workflow that sends the approved template. When the intended signing event occurs, a narrowly configured native workflow creates the next administrative task.

If the recipient asks a legal question about the agreement, staff pause the ordinary chase and route it to the attorney. The receptionist does not interpret the document or promise its legal effect.

This is an illustrative design, not a customer story or a claim that all steps are preconfigured in Clerx. The useful result is an explicit approval boundary with repeatable administration after it.

Review the sequence before enabling it for real prospects

Use fictional names, test email addresses, and sample documents. Walk through a normal send, a wrong-recipient correction, an unsigned request, and a signed document that should not activate the engagement workflow.

The pre-launch testing guide provides a broader method for checking the intake side. Extend the test to the native Lawcus actions and the staff handoff rather than stopping when a call record appears.

Track corrections, wrong-template incidents, unanswered recipient questions, and documents waiting without an owner. These are proposed quality measures, not published Clerx performance results. The goal is reliable progression through the firm's approved process, with attorneys retaining the decisions that belong to them.

Frequently asked questions

Can Lawcus send eSign documents through workflows?

Yes. Its official documentation describes a Send eSign Document action using saved templates, configured records, and signers. Confirm current account access and limits.

What is a user-activated workflow?

It is a native workflow a permitted user manually applies to a selected lead or matter. It does not run automatically simply because a new inquiry appears.

Does Clerx choose the engagement agreement?

The cited inbound integration material does not establish that role. Keep document selection and engagement approval with the firm's authorized team unless a separately verified process is agreed.

Is the caller always the correct signer?

No. Someone may contact the firm for a relative or another person. Verify the intended client, recipient, and signer under the firm's process before sending documents.

Can a signature trigger the next Lawcus workflow?

Lawcus documents a signed-document trigger with entry rules. Configure it for the intended document and conditions rather than treating every signature as the same event.

Does a consultation payment mean representation is accepted?

Do not make that assumption. Booking, payment, and engagement status are distinct facts. The responsible attorney determines the firm's legal and business process.

What if a recipient asks about the agreement's meaning?

Route substantive questions to the authorized legal team. The receptionist can capture the request and follow approved contact instructions without interpreting legal terms.

What should be tested before launch?

The correct record, template, recipient, signer, approval step, signed-event filter, and exception route. Use fictional data and confirm the staff-visible result.

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.