AI Esquire
Menu
Plans from $497/monthBuy Intake AI
Follow-up governance

Your law firm’s follow-up sequence needs a stop rule.

A prospective client calls, starts an intake, and disappears before scheduling. Automation makes it easy to send another text, then another, then an email, then a call. The firm may call that persistence. The recipient may experience it as pressure. A serious intake system needs rules for when follow-up begins, what it may say, how often it may continue, and exactly what stops it.

A lead is not a communications license

Law firms are right to follow up. People call during work, family emergencies, medical treatment, or moments of uncertainty. They get interrupted. They miss return calls. A careful reminder can help a person complete a request they already made.

The mistake is treating one contact event as blanket permission. A person who asks for a consultation has not necessarily agreed to an indefinite sequence of promotional texts, prerecorded calls, newsletters, and reminders from multiple systems. Even when a particular message is legally permissible, more contact is not automatically better client experience.

The operating question is not simply whether the firm has a phone number. It is why the firm is contacting that number, through what technology, based on what evidence, and under which stopping rule.

Separate service follow-up from marketing

A message confirming a consultation, requesting a missing document, or answering the person’s question serves a different purpose from a message promoting the firm’s services. The distinction can affect legal analysis, caller expectations, approval language, and the appropriate cadence.

Do not bury every message under one label called follow-up. Define categories such as requested callback, appointment administration, incomplete-intake reminder, attorney-review update, declined-matter notice, and marketing. Give each category its own permitted channels, content boundaries, frequency, owner, and expiration.

The Federal Trade Commission makes a similar purpose distinction in its CAN-SPAM guidance. Transactional or relationship email is treated differently from commercial email, and mixed messages can be evaluated according to their primary purpose and presentation. A law firm should not turn a case-status message into an advertisement merely because its software makes that easy.

Consent needs an evidence trail

Federal Communications Commission rules impose consent requirements on specified calls and texts made with an automatic telephone dialing system or an artificial or prerecorded voice, subject to the governing definitions and exemptions. Telemarketing generally receives stricter treatment. State law and other rules may add obligations. The details depend on the message, technology, recipient, purpose, and jurisdiction.

That complexity is a reason to collect better facts, not a reason to guess. For each automated channel, preserve what the person was told, the action that expressed consent, the number or address covered, the purpose and message category, the date and time, the source page or script version, and any later change or revocation.

A checkbox without the associated language is weak evidence. So is a vendor field that says opted in without showing how. The firm should be able to reconstruct the permission it relied on without asking a software company to interpret an old database flag.

  • Exact disclosure or request shown to the person
  • Affirmative action or communication relied upon
  • Covered channel, number, and message purpose
  • Timestamp, source, and workflow version
  • Revocation, limitation, or preferred-channel change

STOP cannot fall into the wrong inbox

Current FCC rules provide that covered consent can be revoked through any reasonable method that clearly expresses a desire to stop further calls or texts. Familiar reply words such as stop, quit, end, revoke, opt out, cancel, and unsubscribe are expressly recognized. A business cannot insist that the person use one exclusive revocation method, and covered requests must be honored within a reasonable time not exceeding ten business days.

A compliant deadline should not become an operating target. If an intake prospect says stop, the automation should stop promptly. The request should create a suppression event tied to the person and channel, cancel scheduled messages, prevent a different vendor from restarting the sequence, and notify the responsible team when human judgment is needed.

Free-form language matters. People write do not text me, I hired someone else, wrong number, please leave me alone, or contact me only by email. A system that recognizes only the exact keyword STOP is not reading intent. Route uncertain language to review while suppressing avoidable messages in the meantime.

An opt-out confirmation is not proof that the next scheduled message was actually cancelled.

The 2026 FCC nuance should not become an excuse

On January 6, 2026, the FCC extended until January 31, 2027 a limited waiver involving one part of its consent-revocation framework: whether a revocation made in response to one type of informational message must apply to all future robocalls and robotexts from the same caller on unrelated matters. The order states that the extension is limited to that cross-category requirement.

It does not erase the broader obligation to honor applicable revocation requests. The current regulation still describes reasonable revocation methods, prohibits designating an exclusive method, and addresses the time for honoring covered requests. Firms should resist oversimplified claims that everything was delayed or nothing changed.

