A sticky sender is a rule that once a contact has texted with one of your numbers, every later message to them goes out from that same number. The contact sees one consistent thread, replies land where they expect, and your product doesn't create the impression that five different strangers are texting them. If you run more than one number, you need to decide how new contacts get a number and how long they keep it.
This guide explains why stickiness matters, how it interacts with local presence and number rotation, and how Ready picks a sender when you call the API. It's written for developers and for the sales and agency teams they build for.
What "sticky" means in practice
Without a rule, an account with several numbers can send each text from whichever number is free. Contact A hears from +1 212 on Monday and +1 646 on Wednesday. The phone shows two threads, the second looks like a new, unknown sender, and a reply to the first number may go nowhere useful in your product.
Sticky assignment fixes that with one mapping: contact to sender. The first send picks a number by your chosen method. Every send after that reuses it. If your product shows a conversation per contact, the mapping is what makes the conversation hold together.
Why a contact should keep seeing the same number
There are four practical reasons.
- Thread continuity. The phone groups messages by number. One number means one thread, with the history the contact remembers.
- Recognition. People save a number as a contact. A message from a saved number gets read, and one from a new number gets ignored.
- Opt-out clarity. A STOP is received by a specific number. A clean mapping tells you exactly which sender the contact stopped, and avoids a text from a second number that looks like you ignored them.
- Traffic pattern. Spreading one conversation across many numbers can make each number's traffic look odd. A steady one-to-one pattern on one number looks more like a person.
None of this is a guarantee about deliverability, and it isn't a reply-rate statistic. It's a design choice that makes your product behave predictably.
How local presence and stickiness interact
Local presence means sending from the account's number closest to the contact's area code. It answers "which number should a new contact get?" Stickiness answers "which number should a returning contact get?" They work one after the other, not in competition.
On Ready, with local presence on, Ready sends from the account's number closest to the contact's area code. Every number still sits on the account's registered 10DLC campaign, so local presence chooses among registered numbers and doesn't bypass registration. Local presence is off unless the account turns it on, and it costs $0.0015 for each segment of a delivered text, on top of the text itself. Accounts made before November 16, 2026 keep it free. Check the setting for your account in the app before you rely on it.
Here's the order of decisions:
| Step | Contact state | Which number sends |
|---|---|---|
| 1 | Never texted | The number closest to their area code (local presence) |
| 2 | Texted before | The same number, whatever the area code |
| 3 | Its number was released | Your rule: assign a new number once, then stay sticky on that one |
Local presence helps most when you hold numbers in several area codes. Local presence texting explains the basics and local presence and 10DLC covers the registration side.
Rotation without breaking stickiness
Rotation spreads new contacts across several numbers so no single number carries all the volume. Done wrong, it undoes stickiness: a contact gets a different number on every message. Done right, the rotation is only for the first assignment.
In GoHighLevel on Ready, the #from:local# tag picks the local number, and #from:rotate# spreads new contacts across numbers inside the local area-code group. A contact keeps the number it already texts with. So rotation chooses the first number, and then the contact is sticky. If you use that, the rule of thumb is to rotate across contacts, never across messages to one contact. See GHL local presence tag choice for when to use which tag.
The general discussion of rotating numbers, and when it helps or hurts, is in SMS phone number rotation.
Choosing the sender in the API
On Ready's API, you can leave the sender out and let Ready choose. A first send looks like this.
POST /v1/messages
Idempotency-Key: <any UUID>
{"to": "+12125550199", "body": "Your order #1042 has shipped.", "consent_attested": true} Leave from out and Ready picks the number: the one this contact already texts with, otherwise your number closest to their area code. That's the sticky rule plus a sensible first assignment, with no extra field. If you set from to one of your own numbers, you're choosing the sender yourself for that request. Do that only when you have a reason, such as a customer who must always text from one named line, and note that it replaces the automatic choice.
For a platform, the practical pattern is:
- Store the sender number you used on the first message with the contact record, so your own UI can show it.
- Let the API choose by default.
- Override with
fromonly for a deliberate, documented case.
See the messages API docs for every field. For each customer of your platform, the numbers belong to a sub-account, which keeps one customer's numbers and registration apart from another's (sub-accounts docs).
How many numbers do you need
Stickiness means a number carries every conversation it starts, so capacity matters. A single 10DLC number has per-second and daily limits that depend on the campaign's tier, and those figures are approximate. If one number carries a growing list of active conversations, add more numbers as new contacts arrive. How many SMS numbers do you need shows how to estimate it.
Numbers are $2 a month each on Ready, and registration is $25 a month per customer, with $20 for each extra campaign. Accounts opened before November 12, 2026 keep the prices they signed up with, shown under Billing.
Frequently asked questions
What is a sticky sender in SMS?
A sticky sender is a rule that sends every message to a contact from the same number they've already texted with. It keeps the conversation in one thread on the contact's phone and ties replies and opt-outs to a single sender.
Does local presence conflict with a sticky sender?
No. Local presence picks the first number for a new contact, based on their area code, and the sticky rule keeps that number afterward. On Ready, a contact keeps the number it already texts with.
Should I rotate numbers on every message?
No. Rotate across contacts when you assign the first number, and keep each contact on that number afterward. Changing the sender mid-conversation breaks the thread and makes the new number look like an unknown sender.
Next step
Decide how a new contact gets its first number, store that mapping on your contact record, and send without a from unless you have a reason to override it. To try it with your own numbers, start with the API quickstart, or see the pricing page for number and registration costs.