To add texting to a dialer, you need four things: a send call from the agent screen, a way to receive replies, opt-out handling that both channels respect, and a decision about which numbers carry voice and which carry text. The send call is the easy part. Replies, opt-outs and numbers are where the design work goes.

This post is for product teams building or extending a dialer or call-center app. It covers each of those four things, with the tradeoffs and the Ready specifics, and it's honest about where your app, not the API, has to make the call.

Why dialers add text

Reps who call and get voicemail often follow with a text. A call that goes unanswered is a lead with no next step, and a text gives the rep one. Dialer apps that skip text push that workflow into a second tool, and the rep ends up copying numbers between screens.

The shape that works is one thread per contact. The call log, the voicemail note and the text conversation sit together on the contact. Our guide to call-center dialer software selection covers what buyers look for, and a unified thread comes up often.

If you'd rather not build it, Ready itself has a Dialer billed at $0.025 per minute, with texting in the same inbox. That's a fit for teams buying a tool. This post is for teams building one.

The send path

Sending a text from your agent screen is one call. On Ready it's POST /v1/messages with to, body and consent_attested, authenticated with an X-API-Key header. Add an Idempotency-Key header so a double click or a retry never sends twice. Leave from out and Ready picks the number: the one this contact already texts with, otherwise your number closest to their area code.

POST https://api.tryready.com/v1/messages
{"to": "+12125550199", "body": "Sorry I missed you. When's a good time to talk?", "consent_attested": true}

Three product decisions sit around this call.

  • Who may text. Calling someone doesn't mean they agreed to texts. consent_attested is your promise that the recipient agreed, so your app needs a real place to record that, and a rule for when the text button is enabled.
  • Cold lists. Cold contact is by phone and mail, and SMS goes to consented or replied leads. A dialer that lets a rep text every number in a call list is a compliance problem you built.
  • Segments. Each segment is billed at $0.0075 plus a $0.0045 carrier fee. Show reps a segment counter, since an emoji cuts the limit to 70 characters.

Inbound replies

Replies are the part that surprises dialer teams. A call ends when someone hangs up, but a text thread stays open for days. Your app needs a place for a reply to land, and a way to tell the rep.

On Ready, replies arrive in the Ready inbox, and a webhook can push them to your app. Our inbound webhooks post covers the pattern, and the API quickstart shows how to set one up. Replies are billed like a sent text, at the per-segment rate plus the carrier fee, so a chatty thread costs something on both sides.

Design the inbound side around the rep's attention:

  1. Match to the contact. Look up the contact by E.164 number. If you store numbers in other formats, normalize first.
  2. Route to an owner. Send the reply to the rep who last called or texted, not to a shared pile, or nobody answers.
  3. Surface it where reps work. A badge on the contact and a notification beat a separate inbox they have to remember.
  4. Handle the quiet cases. An unknown number replying means a new lead or a wrong number. Decide which, and where it goes.

Two-way texting also has a rule about replies. A one-to-one or API text to a contact who texted this account in the last 24 hours can go out at any hour. Without a recent reply, quiet hours apply, and an API send outside the window answers 409 QUIET_HOURS_BLOCK.

Opt-outs across voice and text

When someone texts STOP, Ready honors it automatically, and the opt-out propagates so that contact can't be messaged again. Clear phrases like "please stop texting me" or "take me off" are caught too. STOP, START and HELP are answered automatically.

The catch for a dialer is that your call list and your text opt-outs are separate lists. A dialer do-not-call entry isn't part of GET /v1/opt-outs (it is in GET /v1/opt-outs?scope=all, which adds the Ban list), and a text opt-out doesn't write to your dialer. So your app has to decide how the two relate and keep them in sync.

A workable policy:

  • Before any text, check GET /v1/opt-outs/:phone. It's the authoritative answer for that number. To mirror the list instead, sync GET /v1/opt-outs?scope=all once and keep it current: it returns the opted-out contacts plus the whole Ban list, which holds every deleted-contact STOP and every do-not-call number. It still leaves out a STOP held on another account of the same agency family, so keep the per-number check for that case.
  • Before any call, check your own do-not-call list and whatever scrub you run.
  • When a contact asks to stop on either channel, show that on the contact and let a person decide whether the other channel is also off. Many teams treat "stop" as a stop everywhere, because it avoids an argument. That's a policy choice for you and your counsel.

Our posts on syncing opt-outs across channels and the opt-out API go into the sync design.

Sharing numbers between voice and text

The same number for voice and text feels natural: the rep calls from it, the customer texts back to it. Ready's texting runs on local 10DLC numbers, and each customer sub-account has its own numbers and its own registration. Whether your voice numbers can also carry text depends on where those numbers are hosted, so don't assume it. If your voice numbers live elsewhere, email support@tryready.com about a specific number before you design around it.

Here's how the main options compare.

OptionCustomer experienceTradeoff
One number for voice and textCalls and texts come from one placeNeeds both channels to be possible on that number
Separate numbers, one contact threadCustomer sees two numbersEasy to ship, but a reply to the wrong number gets missed
Local number per contactMatches the contact's area codeNeeds the numbers to exist on the account

Whichever you choose, every texting number sits on the account's registered 10DLC campaign. A number costs $2 a month, and registration is $25 a month per customer. Our 10DLC explainer covers why unregistered traffic gets filtered. If you serve many customers, each gets a sub-account, so one customer's opt-outs and numbers don't mix with another's. That's part of how a platform keeps tenants apart.

What to build first

Start with the smallest slice that closes the loop. A rep sends one text after a missed call. The reply lands on the contact and notifies the rep. A STOP blocks the next send. If those three work, you have texting in your dialer, and everything else is polish.

Two honest limits to plan around. Ready's Dialer places one call at a time and doesn't do predictive dialing, so if your app does, the calling side stays yours. And your product, not the API, owns the rule for when a contact may be texted. Build that rule early.

For the full build path, the SMS API integration guide is the next read, and the messages docs have the request details.