This is general educational information, not legal advice. A firm should evaluate its actual tools, messages, jurisdictions, consent language, exemptions, and professional obligations with qualified counsel. The operational recommendation is more conservative: when a person clearly asks a law firm to stop an automated channel, do not use regulatory ambiguity as a reason to keep pursuing them.

Build follow-up as a state machine

A reliable sequence should have explicit states, not a calendar of messages that fires until someone remembers to intervene. A prospect might be awaiting a callback, scheduled, completing intake, pending attorney review, declined, retained, unresponsive, represented elsewhere, wrong number, or opted out. Each state should permit only defined actions.

Events should move the person between states. Booking a consultation cancels booking reminders. A decline ends retention-oriented outreach. Notice of existing counsel triggers review. A request for email only suppresses text and call automation. A global do-not-contact instruction overrides lower-level campaigns. Expiration ends a sequence even when nothing else happens.

This design prevents the most common failure: multiple tools acting on different versions of the same person. The intake platform sends a reminder, the CRM sends a campaign, the calendar sends a confirmation, and a staff member calls from a separate list. Every component appears to work while the firm behaves incoherently.

Cadence should reflect the person’s request

There is no universally correct number of follow-ups. Urgent safety information, a requested same-day callback, a consultation reminder, and a general marketing message do not belong on the same schedule. Set cadence by purpose, sensitivity, channel, and the likely cost of delay.

Use the least intrusive channel that can accomplish the requested task. State the firm’s identity and the reason for contact. Keep sensitive facts out of messages that may appear on a shared screen or voicemail. Provide an easy way to change channel or stop. End the sequence after a defined period rather than converting silence into permission for more attempts.

Measure completed next steps, not message volume. A sequence that sends twelve reminders and produces one appointment may look active while damaging trust, increasing complaints, and consuming staff time. More attempts can conceal a weak intake offer, confusing scheduling, or slow attorney review.

Audit the vendors as one system

Ask every vendor what triggers a message, what technology sends it, where consent evidence is stored, how revocation is detected, how quickly queued messages are cancelled, and how suppression travels to other tools. Test the answers. Marketing slides are not an integration test.

Create scenarios using common language, misspellings, replies to old threads, requests received by phone, and preferences entered by staff. Confirm that each request reaches the system of record and blocks the relevant future activity. Then test restoration so an employee cannot casually reactivate contact without new authority and a documented reason.

The firm needs one accountable owner for the full communications map. Assigning each vendor to a different department does not divide the recipient’s experience. The person sees one law firm.

Good follow-up knows when to end

Responsiveness remains a competitive advantage. A prompt, useful message can rescue an interrupted intake, prevent a missed consultation, or tell a worried person what happens next. The discipline is making each contact serve the person’s request.

Record the permission. Limit the purpose. Respect channel choice. Suppress quickly. Reconcile vendors. Escalate ambiguity to a human. Let silence expire instead of treating it as an invitation to pursue forever.

The best follow-up system is not the one that sends the most messages. It is the one that continues only while the contact remains useful, expected, and justified.

Sources and further reading

Primary and industry sources used to support this page. External guidance should be reviewed in context and for your jurisdiction.

  1. 47 C.F.R. § 64.1200Current federal rules addressing covered calls and texts, consent, reasonable revocation methods, confirmation messages, and honoring opt-out requests.
  2. FCC Order DA 26-12, January 6, 2026The FCC’s limited extension, until January 31, 2027, of the cross-category consent-revocation requirement for unrelated informational messages.
  3. FCC, Stop Unwanted Robocalls and TextsCurrent consumer guidance on consent and the ability to opt out of robocalls and robotexts.
  4. FTC, CAN-SPAM Act Compliance GuideBusiness guidance distinguishing commercial email from transactional or relationship messages and explaining opt-out responsibilities.
Put the framework to work

See Intake AI handle your firm's real workflow.

Bring the intake questions, routing rules, or coverage gap you want to improve. We will demonstrate the system against them.

Call Intake AI now (941) 941-6967Book a 30-minute working session