Bulk texting works for a sales team when the list is made of people who agreed to hear from you and replies land somewhere a rep will see them. It fails when a team sends a campaign to a purchased list and lets answers pile up unread. The compliance work and the reply routing matter more than the send button.

This post covers when to send a campaign and when to text one to one, what to check before a send, and how to run replies so no lead goes cold.

One-to-one or campaign

Use one-to-one for anyone in an active conversation, and a campaign for an announcement everyone on the list has already asked for. The difference is intent. A one-to-one text is a rep following up with a specific person. A campaign is the same message to a segment.

SituationBetter fit
Rep replying to a lead who texted inOne to one
Follow-up after a call or demoOne to one
Event reminder to registered attendeesCampaign
New offer to opted-in customersCampaign, segmented
Cold list you boughtNeither. Call or mail instead

That last row matters. Cold contact is by phone and mail. SMS goes to consented or replied leads. A campaign to people who never opted in is how teams end up in TCPA trouble.

Consent comes first

You need a record of why each person is on the list. Ready records the sender's opt-in attestation for each bulk send and for API sends that set consent_attested: who sent, to how many, and when. It isn't a per-contact consent record. Ready stores no recipient opt-in time or wording, so you keep that in your form or CRM. The one exception is a sign-up on a Ready-hosted opt-in page, which is stored per contact.

If you want the legal background, our plain-English TCPA guide for texting is a good start.

Scrub before you send

Scrubbing checks numbers against known TCPA-litigator and Do Not Call complainer lists, so you can find risky numbers before a campaign goes out. The standalone scrub is $0.005 a contact, and you pay only for what you check. It only reports which numbers matched. It blocks sends only on accounts with send-time scrubbing switched on in Settings under Compliance.

Scrubbing reduces exposure. It doesn't make a send lawsuit-proof, and the sender is ultimately responsible. For the difference between the lists, read DNC, litigator and TCPA lists explained.

Timing and quiet hours

Texts shouldn't land at 2 AM, and Ready enforces that by the recipient's area. Campaigns wait up to 24 hours for the window to open. A text a rep types to one person in the Inbox outside the window is scheduled for when it opens, however far off, and shows in the thread. A text sent through the API is held only if the window opens within 6 hours, otherwise it isn't sent, and your code has to send it again once the window opens.

There's one exception worth knowing. A reply to a contact who texted your account in the last 24 hours can go out at any hour. That's why quick answers to inbound leads aren't blocked.

If your list spans time zones, this post on multi-timezone campaigns shows how to plan the send.

Opt-outs run themselves

When someone texts STOP, Ready honors it and blocks that number from further messages. Clear phrases like "please stop texting me" or "take me off" are caught too. Odd wording that no list catches still needs a person to read the reply, so reps should skim replies rather than assume the system saw everything.

Ready adds "Reply STOP to opt out" and your business name to the first text to each contact unless you turn that off. Count those characters when a message sits near a segment limit.

Route replies so nobody waits

Replies come into the Ready Inbox as threads, next to the history for that contact. That's your shared inbox: every rep on the account can see the thread and answer from the same number the lead already knows.

To make sure someone notices, connect Slack under Settings, Integrations, Apps and pick a channel. Ready posts each inbound reply and opt-out there. Automations also have Slack steps that message the contact's assigned teammate. Sending a text from Slack isn't built, so reps answer in the Inbox.

A simple routing habit goes a long way:

  1. Decide who owns replies for each list before the send.
  2. Point the Slack channel at that team.
  3. Set a response target, such as within the hour in business hours.
  4. Review opt-outs and odd replies once a day.

Replies are billed like a sent text, at the per-segment rate plus the carrier fee, so a good campaign produces reply costs too. Budget for them.

What it costs

Ready's Standard rate is $0.0075 a segment, plus a $0.0045 carrier fee a segment. Registration is $25 a month for the brand and first campaign, and each number is $2 a month. Most approvals take 2 to 7 days. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.

Segments, not messages, are what's billed. A 175-character text with an emoji is three segments, so cut length where you can. The bulk SMS cost guide has more worked math, and the pricing page lists every line.

The takeaway

Text consented leads, scrub the list, respect quiet hours, and route replies to a named owner. Use one-to-one for conversations and campaigns for announcements people asked for. When you want to try it, sign up and send to a small list first.