Skip to main content

Changelog

Follow new updates and improvements to Growably.

Improved A2P Rejection Guidance for Chat Widget and Manual Campaigns

We've rewritten the guidance in the "View required fixes" modal so it matches how you registered your campaign.

What's new:

  • Guidance for your setup: the most common rejection reasons now have separate guidance for campaigns set up through the Chat Widget (Quick Setup) and through Manual Setup, since the fix is in a different place for each.

  • Clearer next steps: each reason explains in plain language what happened, then lists the specific actions to take.

  • Know when it's not on you: some rejections are caused by something the platform generates, like the chat widget's consent wording. We'll tell you and point you to support, so you don't spend a resubmission on something you can't change.

  • Exact wording where carriers require it: for reasons like privacy policy verification, the steps include the required statement.

  • Notice when resubmitting won't help: for reasons like a business type mismatch, we'll tell you what needs to change first.

Previously:

The modal showed the carrier's generic guidance, written for every registration method. Chat Widget users were often asked to fix fields or consent wording they never wrote.

Why it matters:

Guidance that matches your setup helps you fix the right thing the first time and resubmit with confidence, without waiting on support.

ImprovedChat

Chat Widget Spam Protection

Chat Widget now includes built-in spam protection to help prevent bot and high-volume suspicious submissions from impacting your messaging costs and sender reputation.

Spam protection works automatically in the background without adding CAPTCHA, extra form fields, or additional steps for genuine visitors.

Instead of deleting suspicious submissions, HighLevel keeps the contact, tags it for review, and can pause SMS, email, or both based on your selected setting. This ensures potentially legitimate leads are not lost while preventing unnecessary outbound messages to suspicious contacts.

What's New

Automatic spam protection without visitor friction

Spam and suspicious submissions are detected automatically without changing the visitor experience.

There is:

* No CAPTCHA

* No additional form fields

* No extra loading or verification step

* No change to the experience for genuine visitors

Suspicious leads are kept for review

Flagged contacts are not deleted.

They are created normally and tagged with: chat_widget_high_volume_flag

Depending on your configuration, SMS, email, or both can be paused for that contact. This allows your team to review suspicious leads and restore messaging when the submission is legitimate.

Protect your sender reputation

Sending messages to invalid phone numbers and email addresses can generate unnecessary costs, bounces, and delivery issues.

Spam Protection prevents outbound messaging on the selected channels for flagged contacts, helping reduce unnecessary messaging spend and protect SMS and email sender reputation.

Configure protection independently for each widget

Spam Protection is configured at the individual Chat Widget level.

You can choose from four actions:

* Tag Only

* Pause SMS

* Pause Email

* Pause Both

Only the selected channel is affected. Other communication channels and existing DND preferences remain unchanged.

Clear activity history

When messaging is paused by Spam Protection, the contact activity log records the action and identifies the affected channel.

Flagged contacts can also be found by filtering for the chat_widget_high_volume_flag tag.

Safe defaults for existing and new widgets

For existing Chat Widgets, Spam Protection is OFF by default so current behavior does not change unexpectedly.

For newly created Chat Widgets, Spam Protection is ON by default with Pause Both selected.

## How to Enable Spam Protection

  1. Go to Sites > Chat Widget.

  2. Open the Chat Widget you want to configure.

  3. Open Spam Protection in the builder sidebar.

  4. Turn Spam Protection on.

  5. Select the action to take when a suspicious submission is detected.

  6. Save your changes.

To review flagged contacts later, filter your contacts using the chat_widget_high_volume_flag tag.

If you're expecting an unusually large legitimate traffic spike, such as during a major campaign, launch, event, or press announcement, you can temporarily disable Spam Protection for that widget and enable it again afterward.

Why We Built This

A spam attack against a Chat Widget can create hundreds of fake contacts within a short period of time. If automated follow-ups are triggered for those contacts, businesses can end up sending SMS and emails to invalid destinations.

Beyond the unnecessary messaging cost, repeated failures and bounces can negatively affect sender reputation and the deliverability of legitimate campaigns.

Chat Widget Spam Protection helps prevent this automatically while keeping suspicious contacts available for review rather than permanently discarding them.

For security reasons, the specific signals and thresholds used to identify suspicious activity are not published. This helps prevent malicious actors from designing submissions specifically to bypass the protection.

What's Next

We will continue improving Spam Protection with:

* Broader protection coverage

* Better visibility into flagged contacts

* Additional review and management controls

* Ongoing detection improvements based on real-world traffic

image (48)
Screenshot 2026-09-18 at 9
Screenshot 2026-09-18 at 9
NewChat

Chat Widget: Flexible Compliance Notice & Consent Settings

Chat Widget compliance settings are now more flexible, giving businesses greater control over how legal notices and visitor consent are handled.

What’s New?

The previous all-in-one HIPAA compliance setting has been upgraded to a new Compliance notice & consent section.

You can now:

Show a legal notice below the contact form without requiring any visitor action.

Add a consent checkbox with custom wording for explicit opt-ins such as SMS or email marketing consent.

Make consent required or optional depending on your business needs.

Pre-check the consent checkbox when the form loads.

Show clear validation when required consent is missing, with a “Please tick this box to continue.” message.

Track consent in Activity details, including whether consent was given, whether it was required, and the exact consent text shown to the visitor.

How to Use It

Navigate to: Chat Widget → Chat window → Additional options → Compliance notice & consent

From here, you can configure your legal notice, consent checkbox, required/optional behavior, and pre-checked state. The live preview updates as you configure the experience.

Why It Matters

Legal disclosures and explicit marketing consent don't always serve the same purpose. Previously, they were handled through a single setting.

With this update, businesses can independently configure disclosures and consent, making it easier to create the right experience for different compliance requirements while maintaining a clear record of what each lead agreed to.

Availability & Migration

Available to everyone.

Existing widgets remain unchanged until they are opened and saved in the builder.

Existing legal text is automatically carried over to the appropriate field.

Widgets created through A2P registration retain their existing compliance configuration.

New widgets default to:

Legal notice: On

Consent checkbox: On

Required consent: Off

No changes to existing website embed code are required.

image (28)
NewChat

Earlier updates