Law enforcement and subpoena requests

How do we log a law enforcement or subpoena request, check its validity, route it to the compliance team, and answer it on the deadline with an audit record?

Treat every legal demand as a case with a validity check before any data moves. When a subpoena, a court order, a warrant, an emergency request or a preservation letter arrives, Callvu logs it with the requesting agency and the officer, classifies it by legal process and by the data sought (subscriber information, transactional records, stored content, location data, real-time intercept), checks the validity against the standard the law sets for that data (the issuing authority, the signature, the scope, the time period, the jurisdiction, the emergency certification), chases a defective or overbroad request back to the agency with the specifics, routes the decision to the compliance team in the Decision Desk with only the allowed outcomes, produces exactly the data ordered from the systems with the certification, delivers through the secure channel by the return date, and writes the audit record the law and the policy require, including the customer notice where permitted.

In scopeComplex: multi-party handoffsCallvu moves: classify, chase and verify, decide, write back

Talk to an expert Try it in the sandbox

Last updated November 7, 2026.

The problem today

The fax asked for a year of location data on a subpoena that could only reach the subscriber's name, and the clerk sent it all.

Today, without Callvu

Carriers receive hundreds of thousands of legal demands a year: subpoenas for subscriber details, court orders for call records, warrants for content and location, emergency requests at two in the morning, preservation letters. Each has a legal standard the agency must meet for the data it seeks. A demand processed by a clerk under deadline pressure, from a fax queue, is where the over-production and the missed return dates happen, and both are reported.

The Stored Communications Act sets the process required for each category: a subpoena for basic subscriber information, a court order on specific and articulable facts for transactional records, a warrant for content and, after the Supreme Court's decision on cell-site location, for historical location; emergency disclosure has its own certification. CALEA governs the intercept capability and its lawful authorization. The validity check is a classification against these standards, the production is a scoped pull, and the record is the carrier's defense.

A demand answered exactly as the law allows, on the date, with the record, is the only kind to answer.

How it runs

From the requestto the system of record.

A legal demand arrives from a law enforcement agency, a court, a government body or a civil litigant, by the legal portal, fax, mail or an emergency line. Callvu logs it and opens the case.

Requesting agency or litigant: Submits the demand and receives the response, the certification or the deficiency notice.
Compliance team (the legal demands unit): Decides validity questions, emergency requests and objections in the Decision Desk.
Legal counsel: Decides objections, motions to quash and novel requests.
Callvu: Logs, classifies, checks validity, chases defects, routes, produces, delivers and records.

