Turn on Telnyx as your native SMS provider

For admins · Updated Oct 20, 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.

Note: Early access. Texting from HighLevel Conversations runs on Telnyx in our pilot account. Workflow and bulk texting are not proven yet, and 10DLC registration on the pilot is still to come, so we do not promise volume sending.

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 local-number business texting needs A2P 10DLC registration; toll-free numbers use separate verification. Complete the applicable approval before relying on texting. See Register for A2P 10DLC.

Turning it on

Open the installed sub-account’s HighLevel Settings → Phone System → Additional Settings.
Select Phone Clover SMS as the custom SMS provider and save. Older versions may still display Telnyx SMS.
Return to Conversations and send a test message from an enabled Phone Clover number, then reply from the receiving phone.

Connecting Telnyx inside Phone Clover does not replace this HighLevel provider-selection step. Check each sending path before using it for customer messages; workflow and bulk delivery still need separate verification.

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

Confirm the selected provider in HighLevel, then check Phone Clover’s Settings → Overview → Phone health → Telnyx messaging and Settings → Texting → Business texting registration. A healthy Telnyx badge alone does not prove HighLevel selected Phone Clover as its SMS provider. Test both sending and receiving. See What the settings health badges mean.

What this enables

Once the native provider is active:

Conversations uses your selected SMS provider. Workflow and bulk sending should be tested separately before use; these paths have not yet been fully verified for Phone Clover. 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 selected custom SMS provider in HighLevel’s Phone System settings, then test a message in each direction. The Phone Clover health badges describe the Telnyx connection, not the provider selection in HighLevel.