Do text messages hold up in court? Business texts as records and notice

Yes, text messages are routinely admitted as evidence in US courts, as long as someone can show who sent them and that they haven't been altered. Whether a text also counts as written notice or forms a binding agreement depends on the contract, the statute and the state, so "do text messages hold up in court" really means "can you prove what was sent, by whom, when, and that text was an allowed way to send it."

This post is general information, not legal advice. If you're facing a dispute, or drafting a contract that relies on text notice, talk to a lawyer licensed in your state. Our goal is narrower: to explain how courts generally treat texts, and what a business should keep so its message history is useful evidence and not a pile of screenshots on someone's personal phone.

Do text messages hold up in court as evidence?

Courts treat text messages like any other document. The same few hurdles apply to a text that apply to an email or a letter.

Authentication: proving who sent it

Under the federal rules of evidence, and most state equivalents, the side offering a text has to show it is what they claim it is. With texts that usually means connecting the message to a person. The usual ways to do that:

• The phone number is tied to the sender (their known number, a business line on their website)
• The content refers to things only that person would know
• Testimony from someone who sent or received it
• Surrounding messages in the same thread that fit the context
• A records custodian explaining how the system stores messages

The weak spot is always "who was holding the phone." A text from a number proves the number sent it. It doesn't, on its own, prove a specific human typed it. That's why context and consistent records matter so much.

Hearsay and the business records route

