Link Leads Blog · November 10, 2026

Washington telephone solicitation act: what insurance agents need to know before calling WA leads

In 2023, Washington raised its telemarketing statutory damages tenfold and turned every violation into a Consumer Protection Act claim on top. Here's what the statute covers, what the amendment changed, and how to work a Washington slice of an aged list without walking into it.

A third state with its own rulebook

Our post on manual dialing vs. autodialer covers how the Supreme Court narrowed the federal definition of an "automatic telephone dialing system" in 2021, and notes that a handful of states never adopted that narrower reading. Florida and Oklahoma are two of them. Washington is a third, and it got stricter in 2023. The Washington Telephone Solicitation Act (WTSA), codified at RCW 80.36.400, has regulated solicitation calls made with an "automatic dialing and announcing device" since the 1980s. What changed four years ago is how expensive getting it wrong became.

What the WTSA covers

The statute restricts commercial solicitation calls and texts placed with automated dialing equipment to Washington numbers, and its equipment definition — "automatic dialing and announcing device" — is older and broader than the federal ATDS standard the Supreme Court narrowed in 2021. It doesn't turn on whether a system generates numbers randomly or sequentially the way the post-Duguid federal reading does; it reaches equipment built to dial automatically from a stored list, which covers most commercial dialers and bulk texting platforms in practical use today. One detail worth knowing before you filter a national list by area code: the statute's protection follows the person, not just the area code. It applies to any number with a Washington area code or to a phone registered to a Washington resident on the state's do-not-call registry — so a transplant who kept an out-of-state area code can still be a Washington record for WTSA purposes, and a Washington area code that ported out of state might not be.

What the 2023 amendment changed

The Robocall Scam Protection Act (ESHB 1051) amended RCW 80.36.400 three ways that matter here. First, a WTSA violation is now a per se violation of Washington's Consumer Protection Act, so a plaintiff doesn't have to separately prove the "unfair or deceptive" elements a CPA claim normally requires — the TSA violation itself does that work. Second, the statutory damages floor went from $100 per violation to the greater of actual damages or $1,000 per violation, a tenfold jump, with CPA treble damages stacked on top up to a statutory cap. Third, liability now reaches anyone who assists in transmitting the illegal call or text, not just the business whose name is on the pitch — the platform, answering service, or list broker that helped send it is exposed too. That last point is why "we just supplied the data" isn't the shield some vendors imply it is.

What this means for a Washington slice of an aged list

Aged data carries no prior express written consent tied to you as the caller — true of any aged list, Link Leads' included, and no vendor can honestly sell a file that changes that fact. Practically, the WTSA's broader equipment definition means the safer posture on Washington records is a manually placed call or a manually sent text, one record at a time, rather than a predictive dialer or bulk-send platform. A tool a court might read as outside the narrowed federal ATDS definition after Duguid is not automatically outside Washington's older, broader standard — and after 2023, getting that wrong costs ten times what it used to, before the CPA claim is even added.

Consent age doesn't help here either

Some agents assume an aged file is lower risk because the original data capture happened a while ago. Under a statute keyed to consent for automated contact, age cuts the other way: a record captured with some form of consent at the point of collection typically wasn't consent to be contacted by you, specifically, months or years later. See how we source leads for what "aged 30–90 days" does and doesn't mean — it's a reason to work Washington records manually, not a reason to skip them.

Texting Washington numbers: the landline check still matters first

None of the above matters for a record that can't receive a call or text in the first place, and a purchased phone file — even a 96% mobile-validated one — still has landlines and disconnected numbers mixed in by the time you work it 30–90 days after capture. Run a phone-type check before any Washington slice goes to a texting queue, ideally in the same pass as your DNC scrub. We point buyers at Landline Remover for this (an affiliate link — we may earn a commission if you sign up through it): upload the CSV and it flags landlines, disconnected numbers, and DNC-listed contacts together, so you're not spending a text credit — or taking on WTSA exposure — on a number that was never going to receive the message. The full workflow, including where this step sits relative to dedupe and registry checks, is in the DNC scrub walkthrough.

Calling hours and the state registry

Most Washington compliance guidance cites an 8am–8pm local-time calling window, an hour tighter on the back end than the federal 8am–9pm default most agents build their schedule around — confirm the current rule before you set a Washington-specific block, since this is exactly the detail state legislatures revisit. Washington residents can also register on a state do-not-call list alongside the National DNC Registry, so a national-only scrub isn't a complete scrub for a Washington slice.

A 50-state list needs a state-by-state pass

Florida, Oklahoma, and now Washington arrive at the same practical advice through three different mechanisms: a single "state overlay" rule doesn't cover a 50-state pull correctly. Florida leans on calling-window and volume restrictions, Oklahoma on a broad equipment definition plus a private right of action, Washington on tenfold statutory damages stacked with a CPA claim and third-party liability. A compliance checklist built state by state — not one rule assumed to apply uniformly — is the only version that holds up once a list spans more than a handful of states.

A script structure that keeps it low-risk

Whatever state the record is in, the opener does the same job: identify the caller, not the list, and make opting out effortless from the first message. Never greet the person by name or use a name placeholder — the agent introduces themselves, not the recipient:

"Hi, this is {agent} with {agency} in {state}. I work with folks in your area on [coverage type] — is now an OK time for two quick questions? Reply STOP anytime and I'll take you off the list."

On a live call, state your name and company first, ask permission before pitching, and treat any version of "take me off your list" as an immediate stop and a marked record — not just the literal word "stop."

Not legal advice

This is a practical planning guide, not legal advice. The WTSA, the federal TCPA, and how courts apply each to a specific calling or texting program are subject to amendment and interpretation this article can't track in real time. Talk to counsel familiar with Washington telemarketing law before you scale a campaign into the state, especially one using an automated dialing or bulk texting platform.

Building a Washington-safe list

Link Leads sells aged consumer data leads by state at a flat $0.012 per lead, minimum order 5,000 leads ($60), so you can pull a Washington-only slice sized to what you can actually work by hand — the Washington leads page has current record counts and pricing. Build a custom order in the order builder, or start with the free 100-row sample before you commit to a batch.

These are aged data leads (not consented insurance-form leads) and are not DNC-scrubbed. Buyers are responsible for DNC scrubbing and dialing/texting compliance.