Give the role a reliable starting point.
Provide contact permissions, approved cadence, message templates, and stop-contact rules.
Maintain respectful, approved follow-up while an inquiry awaits information or attorney review.
Book a free consultationScope, access, and coverage are agreed with your team.

Define the recurring work and the evidence your team needs to review it. These building blocks become a role-specific operating plan.
A working record with source references, current status, and the person responsible for the next step.
A focused view of missing inputs, unanswered questions, and items that need your decision.
A dated handoff that distinguishes completed work from pending review and unresolved exceptions.
Provide contact permissions, approved cadence, message templates, and stop-contact rules.
A prospect replies with a question about likely damages. The assistant acknowledges the message using approved language and routes it to the attorney.
Illustrative workflow, not a client case study.Check consent preferences, contact accuracy, and the current inquiry status before sending.
Tool familiarity is considered when defining the role. Your team approves every platform, access level, and source of truth.
Platform names describe possible working environments, not endorsements or a promise of certification.
Maintain respectful, approved follow-up while an inquiry awaits information or attorney review. The scope below connects each recurring responsibility to its source information and a checkable working record. Your team confirms the exact steps, templates, and approval limits before work starts.
Begin with the latest request and its approved source record. Check that the necessary information is present, identify the owner, and clarify conflicting details before making an update.
Working output: Follow-up queue. Include the source reference, current status, and next owner when an item remains open.
Use the agreed template or checklist to carry out this task. Record what was checked and the date of the action so another team member can understand the current position.
Working output: Response history. Include the source reference, current status, and next owner when an item remains open.
Keep this work connected to the wider queue. Note dependencies and unanswered questions, and use the agreed escalation route when the next step requires a decision.
Working output: Attorney question list. Include the source reference, current status, and next owner when an item remains open.
Complete the task only when its agreed checks have passed. If an input is missing or an approval is pending, keep that status visible rather than treating the item as finished.
Working output: Follow-up queue. Include the source reference, current status, and next owner when an item remains open.
A prospect replies with a question about likely damages. The assistant acknowledges the message using approved language and routes it to the attorney.
The agreed task is complete and the supporting information is available in your approved system. Attach or link the relevant record and identify any final reviewer before closing the item.
Review against: Check consent preferences, contact accuracy, and the current inquiry status before sending.
Name the missing information, where it was requested, and who is expected to supply it. Keep a follow-up date visible. An unanswered request should not disappear into a completed-work total.
Starting requirements: Provide contact permissions, approved cadence, message templates, and stop-contact rules.
Summarize the exception and the information already checked. Ask a specific question and route it to the authorized person. Keep the original source intact while the decision is pending.
Approval boundary: No outcome prediction, legal strategy, or pressure to retain the firm.
Provide individual, approved access to the systems used for this responsibility. Share a completed example, an incomplete example, the relevant template, and a named reviewer. Sensitive working records belong in those systems, not in a public inquiry form.
Possible working environments include Lawmatics, Clio Grow, Outlook, Your CRM. Tool access and familiarity are confirmed as part of the role brief.
Agree which measures are useful for this queue: completed items, items awaiting an input, age of unresolved work, and corrections requested by the reviewer. Review these together with actual examples; volume alone does not establish that work is accurate.
Set response expectations from your operating needs. Coverage, turnaround targets, and the amount of work assigned are agreed separately rather than assumed from the service name.
Provide contact permissions, approved cadence, message templates, and stop-contact rules.
Check consent preferences, contact accuracy, and the current inquiry status before sending.
No outcome prediction, legal strategy, or pressure to retain the firm.
We scope the role around your approved systems, including environments such as Lawmatics, Clio Grow, Outlook. Access, training, and the final tool requirements are confirmed before the role begins.

Capture approved first-contact information and route it to the correct person in your firm.
Explore the service ↗
Arrange consultations using approved availability, prerequisites, and client communication.
Explore the service ↗
Coordinate attorney-approved document requests through the firm’s secure channels.
Explore the service ↗
Prepare names and administrative identifiers for your firm’s attorney-controlled conflict process.
Explore the service ↗Tell us where the queue slows down. We’ll discuss the scope, tools, coverage, and review points that belong in your support role.
Define the role before making a commitment.