Classify the demand
The demand is logged with the agency, the officer or attorney, the case reference, the receipt date and the return date, and classified by the legal process (a grand jury or administrative subpoena, a civil subpoena, a court order under the Stored Communications Act, a search warrant, a pen register or trap and trace order, a wiretap order, an emergency request, a preservation request, a foreign request through the treaty process) and by the data sought (basic subscriber information, transactional and call detail records, stored content, historical or real-time location, an intercept).
Chase and verify validity
The demand is checked against the standard for the data sought: the issuing authority and the signature, the jurisdiction, the scope and the time period, the identifiers (the number, the account, the device identifier), the specific and articulable facts for an order, the probable cause finding for a warrant, the emergency certification's elements for an emergency request, the preservation period's rules; a defective or overbroad demand is returned to the agency with the specifics (the process required, the scope to narrow) through the portal, and the case waits.
Decide
A valid demand within the standard proceeds to production by rule where the policy allows; an emergency request (which requires the compliance team's judgment on the certification), a demand for content or location, an objection or a motion to quash, a request outside the jurisdiction, a civil subpoena for a customer's records (which triggers the customer notice where the law permits), a gag order question or a novel request goes to the compliance team or counsel in the Decision Desk with the classification and the validity check and only the allowed outcomes (produce, produce in part with the reason, return as deficient, object, or escalate to counsel).
Produce, deliver and write back
The data is pulled from the systems (the BSS, the system of record for the subscriber and the account, the call detail and the location systems, the content stores) exactly to the scope and the period ordered, formatted with the certification of records, delivered through the secure legal channel by the return date with the delivery logged, the customer notified where the law permits and no gag order applies, the reimbursement invoiced where the law allows, and the audit record (the demand, the classification, the validity check, the decision, the data produced, the dates and the people) retained for the period the law and the policy require and reported in the transparency statistics.

Where it ends: Every demand was classified and checked against the legal standard for the data it sought, defects went back to the agency, the compliance team decided the hard ones, exactly the data ordered was produced by the return date, and the audit record shows all of it. The Decision Trace shows the classification, the validity check and the decision; the Audit Trace shows the receipt, the deficiency notices, the production and the delivery with time.

Runtime enforcement

What is enforcedwhile the work runs.

The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.

Regulations

Stored Communications Act (18 USC 2701 to 2713, including 2702 and 2703): A provider may disclose basic subscriber information (name, address, service dates, payment source, telephone and device identifiers) on a subpoena; transactional records and other non-content records on a court order under 2703(d) based on specific and articulable facts; the contents of stored communications on a warrant (and, under the Supreme Court's decision in Carpenter, historical cell-site location on a warrant); may voluntarily disclose in an emergency involving danger of death or serious physical injury under 2702(b)(8) and (c)(4); must preserve records for 90 days on a government request, renewable once (2703(f)); and is entitled to reimbursement for the costs of producing records (2706).
CALEA (47 USC 1001 to 1010) and the Wiretap Act and pen register statutes (18 USC 2510 to 2523, 3121 to 3127): A carrier must have the capability to isolate and deliver intercepted communications and call-identifying information to law enforcement under a lawful authorization, with the intercept activated only on a court order (a wiretap order under Title III or a pen register or trap and trace order) and the carrier's personnel and procedures protecting the authorization and the intercept from unauthorized use; the system security and integrity rules under 47 CFR 1.20000 require a record of each intercept activation.
FCC CPNI rules (47 CFR 64.2005) and the carrier's legal demand policy: Customer proprietary network information may be disclosed as required by law, which the validity check establishes; the policy sets the acceptance channels, the deficiency handling, the emergency request procedure, the customer notice practice, the retention of the audit record and the transparency reporting.

Company policies

No data moves before the demand is classified and checked against the legal standard for that data type.
A defective or overbroad demand goes back to the agency with the specifics; the carrier does not fill the gap.
Emergency, content, location, objection and novel requests are decided by the compliance team or counsel, never by rule.
Production is exactly to the scope ordered, from the systems of record, with the audit record retained and the statistics reported.

Controls

Demand logging and classification by process and data type.
Validity check against the statutory standard.
Deficiency returns to the agency.
Decision Desk for emergency, sensitive and contested demands.
Scoped production with certification and secure delivery by the return date.
Audit record retention, customer notice where permitted and transparency reporting.

Clocks and deadlines

Return date: The demand's date, on the case, with escalation before it.
Preservation: Ninety days from a preservation request, renewable once for a further ninety.
Emergency request: Handled on receipt by the compliance team on the emergency line, with the certification recorded.

Documents and checks

The demand as received and its classification
The validity check and any deficiency notice
The decision and the person
The data produced with the certification and the delivery log
The audit record and the customer notice where sent

In the Decision Trace

The classification by process and data type.
The validity check against the standard.
The decision and the person.

In the Audit Trace

The receipt with time and channel.
Each deficiency notice and response.
The production, the delivery and the notice with time.

The handoff

Between the front doorand the back office.

The front door

The legal portal, fax, mail or the emergency line; agencies receive deficiency notices and responses through the portal.

The back office

The compliance team decides emergency, sensitive and contested demands; routine valid demands are produced by rule from the systems of record.

The Decision Desk

An emergency request, a demand for content or location, an objection, a jurisdiction question, a civil subpoena for a customer's records, a gag order question or a novel request goes to the compliance team or counsel in the Decision Desk with the validity check and only produce, produce in part, return as deficient, object, or escalate to counsel.

Proof

In scope.Proof at scale, not one process at a time.

The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.

More than 1,000 processes are live across Callvu customers.

Across Callvu customers

AT&T runs close to 100 processes on Callvu, used by 55,000 agents.

TEL-02

Questions

What buyers ask next,answered plainly.

What legal process is needed for which data?

Under the Stored Communications Act, a subpoena for basic subscriber information, a court order on specific and articulable facts for transactional records, and a warrant for content and historical location; emergency disclosure needs the certification; an intercept needs a wiretap or pen register order under CALEA's framework.

What happens with a defective request?

It goes back to the agency with the specifics (the process required or the scope to narrow), and the case waits; the carrier does not produce beyond what the process allows.

Is the customer told?

Where the law permits and no gag order or delayed notice applies, under the carrier's notice policy, with the notice recorded on the case.

Related processes

Customer data access and deletion request Regulator complaint response Account takeover report CPNI consent and opt-out Try it in the sandbox All telecom processes

Bring this process, or the one that costs you most.

We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.