Send bulk SMS

Sending a text to a list or segment of contacts at once (a bulk send) works the same way in HighLevel whether Phone Clover is your SMS provider or not. What Phone Clover changes is which carrier those messages travel over, and what happens if some of them fail.

Before you start

• Who can do this: an admin or anyone with permission to run bulk sends in HighLevel.
• What it needs: Phone Clover switched on as your sub-account’s native SMS provider, and A2P 10DLC registration on the sending number. See Turn on Telnyx as your native SMS provider and Register for A2P 10DLC.

Sending a bulk text

Build and send your bulk message from HighLevel’s own bulk-send or workflow tools, targeting the list or segment you want. Once the native provider is on, the send routes through your Telnyx number automatically, using your sub-account’s default number unless the send is tied to a specific number.

Plan around carrier sending limits

Carriers apply their own throughput and content rules to every text sender, regardless of provider, and a bulk send is exactly the kind of traffic that can run into them. Before a large send:

• Confirm A2P 10DLC registration is complete, not just started. An in-progress registration can still see messages filtered at volume even if occasional one-off texts go through fine. See Register for A2P 10DLC.
• Check number health first. A number already showing signs of carrier flagging is more likely to have a bulk send filtered outright. See Number health radar.
• Expect some messages to fail even on a healthy, registered number. Landline numbers in your list, contacts who have opted out, and normal carrier filtering all reduce delivery below 100% on any bulk send, with any provider.

Warning: “Sending limits” is one of the standard failure reasons Phone Clover can show you after a send. Do not assume a filtered message means something is broken; it may simply mean the send tripped a carrier’s rate rule. Spacing large sends out, or breaking one very large list into smaller batches, reduces this.

Checking results after a send

Use Settings → Texting → Failed texts to see which messages in a bulk send did not deliver and why, in plain language instead of a raw carrier code. See Why texts fail and what the reasons mean. Two toggles there can help with recurring bulk sends:

• Retry from another number: automatically resends a failed message from another number you own.
• Skip landlines: checks a number before texting it, to avoid a guaranteed failure on a landline that cannot receive texts at all.

Troubleshooting

A large portion of the send failed immediately. This usually points to an incomplete A2P 10DLC registration or a number that carriers have already flagged. Check What the settings health badges mean and Number health radar before resending.

The send worked for most contacts but failed for a specific segment. Check Why texts fail and what the reasons mean for the failed contacts specifically; a shared cause (for example, a batch of landline numbers, or contacts who opted out together) is common.

I need to send to the same list again after fixing a problem. Turn on Retry from another number in Settings → Texting → Failed texts before resending, so a temporary carrier issue on one number does not repeat the same failure.

Related

• Why texts fail and what the reasons mean
• Number health radar
• Register for A2P 10DLC