
One afternoon, one client alert
The above client alert tracks a key issue in one of this year’s active litigation trends: whether a marketing text message counts as a “call” under federal telemarketing law. It draws on 25 federal decisions issued in 2026, and every case it cites links to the passage in the opinion that supports it.
It’s built entirely with Midpage inside of Claude.
Building it took a single afternoon and the alert keeps itself up to date. What follows is a walkthrough of how it was built, why its conclusions can be trusted, and how it stays current as new decisions come down.
Why client alerts matter, and why they are so hard to keep current
A client alert is a short memo that a law firm sends to its clients, and often publishes on its website, when something important changes in the law. The trigger might be a new statute, a significant appellate decision, an agency rule, or a shift in how courts are handling a recurring type of claim. A good alert explains what happened, who is affected, and what clients should do about it, usually in a few pages that a general counsel can read between meetings.
Alerts serve two main purposes: (1) They keep clients informed about risks they may not be tracking themselves, and (2) they position the firm as a go-to authority on the issue. Most firms treat client alerts as both a client service and a business development tool. These alerts often have the added upside of providing valuable internal education by keeping attorneys current on the state of the law.
High quality client alerts track trends across jurisdictions, explaining how courts in different parts of the country are resolving the same question and where a client’s exposure is highest. When I was a litigation associate at a big law firm, I was regularly asked to build these multi-jurisdictional surveys. Clients valued them, and they kept the firm top of mind, but they were time and labor-intensive to produce. A single alert could take days of research, and more than once, the law had shifted by the time the draft was ready to send.
That tension sits at the heart of the knowledge management function. Clients expect their firm to be ahead of the curve, yet the traditional way of producing an alert almost guarantees that it will trail the law or, at best, present a single snapshot that ages immediately. The workflow below, built on Midpage’s case law and docket data, is designed to close that gap by collecting and analyzing decisions, presenting them in a form clients can use, and keeping the result current without starting over.
The example: is a text message a “call”?
To demonstrate the workflow, I chose a live litigation wave involving marketing text messages under the Telephone Consumer Protection Act (TCPA). The approach described here works for any issue a firm wants to follow.
The TCPA allows consumers to sue companies that send marketing messages to numbers listed on the National Do Not Call Registry, with statutory damages of $500 to $1,500 per message. Because those damages accrue message by message, a single text campaign sent to a large customer list can quickly become a class action.
For years, courts largely treated text messages as “calls” under the statute, following the FCC’s interpretation. That consensus began to unravel in June 2025, when the Supreme Court held in McLaughlin Chiropractic Associates v. McKesson Corp. that district courts hearing TCPA cases are not bound by the FCC’s interpretation of the statute and must instead read it for themselves, giving the agency’s view only appropriate respect. Then, on July 14, 2026, the Seventh Circuit held in Steidinger v. Blackstone Medical Services that text messages are not “telephone calls” under the do-not-call provision, and district courts in other circuits have since divided on the question.
The result is precisely the kind of uncertainty that prompts clients to call their lawyers. Every company that markets by text, whether a retailer, a healthcare provider, or a real estate brokerage, now wants to know whether it is exposed, and the firms that answer first are the ones clients remember.
Step 1: Gather the case law
The research began with a single question, written the way a lawyer would ask a colleague. For this demo I used Claude connected to Midpage, though the same workflow runs in any AI assistant that can connect to Midpage’s data:

There was no need for search syntax, Boolean operators, or terms and connectors. Claude recognized that the question called for case law and routed it to Midpage on its own.
What came back was a table organized by circuit, listing each defendant, its industry, the court, the date of decision, and how the court answered the texts-as-calls question. The defendants spanned virtually every major sector. Because the results were grouped by circuit, the shape of the split was visible at once: some circuits were treating texts as potentially actionable calls, while others were not.

In effect, this table is the raw material for a multi-jurisdictional survey.
Step 2: Verify any row in seconds
A table of results is only useful if the people relying on it can trust it, so the next step is verification. Clicking Steidinger in the table does more than open the opinion. Midpage takes the reader directly to the passage that answers the question, in this case the Seventh Circuit’s holding that texts are not “telephone calls” under § 227(c)(5).
Every case in the table works the same way, and that changes the nature of review. Rather than re-researching a summary, a reviewer can check each conclusion against its source in a matter of seconds. That is the difference between a draft that has to be redone and one that is ready for sign-off and shipment.
Step 3: Turn the same data into a map
A table of case law serves an associate drafting a brief well, but partners and clients may want to see the bigger picture. I asked the assistant to take the same Midpage data and build an interactive map. Its first view colors the country by federal circuit, which makes the geography of the split visually apparent.

