Legal Client SMS in Salesforce: Intake, Court Dates, and Document Requests
A legal-client text may look like a simple reminder, but the operational consequences are not simple. A phone number can belong to a prospective client, an existing client, a guardian, a family member, a company representative, or someone whose authority has changed. A court date may move after a reminder is queued. A document request can reveal confidential context on a lock screen or send a client to the wrong matter portal.
A dependable Salesforce workflow connects the correct person and matter, an authoritative legal event, current permission, minimal message content, a secure next step, the client’s reply, and an accountable staff owner. This guide explains how to design SMS for intake, appearances, and document collection without treating a successful send as proof that the legal communication was correct.
Important: Attorney-client duties, confidentiality, privilege, legal advertising, representation rules, court procedures, consumer-protection requirements, consent, messaging registration, quiet hours, accessibility, supervision, records, and retention vary by jurisdiction, organization, matter, and recipient and can change. Treat this article as implementation guidance, not legal, ethics, compliance, or carrier-policy advice. Have authorized legal, ethics, privacy, security, records, and messaging owners approve the current workflow before launch.
Model the Legal Communication Event Before the Message
Start with the event Salesforce must communicate, not the SMS template. An intake follow-up, consultation, court appearance, filing deadline, case milestone, document request, signature request, or staff callback should have its own governed record or event contract. Store the matter, responsible person, event type, source, effective time, time zone, version, verification state, owner, and expiration.
Keep the event separate from delivery attempts. One verified appearance event may produce a confirmation, reminder, reply, handoff, and cancellation, but an SMS retry must not create a second court date. If a continuance, venue change, substitution of counsel, representation change, or corrected filing updates the event, the new version should supersede the old one and cancel stale work.
Use explicit states such as identified, awaiting verification, eligible, queued, sent, delivered, replied, handed off, resolved, canceled, superseded, blocked, or reconciliation required. Preserve every transition and source timestamp so the matter team can reconstruct what Salesforce knew and which rule authorized each action.
Resolve the Recipient and Matter Together
A normalized mobile number is a routing clue, not proof of identity or authority. The same number may appear on multiple Leads, Contacts, Person Accounts, household members, employees, clients, witnesses, or opposing-party records. One person may also be connected to several matters with different counsel, permissions, and confidentiality requirements.
Resolve the recipient together with the matter, client or representative role, organization, engagement status, prior conversation, recent outbound message, preferred language, number ownership evidence, and current communication authorization. Store why the match was accepted. If more than one person or matter remains plausible, withhold case-specific content and send the ambiguity to a staff queue.
Representation can change during a matter. Recheck whether the person is a current client, prospective client, authorized representative, guardian, corporate contact, or other permitted recipient at the final send decision. Closed, declined, conflicted, transferred, withdrawn, or substituted relationships should not inherit yesterday’s automation eligibility.
Design Intake SMS Around Safe Next Steps
Intake SMS can acknowledge an inquiry, provide a scheduling path, request a low-risk next step, or route a reply to an intake owner. It should not imply that representation exists merely because a Lead was created or a questionnaire was started. Create separate states for inquiry received, conflict review pending, consultation offered, consultation booked, engagement decision pending, retained, declined, referred, and closed.
Keep early messages neutral. Avoid inserting sensitive allegations, adverse-party names, medical details, immigration status, criminal facts, financial information, or strategy into notification text. A short message can identify the organization using approved wording and direct the recipient to a secure destination where identity and context are verified.
Connect every intake reply to an owner and service target. A response such as “call me,” “wrong number,” “urgent,” or “I already have a lawyer” is not merely campaign engagement. Preserve the original text, stop incompatible automation, and route it according to the organization’s approved intake, conflicts, supervision, and emergency procedures.
Use an Authoritative Source for Court Dates and Deadlines
A Salesforce calendar event is convenient, but it may not be the authoritative source for an appearance, deposition, filing, or hearing. Define which docket, court notice, matter-management record, filing system, or approved staff verification controls each deadline type. Synchronize only the fields needed for communication and retain the source reference, verified-by role, verification time, effective time zone, and version.
Treat scheduled, confirmed, tentative, continued, canceled, completed, missed, corrected, and unknown as different states. A reminder should state only details that the organization has approved for SMS. Venue, remote-access instructions, arrival time, document checklist, or attorney name may require different verification and disclosure rules.
Recheck the event immediately before sending. If the source is stale, two systems disagree, the time zone is missing, a continuance is unprocessed, or an owner has not completed the required verification, block the reminder and create a deadline exception. A timely but wrong court-date text is not a successful outcome.
Cancel Stale Reminders When Legal Events Change
Court and matter events can change while messages are queued. Give each communication request the source event ID and version. When a newer event arrives, compare it with every pending request, cancel messages tied to the old version, and decide whether the new event needs a correction, a replacement reminder, or staff review.
Do not silently edit a previously sent message record. Preserve the original content and event evidence, then create a linked correction or cancellation action when the approved process requires one. Staff should see which recipients received the earlier version, which delivery states are known, whether they replied, and who owns the correction.
Expiration matters too. A court reminder, consultation prompt, or document deadline should have a latest-useful time. Delayed jobs and retries must re-evaluate the current matter state instead of delivering an obsolete instruction after the event has passed.
Apply SMS Eligibility at the Final Moment
A message approved when it entered a queue is not automatically eligible when it leaves. Immediately before submission, recheck the recipient and number, matter relationship, purpose-specific permission, suppression, sender registration and use-case mapping, template version, content variables, destination market, timing, frequency, event freshness, owner, and expiration.
Map consent evidence to the legal communication purpose rather than a universal “SMS allowed” checkbox. Intake, appointment reminders, matter updates, document requests, billing, and promotional outreach can have different requirements. Keep source, captured wording, date, number, purpose, business identity, status, and withdrawal history.
Process STOP and equivalent withdrawal signals through the organization’s approved suppression workflow, including queued and scheduled work. Pair this design with the Salesforce SMS opt-in and opt-out guide. A deadline or staff preference should not bypass a current suppression or uncertain number owner.
Request Documents Through a Controlled Destination
SMS can notify a client that action is required without carrying the confidential document itself. Generate an organization-approved link that is authenticated where needed, short-lived, purpose-bound, revocable, and connected to the exact matter and request. The destination should verify identity before showing a document list, accepting an upload, collecting a signature, or displaying case details.
Model the request separately from the file. Store the requested document type, matter, responsible client or representative, request version, due date, secure destination, allowed file rules, fulfillment state, reviewer, and expiration. A received file should not automatically become “accepted”; validation, malware scanning, record association, completeness review, and staff approval can be separate states.
Do not place passwords, long-lived tokens, sensitive descriptions, full identifiers, or confidential allegations in message text, visible URLs, analytics parameters, or provider metadata. Log link issuance and access events at the minimum approved level, and ensure expired or superseded requests cannot be reopened from an old text.
Bound Automated Replies and Hand Off Legal Questions
Define a small set of low-risk replies the automation may process, such as confirm an appointment, request a call, report a wrong number, ask to reschedule, acknowledge receipt, or opt out. Preserve the original message before classification and relate it to the conversation, recipient, matter, event, and latest outbound request.
Legal questions, new facts, changes in representation, threats, safety concerns, deadline disputes, confidential disclosures, document problems, accessibility needs, and ambiguous replies require human review. Create a task or exception with the full context, urgency, responsible team, due time, and last safe automated response. Do not let a generic assistant invent advice or promise a legal outcome.
Design after-hours and unavailable-owner rules. A message can acknowledge receipt using approved language while clearly stating the next expected action; it should not imply active monitoring or emergency response unless that service actually exists and is authorized.
Minimize Lock-Screen and Shared-Device Disclosure
SMS previews can appear on a locked or shared device. Use the least detail needed for the approved purpose. Even a matter name, adverse-party name, practice area, court, medical provider, charge, immigration status, debt amount, or settlement reference may reveal more than the recipient expects.
Create content tiers. A low-disclosure notification can ask the recipient to review a secure update; a verified portal can reveal the detailed task. Store the approved disclosure tier on the message template and prevent free-text variables from expanding it. Test every template with realistic long values and lock-screen previews.
Shared numbers need additional caution. If Salesforce cannot distinguish which household member, employee, or representative controls the phone, route the matter to staff rather than including details or requesting a reply that could be misattributed.
Give Exceptions Clear Owners and Deadlines
Route identity ambiguity to intake or matter administration, deadline conflicts to the assigned legal team, consent and suppression issues to the approved privacy or compliance process, sender failures to messaging operations, secure-link problems to the portal owner, and legal questions to supervised staff. Do not leave all failures in one unowned SMS queue.
An exception record should include the matter and event, recipient reference, message purpose, current and source states, raw evidence, deadline, attempted actions, consent result, delivery status, recommended next step, owner, service target, and resolution. Keep access aligned with matter permissions; technical support may need error codes without access to confidential legal facts.
Define a safe pause. If deadline data conflicts, number ownership changes, suppression propagation fails, a sender is inactive, the secure portal is unavailable, or the responsible team lacks coverage, the automation should stop affected work and surface the scope instead of continuing with partial evidence.
Report the Legal Outcome, Not Just the Send
Report the full path: events identified, blocked before send, queued, submitted, delivered, failed, unknown, canceled, superseded, replied, handed off, resolved, and reconciled. Connect messages to operational outcomes such as intake appointment booked, appearance confirmed, reschedule reviewed, requested file received, file accepted, staff callback completed, or wrong-number suppression applied.
Segment by matter type, office, event type, source, event version, recipient role, sender, template, disclosure tier, language, delivery state, reply category, owner, and exception reason. Keep network delivery separate from legal completion. A delivered document request is not a received or approved document.
Reconcile Salesforce requests with provider message identifiers, delivery callbacks, inbound replies, current event versions, tasks, and portal outcomes. Explain unknown deliveries, replies with no match, document uploads without a current request, stale messages, and open handoffs. Missing evidence belongs in the dashboard rather than outside the denominator.
Test Real Legal-Operations Failure Modes
Test duplicate names, duplicate and shared numbers, joint clients, guardians and representatives, company contacts, prospective versus retained clients, opposing parties, conflicts, changed counsel, closed matters, multiple active matters, language changes, current opt-outs, quiet hours, sender mismatch, and expired permission evidence.
For dates, test tentative, verified, continued, corrected, canceled, completed, missed, and conflicting events; time-zone and daylight-saving boundaries; delayed synchronization; duplicate updates; old queued work; and a correction after the first message was delivered. For documents, test missing request types, wrong matters, expired links, duplicate uploads, unsupported files, review rejection, revoked access, and portal outages.
For replies, test confirmations, reschedule requests, wrong numbers, opt-outs, new legal facts, confidential disclosures, ambiguous answers, out-of-order replies, duplicate callbacks, long messages, attachments or links, unavailable owners, and after-hours escalation. Launch one controlled event type, observe staff workload and reconciliation, then expand only after the evidence and handoffs are reliable.
Legal Client SMS Checklist for Salesforce
- Define governed communication events for intake, appointments, court dates, milestones, and document requests.
- Resolve the recipient, authority, number, matter, and current representation status together.
- Choose an authoritative source for every date and store its version, verification state, time zone, and owner.
- Cancel queued work when a continuance, correction, representation change, or newer matter event supersedes it.
- Recheck consent, suppression, sender, purpose, content, timing, event freshness, and ownership immediately before sending.
- Use minimal lock-screen-safe content and controlled templates with approved disclosure tiers.
- Send document requests through authenticated, expiring, purpose-bound destinations rather than exposing confidential details.
- Automate only approved low-risk replies and hand legal, deadline, identity, and confidentiality questions to people.
- Route each exception to an accountable owner with evidence, urgency, and a service target.
- Reconcile messages, callbacks, replies, event versions, staff tasks, and document outcomes in Salesforce.
Frequently Asked Questions
Can Salesforce send legal-client SMS reminders automatically?
Yes. Trigger them from a verified intake, appointment, deadline, document, or matter event after checking recipient identity, authority, consent, sender, source freshness, content, timing, and owner.
Which record should control a court-date SMS?
Use a governed deadline or appearance record synchronized from the approved authoritative source, with a source reference, version, verification state, effective time zone, update time, and owner.
Should legal documents be sent as SMS attachments?
Usually use a minimal SMS linking to an approved secure portal that verifies identity before showing details or accepting an upload, signature, or acknowledgment.
How should Salesforce handle replies to legal texts?
Preserve the original reply, match it to the correct matter and outbound context, automate only bounded low-risk intents, and hand legal or ambiguous content to accountable staff.
How can teams stop stale court-date reminders?
Version every event, recheck the source immediately before sending, cancel queued work when a newer event arrives, expire old requests, and reconcile messages against the current matter timeline.
What should teams test before launch?
Test identity ambiguity, representation changes, consent, changed dates, time zones, secure links, conflicting matters, every reply path, delivery failures, owner coverage, stale work, and reconciliation.
Make Every Legal-Client Text Explainable
Legal-client SMS becomes dependable when every message can explain which recipient, matter, authority, permission, event version, sender, template, disclosure rule, delivery outcome, reply, and owner shaped its lifecycle. That evidence helps teams stop the wrong reminder, correct an ambiguous match, prove which deadline version was used, and hand sensitive work to the right person.
WatBox can help teams connect SMS activity with Salesforce so messages, replies, delivery events, automation, ownership, and reporting stay related to the right record. Start with one approved legal event type and one accountable team, then scale only after identity, deadline authority, secure document handling, exception routing, and reconciliation are proven.
