We set up GoHighLevel for you · Book a free 15-minute callWe set up GoHighLevel for you
Book a call

GoHighLevel texts sending from the wrong number

A woman reading a text message on her phone

Short answer

GoHighLevel chooses the number a text goes from in order: a number picked for that message, then the number assigned to the sending user, then the number already used in that conversation, then the account's default. A workflow's From number overrides the user's and the conversation's. Texts go from the wrong number when an old conversation is tied to a previous number, the user has a different number, the workflow's From number is blank, or the chosen number can't text.

How to fix it

  1. See which number sent it. Hover over the text, open its ⋮ menu and choose Details.
  2. Change it for one conversation. In Conversations, open the contact, choose SMS and pick the From number. Old conversations stay on the previous number until you change it.
  3. Check the user's number. Settings > My Staff (or Users) > edit the user > Call & Voicemail Settings. Only one user can hold an LC number at a time.
  4. Set the workflow's number. Workflow Settings > Sender Details > From number applies to every text in that workflow; the Send SMS step has its own From Number too.
  5. Check the default number. The default outbound number is the fallback, and HighLevel falls back to it when the assigned number can't text.
  6. Make sure it can text. The number has to support SMS and be registered: A2P 10DLC, or toll-free verification.

How to find the cause

Open the text's Details (the ⋮ menu on the message) to see the exact number it went from. Then match that number to the rule in HighLevel's order that picked it.

The number it went fromWhy HighLevel picked itWhat to do
The sending user's own numberNobody chose a number for that message, so the user's assigned number wonPick the From number in the composer, or change the user's Inbound Number under Settings > My Staff > Edit > Call & Voicemail Settings
An older number the contact texted beforeThe conversation stays on the number it's already usingPick the new number from the From dropdown in that conversation
Your default number, when you expected anotherThe number you expected can't send SMS, so HighLevel fell back to the defaultCheck that number can text and has the A2P Verified label
A different number from each workflowEach workflow's Sender Details, or each Send SMS step's From Number, sets its ownSet the From number in every workflow that texts customers
Missed call texts from a number they didn't callMissed Call Text Back uses the dialed number only if it can text; otherwise the last number that messaged the contact, then the defaultMake the dialed number SMS-capable and registered
A number you don't recognize, or one from another locationThe number may be assigned to a different HighLevel location, or left over from before a moveCheck it's provisioned in this location's phone system, and re-select the right number wherever it's used

If sending fails with an error saying the From number isn't SMS-capable, HighLevel lists the usual reasons: the number is voice-only, it belongs to a different location, it isn't linked to an approved A2P campaign, or it was recently moved and old settings still point at it. After a move, re-select the number in Conversations, campaigns and workflows.

Only one user can hold an LC number at a time. If several staff share one line, HighLevel points you to the number's own settings under Phone System for call routing rather than assigning it to each user; for texts, set the From number in the workflow or the conversation.

How to confirm it's fixed

  1. Test as each user who texts. Have each one send a text to your own phone from Conversations without touching the From dropdown. Details on each message should show the number you expect for that user.
  2. Run each texting workflow once. Add a test contact with your own phone and trigger the workflow. Details on the message should show the workflow's From number.
  3. Reply from your phone. The reply should land in the same conversation in HighLevel, and your next text from there should go out from the same number.
  4. Check your phone's message list. All the test texts should sit in one thread from one number. Two threads mean two numbers are still sending.
  5. Test a missed call. If you use Missed Call Text Back, call each of your numbers, let it ring out, and check the text comes from the number you called.

Where this shows up in GoHighLevel

  • A message's Details, from the ⋮ menu when you hover over it: the exact number that sent it.
  • The From dropdown in the Conversations composer: admins see every number in the account; other users see the default, last-used, their own and unassigned numbers.
  • Settings > My Staff > Edit > Call & Voicemail Settings > Inbound Number: the number assigned to each user.
  • A workflow's Settings tab > Sender Details > From number, and the From Number on each Send SMS step, which takes priority for that message.
  • Settings > Phone System > Phone Numbers: whether each number can send messages, and the green A2P Verified label on local numbers linked to an approved campaign.
  • Settings > Phone System > Voice > Voicemail & Missed Call Text Back: the missed call text, which follows its own number order.

Common questions

Why did a customer get texts from two numbers?
Different users, workflows or the default sent them. Set the workflow's From number and the user assignments.
Can staff choose any number?
HighLevel says regular users see the default, last-used, their own and unassigned numbers.

More texting fixes

All Texting & A2P fixes

Want GoHighLevel set up and running for you?

Book a free 15-minute call. Tell us what you sell and where your leads come from, new account or the one you have, and we'll tell you what we'd set up, how long it takes and what it costs.

Rather we set it up? Complete GoHighLevel setup, done for you.

See the packageBook a call