A single toggle converts the map into an exposure heat map, shading each circuit from green for low risk to red for high. Read this way, the practical stakes become plain: a company sued in Chicago faces a very different landscape from one sued in Los Angeles.

The table below, pulled from the client alert, segregates circuits by relative exposure per Midpage’s caselaw.
| Circuit | Exposure for text-only do-not-call claims | 2026 rulings (texts are calls : are not) |
|---|---|---|
| 9th (CA, WA, AZ and others) | Highest | 4 : 0 |
| 3d (PA, NJ, DE) | High | 5 : 0 |
| 5th (TX, LA, MS) | High | 5 : 0 |
| 2d (NY, CT, VT) | High | 2 : 0 |
| 6th (OH, MI, KY, TN) | Moderate | 0 : 1 |
| 4th (VA, MD, NC, SC, WV) | Low to moderate | 0 : 1 |
| 10th (CO and others) | Low | 0 : 2 |
| 11th (FL, GA, AL) | Low | 0 : 3 |
| 7th (IL, IN, WI) | Low (binding Steidinger) | 1 : 3 |
The underlying detail remains available throughout. Hovering over Illinois, for example, brings up the cases behind that state’s color, each linked to Midpage, and clicking Richards v. Shein Distribution opens the opinion at the language supporting the map’s characterization. Nothing on the map has to be taken on faith.

Step 4: Draft the client alert
With the research verified and the landscape mapped, the final step was the deliverable itself. I asked the assistant to draft a short client alert for retailers that text customers nationwide, explaining how their exposure differs by circuit and which theories plaintiffs are turning to.
The result reads like something a firm would send. It opens with a bottom line, namely that exposure for a marketing text now depends on where a company is sued, and then walks through the circuit-by-circuit landscape with representative decisions linked. From there it describes how plaintiffs are adapting: adding quiet-hours and internal do-not-call claims, pleading autodialer claims under § 227(b), and invoking state statutes that expressly cover texts.
The alert closes with concrete compliance steps, from honoring opt-out requests across every channel to enforcing quiet hours based on the recipient’s local time. Throughout, every case reference links to the supporting passage in Midpage.
Step 5: Keep it current automatically
As noted, a key weakness with the client alerts I wrote in practice was that they began going stale the moment they were sent. To address that, I asked Claude connected to Midpage to set up a scheduled task that runs every morning:

Because Midpage refreshes with new case law six times a day, the daily update works from data that is hours old rather than weeks. A lawyer still reviews every change before anything reaches a client, but the legwork of finding and summarizing new decisions is finished before the workday begins.
The update in action
When the first version of the alert was finished, it covered 25 decisions. The first scheduled update added three new cases, two new rulings in cases the alert already cited, and a regulatory change.
One of the new additions was Gutman v. Ember Technologies, decided on October 26. A New York federal court treated texts as calls and allowed an internal do-not-call claim to proceed against a consumer-products brand whose agency had resumed sending promotional texts more than a year after the customer replied STOP.
Within a day of that decision, Ember was already reflected in the alert, linked to its source, and counted in the Second Circuit’s row of the exposure table. Clicking it opens the opinion at the relevant passage, just as with every other case in the alert.
That completes the loop. The alert collects the law, analyzes it, presents it in a form clients can act on, and keeps itself current, with every assertion traceable to its source.


Why this matters for legal and knowledge management teams
Each stage of this workflow answers a familiar concern. The initial question produces in minutes what used to take days of survey work. The click-through citations make every conclusion verifiable, so review can focus on judgment and strategy. The map translates the findings into a form decision makers can absorb at a glance. And the scheduled update turns a one-time deliverable into a standing resource that keeps pace with the law.
By changing the topic in the scheduled-task prompt, a firm can build the same kind of standing feed for any issue it wants to own, whether that is a new privacy statute, an emerging wave of class actions, or a developing circuit split. Clients will ask about these issues either way, and the advantage goes to the firm that has answers at the ready.
Want to build your own litigation-wave tracker? Start a two-week free trial and connect Midpage to the AI tools your team already uses.
A note on methodology
This analysis was generated with AI-assisted research using Midpage connected to a frontier AI model. It reflects targeted searches of 2026 federal decisions through October 27, 2026, not an exhaustive survey. This post is not legal advice.