Client Document Collection

Almost every matter in a small firm has a point where the work stops and waits on the client. The immigration file needs a passport scan and two years of tax returns. The personal injury file needs the signed medical authorization. The estate file needs the deed and the beneficiary designations. The work is not hard, nobody is arguing about it, and the file sits for five weeks because the client meant to send it and then forgot, and because nobody at the firm owned the follow-up.

What usually happens instead is that a paralegal keeps the list in her head or in a spreadsheet, and the chase happens when she has a slow afternoon or when the deadline gets close enough to be frightening. The intake email with the document list goes out once. If the client sends four of the seven items, somebody has to open the email, compare it against the list, and write back naming the three that are missing. That comparison is the step that silently does not happen. The client hears nothing, assumes everything landed, and the firm discovers the gap at the worst possible moment.

The money leak has three parts. Work in progress ages without becoming billable, so the firm carries the cost of the file without the revenue. Deadlines get met by emergency rather than by schedule, which means overtime, rush fees paid to vendors, and occasionally a missed filing window that becomes a much more expensive problem. And clients who hear nothing for a month decide the firm is not working on their case, which produces the status calls, the bad reviews, and the referrals that never come. This build makes the chase a system: a named checklist per matter, an upload link the client can use from a phone, and a follow-up cadence that runs whether or not anyone at the firm remembers it.

Pipeline and stages

One pipeline, Document Collection, with a stage for each state of the waiting. The matter sits in a stage, not in a paralegal's memory.

• Checklist Not Yet Built - matter opened, the responsible attorney has not confirmed which documents are required.
• Request Sent - checklist and upload link delivered, nothing received yet.
• Partially Received - at least one item in, at least one outstanding. This is the stage files die in without a system.
• Under Review - everything requested is in; a human is checking legibility, signatures and completeness.
• Rework Requested - something arrived but is unusable: page cut off, unsigned, wrong tax year.
• Complete - the file is unblocked and work resumes.
• Stalled - Attorney Review - the client has gone quiet past the escalation threshold and a lawyer decides what happens next.

Calendars

• Document Drop-Off - 20-minute office slots for clients who will not or cannot scan. Assign the front desk as a resource so two do not collide.
• Document Walkthrough Call - 15-minute phone slots where a paralegal walks a less technical client through the upload screen by screen.
• Notary and Signing Slot - 15 minutes with a buffer for ID checks, only if the firm has an in-house notary.

Custom fields

Create these on the contact record. Every automation branches on them, so the names matter.

• Matter Reference - the firm's own matter number. Never put the subject of the matter in a field that feeds message copy.
• Matter Type - picklist: Estate Planning, Immigration, Family, Personal Injury, Real Estate, Business, Probate. Drives which checklist template is used.
• Responsible Attorney and Assigned Paralegal - used for routing and internal alerts.
• Documents Requested Count and Documents Received Count - the two numbers every nudge compares.
• Outstanding Items List - a text field holding the plain-language names of what is still missing, rebuilt each time something arrives. This is what gets merged into the nudge message.
• Request Sent Date, Last Document Received Date, Nudge Count.
• Hard Deadline Date - filing or statutory date if one exists; switches the cadence from polite to urgent.
• Preferred Channel - SMS, Email, Phone, Mail. Honor it.
• Portal Link - the client's unique upload URL.
• Language - English, Spanish, other. Picks the message template set.
• Accessibility Note - free text, e.g. client has no smartphone, use paper.

Tags

• doc-request-active, doc-request-complete - the on/off switch for the whole cadence.
• doc-partial, doc-rework, doc-deadline-driven.
• doc-nudge-1 through doc-nudge-4 - stamped as each nudge fires, so nothing repeats.
• doc-escalated-attorney, doc-paper-route, sms-opt-out, client-prefers-phone.

Forms and upload pages

