August 19, 2026. HighLevel changed the A2P campaign registration flow on August 18. Campaign registration now opens straight into Chat Widget Setup as soon as brand registration ends, with no path choice presented up front. For agencies that collect SMS opt in through a website form, a paper form or verbally, that default is describing a consent mechanism they do not operate, and A2P registration is the one workflow where the answer you give is a declaration rather than a preference.
What HighLevel changed
- Campaign registration now opens in the chat widget flow, with the Chat Widget Setup screen appearing immediately after the brand flow ends. There is no path choice to make first.
- Manual Setup still exists. A Switch to manual setup link sits below the first screen for anyone collecting consent through an existing website form, a paper form, a lead form, a QR code, a kiosk or verbal consent.
- Progress is saved, and a confirmation dialog explains what changes on the manual path before you commit to it.
- If you switch to Manual Setup and change your mind, a callout in the left step panel of the Campaign details screen takes you back.
- Separately, on August 19 HighLevel shipped sub-account subscription syncing for SaaS Mode, so customer subscription details inside a sub-account now update automatically on upgrade or downgrade.
The default is an answer, not a shortcut
A2P 10DLC campaign vetting asks how you obtain consent, and carriers check that the described mechanism matches what a subscriber would actually encounter. Registering through the chat widget path is now the fastest route through the flow and the one that assembles the least evidence, which is precisely why it will get accepted by inertia in accounts where the chat widget is switched off or never used.
The exposure is not theoretical. A campaign approved against a consent mechanism you do not run is a campaign whose supporting evidence does not exist if anyone asks for it, and the consequences of an A2P mismatch land as message filtering and campaign suspension rather than as a notice. HighLevel's own list of alternatives is the useful part here, because it doubles as a checklist. If your opt in lives on a website form, that form needs visible consent language and a stored submission record. If it is verbal, you need a call recording or a logged note. If it is a QR code or kiosk, you need the screen the person saw.
What it means for operators
The fix is cheap because HighLevel made switching cheap. Before registering anything new, decide where the opt in actually happens for that sub-account, then take the manual path deliberately if it is anywhere other than the chat widget. Progress is preserved either way, so there is no operational reason to accept a default that does not describe your business. For agencies registering campaigns across many client accounts, this is worth writing into the onboarding runbook now, because the change alters what a new team member sees on screen and defaults are what get clicked when a process is undocumented. That is the same discipline we apply when we build GoHighLevel systems for agencies.
The SaaS Mode subscription sync carries its own operator note that is easy to miss. HighLevel states the update applies to upgrades and downgrades made going forward, and that subscriptions already out of sync before the change will only be corrected the next time that customer upgrades or downgrades. So the fix does not clean your existing data. Any sub-account customer sitting on a mismatched plan today keeps receiving invoices showing the wrong product, price and tax until they happen to change plan, which for a stable customer could be never. If you run SaaS Mode at any scale, audit current subscriptions against plan records manually rather than assuming yesterday's release repaired the backlog, and treat a mismatched invoice as a churn risk in a client acquisition system you are asking clients to trust with billing.
Frequently Asked Questions
Campaign registration now opens directly in Chat Widget Setup once brand registration finishes, instead of asking you to choose a registration path first. Manual Setup remains available through a Switch to manual setup link below the first screen, progress is saved when you switch, and a confirmation dialog explains what changes before you commit.
Use whichever describes how you actually collect consent. If subscribers opt in through the chat widget, the new default is correct and faster. If your opt in happens on an existing website form, a lead form, a paper form, a QR code, a kiosk or verbally, take the manual path, because A2P registration is a declaration about your consent mechanism rather than a workflow preference.
Carriers vet A2P 10DLC campaigns against the consent flow you describe, and expect it to match what a subscriber would encounter. A campaign approved against a mechanism you do not operate has no supporting evidence if it is ever questioned, and A2P problems typically surface as message filtering or campaign suspension rather than as a warning you can respond to.
No. HighLevel states the update applies to upgrades and downgrades made going forward, and that subscriptions already out of sync will only be corrected the next time that customer upgrades or downgrades. A stable customer on a mismatched plan will keep receiving invoices with the wrong product, price and tax indefinitely, so existing records need a manual audit.