Send a text from Conversations
Texting from HighLevel's Conversations screen works as usual once Phone Clover is your SMS provider, with delivery detail Phone Clover adds behind the scenes.
For everyone · Updated Sep 23, 2026
All guides
If your admin has turned on Phone Clover as your native SMS provider, texting from HighLevel’s Conversations screen already works the way you expect. This page covers what actually happens behind that familiar screen, and what to check if a text does not go through.
Before you start
- Who can do this: any rep with access to Conversations.
- What it needs: Phone Clover must be switched on as your sub-account’s native SMS provider. See Turn on Telnyx as your native SMS provider.
Sending a text
Open a contact’s conversation in HighLevel, type your message in the compose box, and send it the same way you always have. Nothing about the Conversations interface itself changes. What changes is which carrier the message actually travels over: with Phone Clover as the provider, it goes out through your connected Telnyx number instead of HighLevel’s default carrier.
Replies land in the same thread, exactly as they always have.
Which number it sends from
Your sub-account’s default number sends the message unless a specific number has been assigned to that contact or conversation. Admins set the default number and manage which numbers are connected from Settings → Numbers. See Set up your first number.
What Phone Clover adds behind the scenes
Because Phone Clover owns the send path once it is your provider, a few things work better than with a generic carrier:
- Spam filtering on the way in. Inbound texts are checked against allow and block lists, country rules, and content and velocity checks before they land in your Conversations inbox. See SMS firewall: block and allow lists.
- Real delivery reasons. If an outbound text fails, Phone Clover can show a plain-English reason instead of a generic error, since it can see the actual carrier response. See Why texts fail and what the reasons mean.
- Number health awareness. If a number gets flagged by carriers, Phone Clover can warn you or move texting to a healthier number automatically, if your admin has turned that on. See Number health radar.
Business texting registration still applies
US business texting requires A2P 10DLC registration on the sending number, regardless of which provider sends the message. If your business is not registered yet, expect carriers to filter or delay messages, especially at higher volume. See Register for A2P 10DLC.
Troubleshooting
My text shows as sent in Conversations but the customer says they never got it. Check Why texts fail and what the reasons mean for the specific reason. Common causes include the recipient’s number being a landline, the message being filtered by a carrier, or the recipient having opted out previously.
Texts are going out, but from a number the customer doesn’t recognize. Check which number is set as default in Settings → Numbers, and whether this specific contact’s conversation is tied to a different number. See Set up your first number.
I can’t tell if Phone Clover is actually sending this text or if it’s still on HighLevel’s default carrier. Ask your admin to confirm the native SMS provider setting for your sub-account. See Turn on Telnyx as your native SMS provider and What the settings health badges mean.
A customer’s replies aren’t showing up. Confirm the number they are replying to is the same number the original text was sent from, and check Settings → Texting → Failed texts for any inbound delivery problems.