A text offered to prove its contents can raise hearsay objections. Two common paths around that: statements by the opposing party (a customer's own "OK, cancel my plan" reply), and the business records exception. That exception generally covers records made in the regular course of business, at or near the time of the event, kept as a regular practice. A messaging platform that logs every inbound and outbound text automatically fits that description far better than an employee who screenshotted a conversation weeks later.

Screenshots vs exports

Screenshots get admitted all the time, but they are easy to challenge: they can be cropped, edited or stripped of context. An export from the system that sent the message, with timestamps and the numbers on both ends, is harder to argue with. If a dispute is reasonably likely, preserve the original records. Don't delete threads, and don't rely on the carrier having them: carriers generally keep message content briefly, if at all.

Is a text message considered written notice?

This is the question that trips up landlords, contractors, service businesses and anyone with a cancellation policy. The short version: a text can be written notice, but only if text is an accepted method for that particular notice.

Work through it in this order:

1. What does the contract say? Many leases and service agreements spell out notice methods: certified mail, email to a listed address, hand delivery. If the contract says "written notice by certified mail," a text probably doesn't satisfy it, however clearly worded. If the contract says "notice may be given by text to the number on file," you're in much better shape.
2. Does a statute set the method? Eviction notices, debt collection, some insurance and employment notices have methods fixed by law. A text often doesn't count for these, and some states are strict about it.
3. Did the other side agree to electronic communication? The federal E-SIGN Act and the state UETA laws generally say a record can't be denied legal effect just because it's electronic, but they rely on the parties having agreed to deal electronically, and they carve out certain notices.
4. Can you prove delivery and receipt? A reply ("got it, thanks") is strong evidence the person received it. Silence is weaker.

Our practical read: use text for reminders and confirmations, and for formal notices only where your agreement explicitly allows text notice. Even then, many businesses send the formal notice by the contract method and use a text to point to it. Our post on appointment cancellation texts covers wording for the everyday version of this.

Are texts legally binding?

Texts can form or modify agreements. Courts have found that a back-and-forth by text showed offer, acceptance and agreement on terms, the same as an email exchange would. Some courts have even treated a text with a typed name as satisfying a "signed writing" requirement. Others have refused to. The outcome turns on the facts and the state.

What tends to make a text exchange look binding:

• Clear, specific terms (price, date, scope), not "sounds good, let's talk"
• An unambiguous acceptance from the other party's own number
• Both sides acting on it afterward (the job got done, the payment went through)

What tends to undercut it:

• Missing terms that would normally be negotiated
• Messages scattered across personal phones, with gaps
• A thread that can't be produced in full, only selected screenshots

If a deal matters, send a proper agreement and use text to confirm it was received. Don't let a text thread be the contract by accident.

Why business conversation history matters

Most disputes involving business texts aren't dramatic lawsuits. They're a customer saying "you never told me the price changed," a contractor arguing over a scope change, or a TCPA claim alleging texts were sent without consent or after an opt-out. In each case, the side with the complete, timestamped record has the easier argument.

Four things make that record useful:

• Completeness: the whole thread, inbound and outbound, not just the parts someone thought to save
• Timestamps: when each message went out and when each reply came in
• Attribution: which business number sent it and which contact number replied
• Business custody: the history lives in a system the business controls, not on an employee's phone that leaves when they do

Worked example: what a shared inbox record shows

Here's an illustrative example with assumed facts, not a real case.

A landscaping company's service agreement says price changes may be given "by text or email to the contact on file, 30 days in advance." On March 1, the company texts a customer from its business number through the Ready inbox: "Starting April 1, weekly mowing goes from $45 to $50 per visit. Reply with questions or STOP to opt out of texts." The customer replies the same afternoon: "ok." In May, the customer disputes the higher charge.

What the conversation history in Ready gives the company:

Because the thread sits in the business's inbox and not on the owner's phone, the full history is still there if the employee who sent it has left. In the Ready inbox, open a conversation's menu and choose Export conversation to download the whole thread as a CSV with timestamps and both numbers, or select several conversations and choose Export. Developers can pull message history programmatically with GET /v1/messages; see the messages API docs.

The honest limits: this record supports the company's position, but it doesn't win the argument by itself. The agreement allowing text notice is what makes the text count. The message history proves the text was sent and answered.

Consent records: what Ready keeps and what you have to keep

Consent is where business texting meets litigation most often. TCPA claims carry statutory damages of roughly $500 to $1,500 per text, so a disputed campaign can get expensive fast. In those cases, your consent and opt-out records are the evidence.

Here's what Ready records, stated precisely:

• Send attestation: for each bulk send and each API send that sets consent_attested, the sender's opt-in attestation is logged: who sent it, to how many recipients, and when. On the API, that's the consent_attested field on each request.
• Opt-outs: inbound STOP and UNSUBSCRIBE replies are honored automatically and propagate across campaigns, so the contact can't be messaged again. Texts to opted-out numbers are refused up front.
• Quiet hours: sends outside permitted local hours for the recipient's area are held and sent later. Campaigns, drip campaigns and automations wait up to 24 hours for the window; a one-to-one or API text is held only if the window opens within 6 hours, otherwise it is refused and must be resent; a one-to-one reply to someone who texted you in the last 24 hours goes out at any hour.
• Litigator and DNC scrubbing: known TCPA-litigator and DNC numbers can be screened out before send.

And here's what Ready does not store: a per-contact consent record. We don't keep the recipient's opt-in time, the wording they agreed to, or the page URL where they signed up, and a keyword reply doesn't create one. For everyone else, that record has to come from wherever consent was collected: your signup form, checkout page, CRM or store. Keep the exact checkbox wording, the timestamp and the source for every contact. If a consent dispute comes up, that's the document that matters most. (A contact who signs up on a Ready-hosted opt-in page is the exception: Ready stores that sign-up, with the time, IP address and exact wording, and support@tryready.com can send you a copy.)

None of this makes anyone lawsuit-proof. Compliance is the sender's responsibility. These tools reduce risk and leave a cleaner trail. If you run texting for other businesses, our piece on who gets sued when a client's list goes bad covers how that responsibility splits, and what a 10DLC compliance platform should do for you covers the rest of the stack.

The practical takeaway

Texts hold up as evidence when you can authenticate them and produce the whole record. They count as notice when your agreement or the governing law allows text notice. They bind when the terms are clear and both sides acted on them. On the business side, what you control is the record: send from a business number, keep history in a system the business owns, collect and store per-contact consent at the source, and let opt-outs and quiet hours be enforced automatically.

If you want to see how the inbox history and opt-out handling work, you can sign up and send a few one-to-one texts. Ready's Standard rate is $0.0075/segment plus a $0.0045 carrier fee, and the standalone TCPA and DNC litigator scrub is $0.005 per contact. Full pricing is at tryready.com/pricing.

FAQ

Do text messages hold up in court?

Generally yes. Courts admit texts when the party offering them can authenticate who sent them and show they weren't altered. Complete exports with timestamps and phone numbers are stronger than cropped screenshots.

Is a text message considered written notice?

Sometimes. It depends on what your contract says about notice methods and whether a statute requires a specific method, such as certified mail for certain eviction or collection notices. Where the agreement explicitly allows text notice, a text with proof of delivery or a reply is much stronger.

Are texts legally binding?

A text exchange can form or modify an agreement if the terms are clear and both parties accepted them. Some courts have treated a typed name in a text as a signature; others haven't. For anything important, use a written agreement and confirm by text.

Can I just use screenshots from my phone?

Screenshots are often admitted but are easy to challenge as incomplete or edited. Records exported from the business's messaging system, with timestamps and numbers on both ends, are more reliable, and they stay with the business when an employee leaves.

Does Ready store proof that each contact consented?

No. Ready logs the sender's attestation for each bulk send and each API send that sets consent_attested (who sent, to how many, when) and enforces opt-outs and quiet hours. The per-contact consent record, meaning opt-in time, wording and signup page, has to be kept wherever you collected consent.