Improved A2P Rejection Guidance for Chat Widget and Manual Campaigns

TL;DR

HighLevel improved the guidance for A2P rejections within the 'View required fixes' modal. This update provides clearer steps for both Chat Widget and Manual Setup campaigns. Agencies will find it easier to understand and address SMS campaign rejections.

Who this affects

This affects any agency owner or SaaS entrepreneur who registers A2P campaigns. Specifically, it impacts those who encounter rejections for Chat Widget (Quick Setup) campaigns or Manual Setup campaigns. HighLevel has not confirmed who else is affected.

What changed

The 'View required fixes' modal for A2P rejections now provides more specific guidance. The changes are:

• Guidance in the modal was rewritten.
• The guidance now matches how the campaign was registered, whether through Quick Setup (Chat Widget) or Manual Setup.
• Common rejection reasons have separate guidance for Chat Widget (Quick Setup) campaigns.
• Common rejection reasons also have separate guidance for Manual Setup campaigns.
• Each rejection reason explains the issue and lists specific actions to take.
• The system indicates when rejections are caused by platform-generated content, such as the chat widget's consent wording.
• Steps for reasons like privacy policy verification include required statements.
• The system indicates when resubmitting will not help and what needs to change first, such as a business type mismatch. HighLevel has not confirmed any limits, plan gating, or rollout status.

Where to find it

HighLevel has not published the exact location for this improvement. Based on the description, this improved guidance will be found within the 'View required fixes' modal. This modal typically appears when an A2P campaign submission is rejected and needs modifications. This functionality resides within the HighLevel platform's A2P campaign registration section.

How agencies will use this

When an agency submits an A2P campaign for a client, it often faces rejections due to non-compliance with carrier rules. Previously, the reasons for rejection and the steps to fix them could be vague. With this update, if a Chat Widget (Quick Setup) campaign is rejected, the agency can navigate to the 'View required fixes' modal. The system will clearly state, for example, that the privacy policy link is missing a required statement and even provide the exact wording needed. If the rejection is due to platform-generated consent language, the system will highlight this, indicating that the issue is not with agency-provided content. This clarity helps the agency quickly identify the problem, make the specific correction, and resubmit the campaign without guesswork, reducing back-and-forth and activation delays for the client's messaging.

Our take

This is a standard product improvement. It addresses a common pain point for agencies dealing with A2P campaign rejections. The increased clarity will save time and frustration. It is not a major new feature, but it improves the operational efficiency for agencies managing A2P compliance. It matters for anyone actively engaging with A2P campaign registration.