A reliable follow-up process begins with a reason for the next contact. Define what the inquiry needs, who owns the action and when the record should stop moving through that path. Then use reminders and automation to support those decisions.
Write A State-Based Playbook
List the situations the team actually encounters: no meaningful contact yet, interrupted conversation, missing document, professional review pending, questions about an agreement or a decision not to proceed. For each, define the next useful action and the evidence that completes it.
A document request should identify the document and an approved way to provide it. A review-pending inquiry should identify the reviewer and how staff will communicate an update. Someone who asked to speak later should have a task reflecting that request rather than the default sequence.
Record Contact Preferences And Stop Conditions
Keep the person’s requested channel and timing visible to the staff member taking action. Define how opt-outs, wrong numbers, changed circumstances and requests for no further contact suppress scheduled activity. Review whether preferences reach all relevant tools, including any outside answering or messaging service.
ABA Model Rule 7.3 addresses solicitation and includes limits involving unwanted contact and coercion or harassment. Applicable professional, calling, messaging and privacy requirements need their own review. There is no universal follow-up cadence in this article; the firm must approve a plan suited to the channel, context and jurisdiction.
Assign One Owner And A Backup
Give the current owner responsibility for coordinating the next step even when another person must supply an answer. Define how a backup takes over during leave or an absence. A shared inbox can hold messages, but it still needs rules that establish who acts.
Illustrative workflow: intake requests a document and records the person’s preferred response method. Receipt changes the record to “ready for review” and assigns the designated reviewer. If the upload cannot be opened, staff receive an exception task. The system does not continue asking for a document simply because the original reminder date arrived.
Test The Exceptions Before Activating Automation
Use synthetic records to test an opt-out, a late document, a duplicate submission, an unavailable owner and a person who has already completed engagement. Confirm that reminders stop or change as intended. Check the destination records as well as the visible messages.
Keep automated statements within the firm’s approved scope. A workflow should not interpret a notice, decide case merit or promise representation based on an incomplete administrative event. Staff need an obvious route for anything the playbook does not cover.
Review Open Work Instead Of Counting Touches
The daily view should prioritize overdue actions and the oldest unresolved states. The periodic review should examine appropriate closure, completed handoffs and recurring information gaps. Contact-attempt volume can help explain effort, but it should not become the goal.
Refine the playbook when actual conversations reveal confusion. Keep changes versioned and train the team on the reason for them. The process is working when staff and the person seeking help both understand the next step, including when there is no further action to take.
Sources And Further Reading
- ABA Model Rule 7.3: Solicitation Of Clients · Checked 2026-10-21
These sources provide context. Requirements depend on the actual activity and applicable jurisdiction. Business-process guidance does not replace professional advice.