Lawyers are bad at returning calls and good at billing. Clients know both. When a firm's software can send a short text, "Your hearing is tomorrow at 9:30 at the county courthouse," a lot of friction disappears. That's why practice management vendors keep hearing the request.

It's also a product area where a careless text does real damage. A message that reveals a client's matter to the wrong person is worse than a missed reminder. This guide is for the product team at a legal practice management or case management product. We'll cover what to text, what to keep out, consent, STOP, quiet hours, and how to separate each firm. Every scenario is a made-up example, and none of this is legal advice for your product.

What to text, and what never to

The safest rule: a text tells the client that something needs their attention and where to find it. The substance stays behind a login or in a call.

Good candidates:

  • Appointment and consultation reminders
  • Court date and deposition reminders, with date, time and general location
  • "Please sign the document we sent" nudges, with a link to a logged-in page
  • Invoice available notices, without amounts
  • Intake follow-ups after a new inquiry
  • Office closed or rescheduled notices

Keep out of texts:

  • The nature of the matter ("your divorce filing", "your DUI case")
  • Settlement amounts, strategy, opposing party names
  • Anything about a client's health, medications or treatment. Ready isn't HIPAA compliant and doesn't sign BAAs, so keep health information out of every text.
  • Any attorney's legal advice

Phones sit on lock screens, get shared with family members and are sometimes owned by someone else. "Example Law, reminder: please call us at 555-0100 about your Thursday appointment" reveals little. Build template defaults that encourage that style, and let firms customize inside limits you set.

Consent when the client is also a prospect

Firms text two groups: existing clients and people who inquired. The second group is where consent mistakes happen.

For a prospect, the agreement should be captured at the moment of inquiry, on a web form or intake page: an unchecked box, the firm's name, the types of texts (replies to their inquiry and appointment scheduling), that message and data rates may apply, and that replying STOP ends texts. For an existing client, an engagement letter can include a texting clause, but your software should still record it as a consent record, not bury it in a PDF.

Your database should hold the agreement: who, when, wording, source page and purpose. When you send through Ready, set consent_attested to true only if your record supports it. Ready logs that attestation (who sent, to how many, when), but it isn't a per-contact consent record and doesn't store the recipient's wording or opt-in time. Our post on a consent record schema for developers lays out the fields, and documenting SMS consent covers how long to keep them.

From January 20, 2027 (UTC), an API send without consent_attested is refused with 403 api_consent_attested_required. Until then it goes out with a warning and no attestation.

Keep marketing apart from service texts. A client who agreed to appointment reminders hasn't agreed to a newsletter about a firm's new practice area. Cold lists don't belong here at all: we don't coach texting people who never asked, and Ready's acceptable use policy bars it.

The send call

One request sends one text. This is the shape the API uses, with a made-up number:

POST /v1/messages
X-API-Key: <key>
Idempotency-Key: <one UUID per message>

{"to": "+12125550199", "body": "Example Law: your appointment is tomorrow at 2:00 PM. Call 555-0100 to change it. Reply STOP to opt out.", "consent_attested": true}

Three habits worth baking in:

  1. One UUID per message, reused on every retry. A retry after a timeout shouldn't text a client twice. See idempotency for duplicate texts.
  2. Count segments. 160 characters in a plain segment, 153 per part when longer, 70 with an emoji. Ready adds "Reply STOP to opt out" and the business name to the first text to each contact unless the account turns it off, so leave room. See the segment counter post.
  3. Validate the number. GET /v1/validate/:phone checks a number before you save it, which catches typos at intake. Docs: https://docs.tryready.com/api/validate-numbers.

Endpoint docs: https://docs.tryready.com/api/messages.

STOP, and the case where the client is still a client

A client who replies STOP has told the firm to stop texting. That doesn't end the representation, so the product should keep the case moving through another channel.

  • Honor it automatically. Ready blocks further texts to a number that replied STOP, UNSUBSCRIBE or a clear phrase such as "please stop texting me."
  • Read the status back with GET /v1/opt-outs and the per-number GET /v1/opt-outs/:phone.
  • Show the staff member a clear "texts off for this contact" marker on the matter, with a reminder to call or email for deadlines.
  • Don't let a paralegal re-enable texting by editing a field. Only a new, recorded agreement should turn it back on.

A STOP always blocks that number in the sub-account that received it. Whether it also blocks the parent and other sub-accounts is decided by Ready, so check the per-number endpoint for the rest. More in handling SMS opt-outs.

Quiet hours and urgent deadlines

Law has real deadlines, and they don't respect sunset. Even so, texting rules limit when a business can contact people, and Ready enforces quiet hours based on the recipient's area. A campaign or automation waits up to 24 hours for the window. An API text is held only if the window opens within 6 hours, and otherwise isn't sent, so your code sends it again once the window opens.

For a truly urgent matter, a phone call is the right tool; a text at midnight is a poor substitute and a risk. Build the retry path, and surface "not sent, outside allowed hours" to the attorney so they know to call. A reply to someone who texted the firm in the last 24 hours can go out at any hour, which covers the client who texts in at night. We explain the response in handling the quiet hours 409.

One sender per firm

A text from one firm must never appear to come from another, and one firm's complaint mustn't affect another's numbers. Ready's sub-accounts give each firm its own numbers and its own carrier registration (10DLC), created through the API. Registration needs an EIN, so a solo practitioner without one can't register; ask at onboarding. Most approvals take 2 to 7 days. Our multi-tenant SMS architecture post covers the tenancy design in more depth.

Inside a firm, think about permissions. Which staff can send? Can a paralegal text a client directly, or only through templates? Log every send with the staff member's ID in your own system so a firm can answer "who sent that?"

FAQ

Can we send documents by text? Send a link to a logged-in page, not the document.

Should texts count as billable time? That's a firm's decision. Give them the log.

What about group threads? Keep client texts one to one. A group thread can expose a client's number and matter to other people.

The practical takeaway

Start narrow: appointment and court date reminders, a neutral template, recorded consent and a sender per firm. Add features after a pilot firm has lived with it for a month. To try the API with a test key, sign up and send a first text.