Turn on Telnyx as your native SMS provider

For admins · Updated Sep 23, 2026

All guides

HighLevel calls the system that actually sends and receives your SMS a Conversation Provider. By default, that is HighLevel’s own built-in carrier. Phone Clover can register itself as that provider instead, so texts sent and received through HighLevel’s own Conversations screen travel over Telnyx.

What changes for reps

Nothing about how a rep sends a text changes. They keep using the same Conversations screen, the same compose box, the same threads. The only difference is which carrier the message actually rides on behind the scenes, and the delivery detail and number-health information Phone Clover can show you because it owns that path.

Before you start

Who can do this: an admin of the HighLevel sub-account.
What you need: at least one number connected to Phone Clover. See Set up your first number.
US business texting also needs A2P 10DLC registration before carriers will reliably deliver your messages at volume. See Register for A2P 10DLC. You can turn on the native provider before registration finishes, but expect delivery problems on high-volume sends until it clears.

Turning it on

Ask your admin, or check Settings → Texting in Phone Clover, to confirm whether the native SMS provider is switched on for your sub-account. Once it is on, every text sent from HighLevel Conversations for a contact tied to your Phone Clover number routes through Telnyx automatically. No separate action is needed from reps, and no workflow, automation or integration that already sends texts through Conversations needs to be changed.

Note: this setting applies at the HighLevel sub-account level. If you manage multiple sub-accounts, each one needs to be switched on separately.

Confirm it’s actually live

Ask your admin to confirm texting runs through Phone Clover by checking Settings → Overview → Phone health → Telnyx messaging badge, and Settings → Texting → Business texting registration status. If either shows a problem, texting may still be running on HighLevel’s default provider instead. See What the settings health badges mean.

What this enables

Once the native provider is active:

Texts sent from Conversations, from a workflow Send SMS step, and from bulk sends all go out from your Telnyx number. See Send a text from Conversations, Send SMS from a workflow and Send bulk SMS.
Inbound texts to your number pass through Phone Clover’s spam filtering before HighLevel ever sees them. See SMS firewall: block and allow lists.
Failed sends get a plain-English reason instead of a generic error. See Why texts fail and what the reasons mean.
Number health monitoring and optional auto-rotate become meaningful, since Phone Clover is the system actually sending your texts. See Number health radar.

Troubleshooting

Texts still seem to be sending from HighLevel’s own number, not mine. Confirm the contact’s conversation is actually associated with your Phone Clover number, and that the native provider setting is switched on for this specific sub-account. A multi-sub-account agency needs to check each sub-account separately.

Some texts go through and others fail immediately after switching this on. This is usually an A2P 10DLC registration gap, not a provider problem. Check Register for A2P 10DLC and Why texts fail and what the reasons mean.

I’m not sure if this is already on. Check the Telnyx messaging badge on Settings → Overview, described in What the settings health badges mean, to confirm your account’s current status. If you need help, contact support.