Agency management systems already hold what a text needs: the policyholder, the phone number, the policy, the renewal date and the producer who owns the relationship. What they often lack is a way to reach the person on the channel they actually read. Email gets buried, and a voicemail about a renewal rarely gets returned.

This guide is for the software company building that feature into an AMS, a quoting tool or a policy servicing portal. We'll cover the messages that fit, where consent comes from, how to keep each agency separate, and the compliance limits you should design around. If you're an agent looking for texting for your own book, SMS for insurance agents is the better read.

Messages that fit an agency workflow

The best insurance texts are short, specific and tied to something the policyholder already has with the agency.

  • Renewals: a heads-up 30 to 45 days before the term ends, with a way to reply or call.
  • Billing: a payment reminder or a note that a payment was received.
  • Documents: "your updated ID cards are ready in the portal", with no policy details in the text.
  • Claims: acknowledgement, adjuster assigned, "we need two photos".
  • Service: a certificate request is done, a policy change is processed.
  • Reviews and referrals: a polite ask after a claim closes or a policy is bound.

Keep the body free of sensitive detail. A text isn't the place for a full policy number, a diagnosis or a medical claim description. Our payment reminder message post has wording that works for billing nudges without spelling out the account.

Health lines need a hard rule

Many agencies sell health, life and Medicare products. Ready isn't HIPAA compliant and doesn't sign BAAs, so your product shouldn't send protected health information through it. Plan messages that carry no diagnoses, medications, test results or claim details. "Your documents are ready, please log in" is fine. "Your claim for the knee procedure was denied" isn't. Build that rule into your templates, not into a training document nobody reads. See SMS and HIPAA classification for how the line is usually drawn.

One sub-account per agency

Your customers are separate businesses, often with separate licenses and brand names. Each should have its own sender. On Ready, a sub-account holds its own numbers and its own 10DLC registration, so one agency's traffic and reputation don't touch another's.

You create a sub-account with POST /v1/sub-accounts and list them with GET /v1/sub-accounts. Registration is one line: $25 a month per customer 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 an agent working as a sole proprietor without one can't register; plan for that in onboarding rather than finding out after signup.

Agency typeSub-account setupNotes
Independent agencyOne sub-account, one brandCampaign for customer care and renewals
Agency with several brandsOne per legal entityDon't share a number across entities
Captive or MGA networkOne per agency, not per carrierProducers send from the agency's number

The vertical SaaS onboarding guide shows how to automate signup so a new agency doesn't wait on your team. The docs cover registration and sub-accounts.

Consent: what you store and what Ready stores

Insurance is a place where consent is easy to get wrong. A quote request, a policy application and a purchased lead are three different situations. A form where the person asked about coverage is one thing. A list a lead vendor sold you is another, and it's the one that draws complaints. Cold contact is by phone and mail; SMS goes to consented or replied leads.

Your software should capture, per policyholder: when they agreed, the exact wording, and the source (application, portal checkbox, quote form). That record belongs in your database. When you send with consent_attested: true, Ready records the sender's attestation: who sent, to how many, and when. It isn't a per-policyholder record, and Ready doesn't store each recipient's opt-in time, wording or page URL. The one exception is a sign-up on a Ready-hosted opt-in page.

Until January 20, 2027 (UTC), an API send without consent_attested still goes out, with a warning and no attestation. From that date it's refused with 403 api_consent_attested_required. Our consent record schema post has a layout you can copy. Compliance stays the sender's responsibility.

Sending a renewal reminder

A renewal text is one API call per policyholder or a bulk call for a batch.

POST https://api.tryready.com/v1/messages
X-API-Key: <the agency's sub-account key>
Idempotency-Key: <one UUID per message, reused on retry>

{"to": "+12125550199", "body": "Your policy renews on Dec 15. Reply here or call us to review it.", "consent_attested": true}

For a batch, POST /v1/messages/bulk takes up to 100 recipients per call, so split a large book into chunks. The idempotency key matters in a renewal run: a job that retries after a timeout would otherwise text the same person twice about the same renewal.

A single-segment text costs the Standard rate of $0.0075 plus a $0.0045 carrier fee. A message with an emoji or a curly quote can switch encoding and split into more segments, so test your templates. Segment math for developers explains why.

STOP, quiet hours and replies

Every policyholder text needs an exit. Ready honors STOP automatically and refuses opted-out numbers up front without charging for them. A STOP always blocks that number in the sub-account that received it. For whether it reaches other sub-accounts, check GET /v1/opt-outs/:phone. Show opt-out state on the policyholder record so a producer knows why a send was refused.

Quiet hours follow the recipient's area. A single API text is held only if the window opens within 6 hours; otherwise the API answers 409 QUIET_HOURS_BLOCK and your software sends again once the window opens. A reply to someone who texted in the last 24 hours can go out at any hour.

Replies are the valuable part. "Can you quote my second car?" should reach the producer who owns that household. Webhooks deliver inbound texts to your app; see the inbound webhooks guide.

A worked example, with assumptions

Say your AMS has 150 agencies, and each averages 2,000 policyholders. Assume each policyholder gets two one-segment texts a year, a renewal reminder and a payment note. That's 150 × 2,000 × 2 = 600,000 segments a year, or 50,000 a month on average, billed at $0.0075 plus the $0.0045 carrier fee. Add $25 a month per agency registration and $2 a month per number. Renewals cluster, so plan for peaks and remember that carriers limit per-second throughput on a fresh campaign. See forecasting SMS costs for a new feature, and the pricing page for exact figures.

Frequently asked questions

Can we text policyholders about claims?

Yes, for logistics like "an adjuster was assigned" or "please send two photos". Keep health details and claim specifics out of the body.

Does Ready store each policyholder's consent?

No. It records the sender's attestation on a send. Keep the per-person record, with time, wording and source, in your own system.

Can a producer text from a personal phone?

Texts go out from the agency's registered number through your software, which keeps the sender consistent and the conversation in one place.

Next step

Choose the one message your agencies ask for most, usually the renewal reminder. Map one agency to a sub-account, store its consent source, and send a test through the API quickstart. When that works, add the rest of your templates one at a time.

Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.