An SMS vendor security review comes down to a dozen questions: who owns your carrier registration, how opt-outs are enforced, what data the vendor keeps, how webhooks behave, what happens when the provider is down, and what the vendor will not do. Ask them in writing and keep the answers, because the vendor you pick becomes part of your own compliance story.

We make Ready, so we answer each question ourselves, including the ones where the answer is "no". A vendor that can't answer a row plainly has just answered it.

Registration and numbers

Carrier registration (10DLC) is where most platform migrations get stuck, so ask about it first.

AskWhy it mattersWhat Ready says
Is registration per customer, and who files it?A shared brand means one customer's bad traffic can hurt everyone's delivery.Each customer gets a sub-account with its own numbers and its own registration. Registration is filed in the app or through the registration endpoints in the API docs.
What does it cost and how long does it take?You need this to price onboarding.$25 a month per customer for the brand and its first campaign, $20 for each extra campaign, $2 a month per number. Most approvals take 2 to 7 days.
Who can't register?Edge cases become support tickets.Ready registers businesses with an EIN only. A sole proprietor without one can't register.

Background: our 10DLC explainer.

Opt-outs and consent

AskWhy it mattersWhat Ready says
Is STOP handled automatically and enforced across campaigns?Texting someone who opted out is the expensive mistake.Inbound STOP and UNSUBSCRIBE are honored and the opt-out blocks that number in the sub-account that received it. Clear phrases like "please stop texting me" are caught too. Odd wording no list catches still needs a person reading replies.
Can I read opt-outs through the API?You need them in your own system.GET /v1/opt-outs and GET /v1/opt-outs/:phone. The list is not a complete mirror, so check the single-number endpoint before sending from another tool.
Does the vendor store consent per contact?You may need proof of opt-in.Mostly no. An API send that sets consent_attested records who sent, how many and when, which is an audit trail, not a recipient's opt-in. You keep the real consent record in your form or CRM. The one exception is a sign-up on a Ready-hosted opt-in page, which is stored per contact.

Data, security and compliance claims

AskWhy it mattersWhat Ready says
Will you sign a BAA? Is this HIPAA compliant?A yes you can't verify is a liability.No. Ready is not HIPAA compliant and doesn't sign BAAs. Keep diagnoses, medications and test results out of texts.
What is kept and for how long?Retention drives your own privacy answers.Ask us in writing for the exact policy. We won't invent a schedule in a blog post. For calls, recordings and transcripts are kept while the account is active, and deleting a contact deletes its recordings.
How are API keys handled?A leaked key sends texts on your bill.Keys go in the X-API-Key header. Our notes on key security and rotation cover the practices we recommend on your side.

Webhooks, retries and failure

AskWhy it mattersWhat Ready says
Can a retried send duplicate a text?Timeouts happen.Send an Idempotency-Key header with any UUID and a retried request never sends twice.
How are webhooks signed and ordered?Your receiver has to trust and order them.See the webhook signing post and the API quickstart. Don't assume order, as our out-of-order events post explains.
What happens when the provider has an outage?This is the question vendors dodge.Ready does not fail over between carrier providers. Ready sits as a thin layer over a messaging provider, so an upstream outage reaches you. Plan your own queue and user messaging. Don't resend a text Ready may still resend: see the messages docs.

Rules the vendor enforces for you

Ask what the vendor blocks before a send, not just what it reports.

  • Quiet hours. Campaigns wait up to 24 hours for the window. An API text is held only if the window opens within 6 hours, otherwise it returns a 409 QUIET_HOURS_BLOCK with next_allowed_at, and one call to POST /sms/schedule with send_at set to that time sends it when the window opens (scheduled messages docs). Replies to a contact who texted in the last 24 hours go out at any hour.
  • Bans and landlines. Opt-outs and numbers on your ban list are refused up front and not charged.
  • Litigator and DNC scrubbing. Known matches can be screened out before send when send-time scrubbing is on. Otherwise the scrub only reports. This is risk reduction, and compliance stays your responsibility.

Pricing and support questions

Ask for the all-in per-segment figure and what it leaves out. Ours is $0.0075 per segment plus a $0.0045 carrier fee, so $0.012 all-in, which does not include screening. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing. Full list at pricing. Then ask who answers a support ticket and whether you can reach engineering. Write down the response you get before you sign.

Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.

Next step

Print the tables, send them to your shortlist and compare the replies side by side. If Ready is on it, read the API quickstart and send a test before you commit.

Frequently asked questions

Does Ready sign a BAA?

No. Ready is not HIPAA compliant and doesn't sign BAAs, so keep protected health information out of texts.

Does Ready fail over to another provider during an outage?

No. Ready doesn't fail over between carrier providers. It does resend some failed texts itself under the same message_id, so before you resend a failed text, check that Ready has finished with it (see Failures Ready resends for you).

Does Ready keep a consent record for every contact?

Not in general. The sender keeps it in their form or CRM, and an API send with consent_attested leaves an audit trail of the send. Sign-ups on a Ready-hosted opt-in page are stored per contact.

Who owns the registration?

Each customer gets its own registration under a sub-account. Ask any vendor, including us, what happens to it if you leave.