Subpoenaing Phone Records: What Carriers Keep and What They Don't

If you are planning to subpoena phone records, settle one question before you draft anything: what can the carrier actually give you? In most civil and family matters, a carrier subpoena produces metadata, meaning the subscriber on the account and logs of calls and texts with dates, times, numbers and durations. It rarely produces the words of a text message, and the reasons are both technical and legal.

That distinction drives the strategy. Carrier records are strong evidence that contact happened, how often, and when. They are weak evidence of what was said. This guide covers what carriers keep, why content is usually out of reach, a Rule 45 workflow, and how to use what comes back. Rules are described under the Federal Rules of Civil Procedure and Evidence; your state’s versions and local practice may differ, so verify them before you serve.

What phone records can you get from a carrier?

A properly issued civil subpoena will generally reach non-content records: who held the account, and the transactional log of calls and messages. What a carrier keeps, and for how long, varies by carrier, record type and time period, so treat this table as a map of categories, not a promise.

Also confirm who the carrier actually is. Many prepaid brands run on another company’s network, and numbers move between carriers through porting, so the company holding records for your period may not be the one serving the number today. Billing statements, an interrogatory or deposition testimony can pin this down.

Why can’t you subpoena the content of text messages?

Three obstacles stand in the way: retention, federal law and technology. Carriers’ retention of message content is generally very limited and varies between carriers, and often there is nothing retrievable to produce. Even where something exists, the federal Stored Communications Act generally prohibits providers that serve the public from disclosing the contents of communications in response to a civil subpoena, while permitting disclosure of non-content records to non-government parties.

The third obstacle is technical. iMessage, WhatsApp, Signal and similar apps send messages over the data connection. To the carrier that traffic is data, not texting, so those conversations generally won’t appear in its text logs at all. If the dispute lives in iMessage or WhatsApp, a carrier subpoena may show nothing for the exchanges you care about, and the app providers are generally subject to the same content restriction.

So message content comes from the people who sent and received it: devices, cloud backups and app exports, obtained through Rule 34 requests, agreed collections or forensic imaging. The account holder’s lawful consent is a recognized exception to the content bar, which is why content disputes tend to run through the party, not the provider.

Should you get the records from the parties first?

Usually, yes. A subscriber can typically download their own call and text history, or billing statements with usage detail, from their carrier account. Those records are within the party’s possession, custody or control and can be requested under Rule 34 without involving a non-party.

• It is faster: no compliance-unit queue, no out-of-state process, no processing fees.
• It strengthens your proportionality position under Rule 26(b)(1) when you later ask a non-party only for what the parties could not or did not produce.
• Your own client’s records cost nothing and let you test the theory first.
• If the opposing party’s production looks edited or incomplete, the carrier’s version becomes a clean comparison point.

The carrier subpoena then corroborates, fills gaps, and arrives with a custodian certification that may simplify foundation. For party-side requests, see drafting requests for production of text messages.

How do you subpoena phone records from a carrier?

Under the federal rules, a records subpoena to a carrier is a Rule 45 subpoena commanding a non-party to produce documents and electronically stored information. The steps below follow that rule; state practice tracks it loosely, but deadlines, notice requirements and service methods vary.

1. Confirm the carrier and the number. Identify the carrier of record for the whole date range, including port dates and multi-line accounts.
2. Find the carrier’s legal-process instructions. Major carriers typically maintain a subpoena-compliance unit with its own service address, accepted methods and fees. Follow them exactly; a misdirected subpoena can sit unanswered.
3. Narrow the request. Specify the number, a tight date range and the record types. Rule 45(d)(1) requires the issuing party to take reasonable steps to avoid imposing undue burden or expense on the recipient, and courts may consider it when objections arrive.
4. Ask for a usable format and a key. Request spreadsheet or native format where available, plus the legend explaining column codes and the time zone used. Under Rule 45(e)(1)(B), if you don’t specify a form, the recipient may produce in the form it ordinarily maintains or a reasonably usable form.
5. Request a records certification. Ask for a custodian declaration suitable for records of regularly conducted activity under FRE 803(6) and 902(11), or your state’s equivalent.
6. Serve notice on the parties first. Rule 45(a)(4) requires a notice and copy of a documents subpoena to be served on each party before it is served on the non-party.
7. Handle place of compliance. Federal subpoenas generally set production within 100 miles under Rule 45(c)(2)(A). In state court, an out-of-state carrier may require you to domesticate the subpoena through the compliance state’s interstate discovery procedure; many states have adopted a uniform act for this.
8. Calendar objections and follow up. Under Rule 45(d)(2)(B), written objections are due before the earlier of the compliance date or 14 days after service. Check in with the compliance unit well before your hearing date, not after it.

Saying expressly that you are not seeking content removes an obvious reason for a compliance unit to push back on a civil subpoena.

What happens if the subscriber objects or moves to quash?

Expect resistance, especially when the records belong to a non-party. The subscriber can object or move to quash or modify under Rule 45(d)(3), usually citing relevance, overbreadth or privacy.

Your best response is the request you drafted before the objection arrived. Tie the date range to specific allegations, explain why the parties’ own records are missing or disputed, and offer limits up front: a protective order restricting use to the case, or redaction of uninvolved third parties’ numbers. Whether to enforce, narrow or quash is the court’s call; a narrow, well-explained request gives it less to trim.

How do you turn carrier records into usable evidence?

Carrier productions are dense spreadsheets full of codes. Their value comes from lining them up against device messages.

Normalize time before comparing anything

Carrier records may be kept in UTC or a single network time zone rather than the subscriber’s local time; the legend should say which. Phone exports usually display local time. Convert one to match the other, and account for daylight saving changes inside your range, before concluding that a message is missing or a call never happened.

Normalize numbers

Standardize formatting so (555) 010-1234 and +15550101234 match, and map numbers to people in a separate key rather than overwriting the source column.

Cross-reference against the message log

Line up carrier SMS rows with the device-extracted conversation. Matches corroborate the export. Carrier rows with no matching message flag a possible deletion worth asking about. Messages with no carrier row are often app-based messages that never touched the SMS system. A tool like Message Extractor can merge device exports into one chronological, Bates-numbered log, which makes the row-by-row comparison practical.

Preserve the production as received

Keep the carrier’s original files untouched and hashed, and annotate only copies. If the comparison suggests deletion, it may feed a preservation dispute; see spoliation of text messages for how Rule 37(e) frames lost electronic information.

Common mistakes with phone-record subpoenas

• Subpoenaing the current carrier when a different carrier held the number during the relevant period.
• Asking for “all records” with no date limit, which invites a motion to quash.
• Requesting message content, which can lead the carrier to reject or delay the whole subpoena.
• Serving close to the hearing, when retention windows may have closed and the compliance unit has little time to respond.
• Omitting the custodian certification and scrambling for foundation later; see how certifications for electronic records work.

Whether a carrier subpoena is worth issuing in a given matter, and how to frame it, is a judgment for the licensed attorney handling the case under the forum’s rules. For an example of how extracted conversations become one paginated log, see how a Bates-numbered message log is built.