• Document Upload Page - a funnel page carrying the client's first name, matter reference and the outstanding items list. One file picker per item with the item name as its label, plus a catch-all for anything else. Mobile-first: most clients photograph documents with a phone.
• Checklist Confirmation Form - internal only. The attorney or paralegal ticks the required documents for that matter type, which writes Documents Requested Count and Outstanding Items List.
• Cannot Provide This Form - lets a client say an item does not exist or cannot be obtained, with a reason. Routes to the paralegal instead of looping the nudge forever.
• Review Outcome Form - internal. Per item: accepted, or rejected with a reason from a fixed list (illegible, unsigned, wrong period, incomplete pages, wrong document).

BO's role and guardrails

BO is the AI assistant that handles the administrative conversation around document collection. BO's job is logistics and nothing else.

• BO may: name which documents are outstanding, resend the upload link, explain how to photograph a document, offer a walkthrough call or a drop-off appointment, confirm receipt, and record that an item cannot be obtained.
• BO may not: answer any question about the merits, timing, strategy or likely outcome of the matter; interpret a document; advise whether a document should be signed; or say anything that could be read as legal advice or as forming an attorney-client relationship.
• Hard handoff rule: any question that is not about the mechanics of sending a file goes to the assigned paralegal, with BO replying only "That is one for your legal team - I have passed it to them and someone from the firm will follow up."
• Every BO-authored message carries the firm's standard administrative footer stating that the message is administrative, is not legal advice, and does not create an attorney-client relationship. Have the firm's compliance counsel approve the exact wording.
• Confidentiality shapes the copy. Nothing about the nature of the matter goes into an SMS body or an email subject line - no diagnosis, no charge, no counterparty, no immigration status, no case caption. Subjects read "Documents needed for your file with [Firm Name]" and nothing more.

Numbers and channels

• A dedicated firm number for client administrative messaging, separate from the main line, so document traffic does not bury new-matter calls.
• Two-way SMS with a human inbox a paralegal actually watches during business hours.
• Email from a monitored firm address, not a no-reply, with replies threading back into the conversation.
• Voice: outbound reminder calls for the paper-route and phone-preference clients, and inbound routing on the document number straight to the assigned paralegal.
• Printed letter fallback, generated from the same outstanding-items data, for clients tagged doc-paper-route.

One client, one matter, start to finish. Follow this once by hand before you automate any of it.

