A lead generation agency can text leads safely only when each lead agreed to be texted by the business that will text them, and the agency can show where that agreement came from. Everything else, from registration to scrubbing, supports that one fact.

The risk sits with the agency because it sits in the middle. You collect the form fill, a client sends the follow-up, and a regulator or a plaintiff's lawyer asks who consented to what. This guide covers the four pieces that decide whether that question is easy or painful: consent, lead source disclosure, scrubbing and per-client sub-accounts.

Consent has to name who will text

The consent a lead gave must cover the business sending the text, in words the lead saw. A generic "we may contact you" on a landing page isn't a safe base for a client's follow-up.

Build the form so the checkbox names the client (or the brand the lead was shopping for), says the messages are automated marketing texts, mentions message frequency and that data rates may apply, and links to terms and a privacy policy. Don't pre-check the box. Don't bundle it with the submit button.

Be honest about what you can't recover later. If a lead filled in a form three years ago for a different brand, that consent doesn't transfer to your client. Our guide to documenting SMS consent goes through what to store, and the consent language guide has wording that carriers accept on registration.

What Ready records and what you keep

Ready doesn't store a per-contact consent record. The agency keeps the opt-in time, the exact wording and the page URL in its own form tool or CRM. What Ready captures is the sender's attestation: an API send that sets consent_attested records who sent it, to how many people and when. That's your promise that the recipient agreed, and it's an audit trail of the promise, not proof of the agreement itself.

An API send without consent_attested still goes out today, with a warning and no attestation, so set it on every call. (If a client collects sign-ups on a Ready-hosted opt-in page, that one case is stored per contact with the time, IP and exact wording. Support at support@tryready.com can send a copy.)

Lead source disclosure

Keep a source field on every lead and make it travel with the contact. At minimum it should say which form or ad produced the lead, the date, the brand named in the consent and the client who owns the follow-up.

That field answers three questions you'll be asked:

  • Did this person opt in, and to whom?
  • Did they come from our own form, or from a partner who sold us the list?
  • Which client should have been texting them?

Bought, rented and scraped lists are the line to hold. Texting a list nobody on it agreed to is the exposure, and a scrub doesn't turn it into a consented list. Phone and mail are the cold channels, and SMS goes to leads who opted in or replied. Our post on lead generation and affiliate texting rules covers where affiliate traffic gets risky.

Scrub before the text, not after the complaint

A scrub checks a number against known TCPA litigator and Do Not Call complainer lists and tells you which numbers matched. It reduces risk. It doesn't make a send lawsuit-proof, and compliance stays the sender's responsibility.

Two ways to run it on Ready:

MethodHow it worksPrice
Standalone scrubPOST /v1/scrub, up to 1,000 numbers per call (GET /v1/scrub/:phone for one), or run a whole list from the dashboard$0.005 per contact
Send-time scrubA switch in Settings under Compliance, per account$0.003 extra per segment, off by default

The standalone scrub only reports matches. It blocks nothing by itself. The send-time switch is what refuses a text to a flagged number, so turn it on for client sub-accounts that handle leads from outside sources. Our litigator scrubbing explainer explains what those lists contain.

One sub-account per client

Give each client its own sub-account so their numbers, registration, opt-outs and billing stay apart. You create them with POST /v1/sub-accounts and list them with GET /v1/sub-accounts.

Separate sub-accounts matter for three reasons. A carrier registration belongs to one brand, so a client's campaign shouldn't ride on another client's registration. A complaint or a filtered number on one client doesn't spill onto the others. And your invoice math gets simple, because every segment belongs to a named client.

Registration is a single line per customer: $25 a month for the brand and its first campaign, $20 a month for each extra campaign, and $2 a month per number. Most approvals take 2 to 7 days. Ready registers businesses with an EIN only, so a client without one needs to get an EIN before you can file. A STOP always blocks that number in the sub-account that received it. Whether it also blocks the parent and the other sub-accounts is decided by Ready for every account, not by a setting you can change, so check GET /v1/opt-outs/:phone before you reuse a lead across clients.

A short checklist for each new client

  1. Collect the consent wording and the form URL the client's leads actually saw.
  2. Create the sub-account and file registration with the client's real business details.
  3. Import leads with the source, date and consent brand attached.
  4. Run the standalone scrub on the first list, and decide on the send-time switch.
  5. Send through the API with consent_attested set and an Idempotency-Key header, reused on every retry, so a retry never sends twice.
  6. Watch opt-outs and review the first replies by hand.

Texts are billed at $0.0075 a segment plus a $0.0045 carrier fee, and accounts opened before November 12, 2026 keep their signup prices, shown under Billing. The pricing page has the full list.

Frequently asked questions

Can I text leads my client bought from a vendor? No. The acceptable-use policy bars texting purchased or rented lists, and a scrub doesn't change that. Text people who opted in or who replied to you.

Does a scrub guarantee I won't get sued? No. It lowers the chance of texting a known litigator or complainer, but consent, quiet hours and honest message content still decide your exposure.

Do I need a sub-account for every client? Yes, if you want separate registration, numbers and opt-out handling. It's also the cleanest way to bill each client for exactly what they sent.

The practical takeaway

Treat consent as the product you sell, and treat the text as the delivery. Keep the source field, scrub the lists that came from outside, and give every client a sub-account. If you'd like to try it, create an account and send your first one-to-one texts to see the flow end to end.