A rep finishes a call, picks an outcome, and moves to the next lead. Whether anything else happens to the person they just called is usually left to memory. The follow-up text that would have saved the deal gets skipped on a busy afternoon, or sent late, or sent to someone who just said no.
The fix is small: decide, in advance, which text (if any) goes with each call outcome. This post gives you a rule per disposition, the consent check that comes first, and wording you can adapt. It pairs with the Ready Dialer, where a rep places one call at a time from the dial pad, but the rules work with any dialer.
First, the consent check
A call isn't consent to text. This is the part that gets teams in trouble, so settle it before you write any rules.
Cold contact is by phone and mail. SMS goes to people who agreed to texts or who replied to you. So a follow-up text is safe to send in two situations: the person already opted in somewhere (a form, a signed document), or they said yes on the call. "Mind if I text you the details?" followed by a yes, noted on the record, is a clean way to turn a call into permission.
If neither is true, don't send the text. Call again or send mail. Compliance is the sender's responsibility, and the call record is where you keep the proof. Our post on documenting SMS consent shows what to store.
Two more gates apply before any text goes out. Quiet hours follow the recipient's area, and an opted-out number is refused. Both are handled at send time, so a rule that fires late in the evening may be held or refused. That's the system working, so build your rules to expect it.
A rule for each disposition
Dispositions vary by team (see call disposition codes for sales dialers for a full list), but most fall into a handful of buckets.
| Disposition | Follow-up text? | Timing | Condition |
|---|---|---|---|
| No answer | Sometimes | Within the hour | Only with prior consent |
| Left voicemail | Yes, short | Right after | Only with prior consent |
| Spoke, interested | Yes | Within minutes | Consent given on the call or before |
| Callback requested | Yes, confirms time | Right after | Consent given |
| Spoke, not interested | No | n/a | Log the reason |
| Wrong number | No | n/a | Remove or fix the number |
| Do not contact | Never | n/a | Add to the opt-out list |
Everything in "Yes" is conditional on the consent check above. The table shows what to send, not whether you may.
Wording that fits each outcome
Keep each text to one segment where you can. A single GSM-7 segment is 160 characters, and an emoji pushes you to 70 characters per segment, so a friendly extra can triple the length. Segment counting explains it.
- Left voicemail. "Hi Dana, it's Sam at Northfield Roofing. I left you a voicemail about the estimate. Reply here if texting is easier."
- Interested. "Thanks for the time today, Dana. Here's the link to book the inspection: [link]. Reply with questions anytime."
- Callback requested. "Got it, Dana. I'll call you Thursday at 2 pm. Reply here if that changes."
- No answer, with consent. "Hi Dana, Sam from Northfield Roofing. Tried you a minute ago. Is now a bad time?"
Two habits help. Put the business name in the first line, because the person may not remember the call. And end with a way out; the standard opt-out handling covers STOP replies automatically, so you don't need a long disclaimer in every message. For more on message length and tone, see text message etiquette and follow-up after no response.
How this works with the Ready Dialer
Here's what's built and what isn't, so you can plan around it.
- The Ready Dialer is click-to-call from the dial pad, in the dashboard or in GoHighLevel. The pad places one call at a time. There's no predictive or parallel dialing, no queue that calls on its own, and no voicemail drop.
- The Dialer records dispositions on calls a rep places. It doesn't send a text for you when a disposition is saved, so the follow-up is a step you add: the rep sends a text from the inbox thread right after the call, or your own software sends one through the API when it sees the outcome.
- A Missed call card appears in the Inbox thread for each call you miss, which is a natural place to answer by text.
- Calls are refused outside calling hours in the contact's local time: 8 AM to 9 PM, with a tighter window for Florida and Oklahoma (8 AM to 8 PM) and Connecticut (9 AM to 8 PM) area codes.
- A call is billed at $0.025 a minute, for answered time only, with each started minute billed as a full minute. A call nobody picks up costs nothing.
A text is billed separately at the Standard rate of $0.0075 per segment plus a $0.0045 carrier fee. The pricing page has the full list.
If you want the rep to stay in one place, the inbox keeps the call card and the text thread together. If you're building the rule yourself, the pattern is simple: when your system records a disposition from the table, check consent, then send one text with an Idempotency-Key so a retry never sends twice. The request shape is in the messages API docs.
A worked example
Say a rep makes 60 calls in an afternoon. Assume 40 go unanswered, 8 reach voicemail, 12 connect, and of those 12, 5 are interested, 3 ask for a callback and 4 say no.
With consent in place for every contact, the rules above send 8 voicemail texts, 5 interested texts and 3 callback confirmations: 16 texts, or 16 segments if each fits in one. At $0.0075 plus the $0.0045 carrier fee per segment, that's the figure to multiply out for your own rate card. The 12 connected calls bill by the minute at $0.025. The 40 unanswered calls cost nothing. The texts also reach the 8 people who didn't pick up.
These counts are assumptions for illustration, not benchmarks. Your own ratios will differ, so run the same sums with last week's call log.
Mistakes to avoid
- Texting after a "not interested". It's the fastest route to a complaint.
- Treating a connected call as consent.
- Sending a text that repeats the voicemail word for word. Add something: a link, a time, a question.
- Texting at night because the rule fired at 8:45 pm. Let quiet hours do their job and send in the morning.
- Forgetting the Do not contact bucket. Put it in the opt-out list the same day.
Speed to lead covers the opposite problem, the first touch for a new lead, and missed call text-back covers inbound calls you couldn't answer.
Frequently asked questions
Can I text someone right after I leave a voicemail?
Only if they agreed to texts, either earlier or on a previous call. Without that, stay with calls and mail.
Does the Ready Dialer text automatically after a call?
No. The rep sends the text from the inbox, or your own software sends it through the API after it records the outcome.
Should I text after every no answer?
Usually not. One text after the first miss is enough. Repeated texts to someone who hasn't replied wear out your sender reputation.
Next step
Take the table above and cut it to the three rules your team will actually follow, probably voicemail, interested and callback. Add the consent question to your call script, then check a week of calls to see how many texts went out and how many replies came back. If you want to try the pad and the inbox together, you can set it up from the signup page.
Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.