1. Matter opens. The engagement is signed and the contact record is created or updated with Matter Reference, Matter Type, Responsible Attorney, Assigned Paralegal, Preferred Channel and Language. A deal is created in Document Collection at Checklist Not Yet Built.
2. The attorney confirms the checklist. An internal task fires on matter open: open the Checklist Confirmation Form, tick the documents this specific matter needs from the Matter Type template, and add anything unusual. Submitting writes Documents Requested Count and Outstanding Items List and sets Documents Received Count to zero. A human owns this step on purpose - a template that silently requests the wrong documents costs more than it saves.
3. The request goes out. The deal moves to Request Sent. The client gets the first message on their preferred channel: an email with the itemized list and the upload link, plus a short SMS saying the email has landed. Request Sent Date is stamped and doc-request-active is applied.
4. The client opens the upload page. It greets them by first name, shows only the outstanding items, and takes phone photos as readily as scans. Each picker is labeled with the plain-language item name, not a code.
5. Partial upload. They send the two easy items and stop. On submission, Documents Received Count increments, Last Document Received Date is stamped, Outstanding Items List is rebuilt with only what is still missing, the deal moves to Partially Received and doc-partial is applied.
6. Immediate receipt confirmation. Within minutes the client gets a message naming exactly what arrived and exactly what is still needed, from the rebuilt list. This single message is the one most firms never send, and it is where most of the value sits.
7. The nudge cadence takes over. Nothing more is expected of the paralegal. Nudges fire at widening intervals, each one naming only the remaining items, each one carrying the link, each one stamping its own tag so nothing repeats. If a Hard Deadline Date exists, the cadence compresses as the date approaches.
8. A client who is stuck gets a human. Nudge two onwards offers the Document Walkthrough Call and the Document Drop-Off calendar. A booking pauses the nudges until the appointment outcome is recorded.
9. A client who cannot comply says so. The Cannot Provide This link in every message opens a short form. The item is marked unobtainable with a reason, removed from Outstanding Items List, and the assigned paralegal gets an internal notification to decide on a substitute - a decision no automation makes.
10. BO fields the replies. The client texts "which tax year do you need" and BO answers from the checklist. The client texts "will this affect my case" and BO does not answer it - the thread is assigned to the paralegal with the message flagged, and BO says only that the legal team will follow up.
11. Last item lands. Received count equals requested count. The deal moves to Under Review, every nudge stops, and the paralegal gets a review task with all files attached to the contact.
12. Human review. The paralegal completes the Review Outcome Form. If anything is rejected, the deal moves to Rework Requested, doc-rework is applied, Outstanding Items List is rewritten to the rejected items with the reason in plain language, and a short targeted rework cadence runs - not the full original sequence.
13. Complete. All items accepted. The deal moves to Complete, doc-request-active is removed and doc-request-complete applied, every pending step is canceled, and the client gets one closing message confirming the file is complete and that the firm is now moving the matter forward. No promise about timing or outcome appears in it.
14. Silence instead. If the escalation threshold passes with items still missing, the deal moves to Stalled - Attorney Review, doc-escalated-attorney is applied, automated client messaging stops entirely, and the responsible attorney gets a task with the full history. From there it is a lawyer's call: a phone call, a formal letter, or a conversation about whether the firm can continue to act.

Seven workflows. Every one of them checks doc-request-active as its first condition and exits if the tag is gone, so completion anywhere kills everything pending. Every outbound message respects quiet hours and skips SMS for anyone tagged sms-opt-out.

1. Checklist Build Request

Trigger: deal created in Document Collection at Checklist Not Yet Built.

• Action 1: create an internal task for the Assigned Paralegal, due in 1 business day: "Build document checklist for [Matter Reference] - open Checklist Confirmation Form."
• Wait 4 hours. If Documents Requested Count is still empty, notify the Responsible Attorney by internal message.
• Wait 1 business day. Still empty - notify the firm administrator. A matter with no checklist is invisible to the rest of the system, so this one escalates fast.

Exit: Documents Requested Count is greater than zero.

2. Initial Document Request

Trigger: Checklist Confirmation Form submitted.

• Action 1: write Documents Requested Count, Outstanding Items List, set Documents Received Count to 0, stamp Request Sent Date, apply doc-request-active, move the deal to Request Sent.
• Branch on Hard Deadline Date: if a date exists and is within 21 days, apply doc-deadline-driven and route to the compressed cadence in workflow 4b.
• Branch on Preferred Channel.
• Email path: subject "Documents needed for your file with [Firm Name]". Body: "Hi [First Name], we have opened your file and there are [Count] documents we need from you before we can move forward. Here is the list: [Outstanding Items List]. You can send them from your phone here: [Portal Link]. Photos taken with your phone camera are fine as long as all four corners of the page are visible. If any of these do not exist or you cannot get hold of them, tell us here: [Cannot Provide Link]. - [Firm Name] client services."
• Wait 15 minutes, then SMS: "Hi [First Name], [Firm Name] here. We have emailed you the list of documents we need for your file. Quickest way to send them is this link: [Portal Link]. Reply STOP to opt out of texts."
• SMS-preferred path: send the SMS first, email 15 minutes later.
• Mail path: if tagged doc-paper-route, skip both, generate the printed checklist letter with a reply-paid envelope and create a mailing task instead.

Exit: none - this always runs once and hands off to the nudge sequence.

3. Upload Received and Reconcile

Trigger: Document Upload Page submission.

• Action 1: attach the files to the contact, increment Documents Received Count by the number of items submitted, stamp Last Document Received Date, rebuild Outstanding Items List by removing what arrived.
• Branch A - received equals requested: move to Under Review, remove doc-partial, cancel all pending nudges, create a review task for the Assigned Paralegal due in 1 business day, and send: "Thanks [First Name] - that is everything we asked for. Someone from the firm will check it over and we will come back to you if anything needs a second look. Nothing further is needed from you right now."
• Branch B - received is less than requested: move to Partially Received, apply doc-partial, reset Nudge Count to 0, and send within 10 minutes: "Got them, thanks [First Name]. That leaves [Outstanding Items List]. Same link when you are ready: [Portal Link]." Restart the nudge sequence from nudge 1.
• Action 3 (both branches): internal notification to the Assigned Paralegal so a human knows files have landed.

Exit: runs on every submission; no exit condition.

4. Outstanding Items Nudge Sequence

Trigger: deal enters Request Sent or Partially Received. Condition on entry and before every send: doc-request-active present, Outstanding Items List not empty, not tagged doc-escalated-attorney, no open appointment booked.

• Wait 3 days. Nudge 1, SMS where permitted: "Hi [First Name], gentle reminder from [Firm Name] - we are still waiting on [Outstanding Items List] for your file. Link: [Portal Link]." Apply doc-nudge-1, set Nudge Count to 1.
• Wait 5 days. Nudge 2, email plus SMS, now offering help: "Still waiting on [Outstanding Items List]. If sending them online is awkward, book a 15-minute call and we will walk you through it, or drop the originals at the office: [Walkthrough Link] / [Drop-Off Link]." Apply doc-nudge-2.
• Wait 7 days. Nudge 3, email from the Assigned Paralegal's own address, signed by name: "Hi [First Name], [Paralegal Name] here from [Firm Name]. Your file is open but we cannot progress it until we have [Outstanding Items List]. Is there something getting in the way? Reply to this email or call [Firm Number] and we will sort it out." Apply doc-nudge-3.
• Wait 7 days. Nudge 4, final automated contact: "Hi [First Name], this is our last automated reminder about the documents for your file. [Outstanding Items List] is still outstanding. [Attorney Name] will be in touch directly. Link if you want to send them now: [Portal Link]." Apply doc-nudge-4, then hand to workflow 6.
• 4b - compressed cadence for doc-deadline-driven: same four messages at 2 days, 3 days, 3 days, 3 days, each adding one line: "There is a date on this file we need to work to, so the sooner we have these the better." Never state the deadline's legal consequence in the message - that is advice, and it belongs in a conversation with the attorney.

Exit at any point: doc-request-active removed, Outstanding Items List empty, an appointment booked, doc-escalated-attorney applied, or an inbound reply the paralegal takes over.

5. Rework Loop

Trigger: Review Outcome Form submitted with at least one rejection.

• Action 1: move to Rework Requested, apply doc-rework, rewrite Outstanding Items List to the rejected items each with its plain-language reason, decrement Documents Received Count accordingly.
• Action 2, immediately: "Hi [First Name], almost there. We need one more go at these: [Outstanding Items List with reasons]. For example, if a page was cut off, please retake it with all four corners showing. Same link: [Portal Link]."
• Wait 2 days - reminder SMS naming the items.
• Wait 4 days - email, plus offer of the walkthrough call.
• Wait 5 days - internal task for the Assigned Paralegal to call the client. The rework loop deliberately stops at three touches; a document that fails twice usually means the client has misunderstood something a person needs to explain.

Exit: replacement upload received and accepted, or doc-escalated-attorney applied.

6. Attorney Escalation and Stall

Trigger: doc-nudge-4 applied and no upload for 10 days, or 45 days since Request Sent Date with items outstanding.

• Action 1: move to Stalled - Attorney Review, apply doc-escalated-attorney, remove doc-request-active. This stops every automated client message on the matter. Nothing further goes out under the firm's name without a lawyer deciding to send it.
• Action 2: task for the Responsible Attorney: "[Matter Reference] stalled on documents. Requested [date], last upload [date], outstanding: [Outstanding Items List]. Decide: call, formal letter, or review the engagement."
• Action 3: add the matter to the weekly stalled-matters internal digest until the attorney clears the task.

Exit: attorney closes the task, which either re-applies doc-request-active and restarts the cadence or closes the deal.

7. Inbound Reply Triage

Trigger: inbound SMS or email on a contact tagged doc-request-active.

• Condition 1 - logistics question (which document, what format, where is the link, can I drop it off, how do I photograph it): BO answers from the checklist and the firm's standard instructions, and resends the link. Pending nudges continue.
• Condition 2 - anything about the matter itself (will this work, what happens next, how long, should I sign this, what does this mean): BO sends only "That is one for your legal team - I have passed it to them and someone from the firm will follow up," assigns the conversation to the Assigned Paralegal, flags it urgent, and pauses the nudge sequence for 2 business days so the firm is not texting reminders while a real question sits unanswered.
• Condition 3 - distress, a threat to the matter, or anything touching a deadline: notify the Responsible Attorney immediately and pause all automated messaging.
• Condition 4 - STOP or any opt-out language: apply sms-opt-out, stop all SMS at once, switch the contact to email and phone, and notify the paralegal that this client can no longer be reached by text.

Exit: conversation closed by a human, or doc-request-active removed.

The chase stops being a person's job. Nobody has to remember which of forty open matters is waiting on what, because the pipeline stage and the Outstanding Items List answer that question at a glance. The paralegal's role moves from chasing to handling the exceptions the system surfaces: the client who cannot get a document, the one who needs a walkthrough, the one who sent the wrong tax year.

Clients stop guessing. The single highest-value message in the whole build is the receipt confirmation that names what arrived and what is still missing, and it goes out within minutes of every upload. Clients who know exactly where they stand do not call for status, and do not assume the firm has forgotten them.

Matters age less. A file that would have sat for five weeks in silence now gets four structured contacts and an escalation to a lawyer inside six weeks, with a documented history of every attempt. That history is useful on its own terms if the firm ever has to explain what it did to move a matter forward.

Metrics to watch

• Median days from Request Sent to Complete, measured per Matter Type. This is the headline number and the one that should fall first.
• Days spent in Partially Received - the stage that used to be invisible. Watch it separately from Request Sent.
• First-response rate: share of clients who upload at least one item before nudge 1 fires. If it is poor, the problem is the initial request copy or the upload page, not the cadence.
• Nudge number at which the last item arrives. If most completions happen at nudge 3, the early intervals are too wide. If they happen at nudge 1, you can shorten the whole sequence.
• Rework rate by rejection reason. A spike in illegible means the upload page needs better photo instructions; a spike in unsigned means the request copy is not making the signature requirement obvious.
• Escalation rate - share of matters reaching Stalled - Attorney Review. This should be small and stable; a rise usually means the checklist is asking for things clients genuinely cannot produce.
• Walkthrough and drop-off bookings, and the completion rate of matters that used them. This tells you whether the human-help offer is worth keeping in the cadence.
• Inbound messages routed to a human by BO, split into logistics answered and legal escalated. The second number is the guardrail working; review a sample of them monthly to confirm BO is drawing the line in the right place.
• Aged work-in-progress on document-blocked matters, pulled from the firm's billing system. The operational metrics above are leading indicators of this one.

Platform and data

• Decide what the system of record is. If the firm runs practice management or case management software, that stays authoritative for the matter and the documents; the platform handles the chase and the conversation. Agree in advance which direction data flows and which fields are read-only on each side, or you will spend a year reconciling two versions of the same checklist.
• Agree where uploaded files finally live. Many firms route uploads into the practice management system or a document store such as Google Drive or SharePoint and keep only the receipt record in the platform. Settle this before you build the upload page.
• Build the checklist templates per Matter Type with the attorney who actually runs that work, in plain client-facing language. "Your two most recent tax returns" beats "Form 1040, TY-1 and TY-2."
• Decide the review step owner and make sure that person has capacity. A collection system that fills a review queue nobody works just relocates the bottleneck.

Integrations

• Two-way email on a monitored firm domain with SPF, DKIM and DMARC configured, so document requests do not land in spam.
• Calendar sync for the paralegals and the front desk, so walkthrough and drop-off slots reflect real availability.
• E-signature, if any of the requested items are documents the firm sends out to be signed rather than collected.
• File storage connection, if uploads are not staying in the platform.

Numbers and messaging compliance

• Provision a dedicated number for client administrative messaging and complete A2P 10DLC brand and campaign registration before sending anything at volume. Register the campaign honestly as account notifications and customer care for an existing client relationship; do not register it as marketing, and do not send marketing on this number.
• Carrier filtering is aggressive on legal-sector traffic. Keep message bodies plain, avoid link shorteners on shared domains, and use a link domain the firm controls.
• Implement opt-out handling properly: STOP, UNSUBSCRIBE, CANCEL, QUIT and the obvious variants all apply the sms-opt-out tag and stop SMS immediately and permanently until the client opts back in. Include opt-out language in the first message of any sequence. Make sure an opt-out does not stop the firm's necessary matter communications - it means the firm must reach that client another way, which is exactly what the Preferred Channel field and the paralegal notification exist for.
• Set quiet hours - typically 8am to 8pm in the client's own time zone - and hold queued messages rather than dropping them. Suppress automated sends on weekends and public holidays unless a hard deadline is in play.
• Collect and record consent to be contacted by text at engagement, in the engagement letter or an intake form, and store the timestamp and source on the contact record.

Confidentiality and professional obligations

This is the part that needs a lawyer's attention before launch, not after.

• Message content is the main risk surface. Nothing identifying the nature of the matter belongs in an SMS body or an email subject line. A text that names a charge, a condition, a counterparty, an immigration status or a case caption can be read by anyone holding the phone. Write every template as though a third party will see it, because one will.
• Confirm the channel is appropriate for the client. A shared household phone or email is a real confidentiality problem in family, immigration and some criminal matters. Record the client's instructions about how they may be contacted and let Preferred Channel and Accessibility Note carry that instruction into the automations.
• Privilege. Think about what gets stored where, who at the firm and at any vendor can see it, and what happens to the data on termination. Review the vendor data processing terms, data location, retention periods and subprocessor list with the firm's counsel.
• No legal advice, no attorney-client relationship. BO's messaging is administrative only. Lock the guardrails in the prompt, test them adversarially before launch with the questions clients actually ask, and review a sample of real conversations every month. Any message that could be read as advice on the matter is a problem regardless of the disclaimer attached to it.
• Unrepresented parties. Make sure the automations can never fire at someone who is not a client of the firm, and that nothing in the copy reads as soliciting a relationship.
• Advertising and solicitation rules. Most jurisdictions regulate what a firm may say in client communications and require certain disclosures or record retention. Automated messaging sent under the firm's name is within scope.
• Data protection. Depending on the clients and the matter types, state privacy law, GDPR, or sector rules may apply to what this system collects and stores.

None of the above is legal advice. Confirm the specifics - message content, consent, retention, disclosure wording, supervision of automated client communication, and whether any of it touches the firm's duties of confidentiality and competence - with the firm's own compliance counsel and against the applicable rules of professional conduct in every jurisdiction where the firm practises. Have the attorney who will be responsible for these communications read and sign off on every template before it goes live.

Scoping

Matter types, checklist complexity, the practice management integration and the number of languages all move the build. To scope it for a specific firm, book a call at bookings.appbo.io.