GoHighLevel Agency Trust Center (A2P Console): Track, Fix and Resubmit A2P 10DLC for Every Sub-Account

If you look after more than a handful of US clients in GoHighLevel, you know how A2P goes. One client is approved, two are stuck in review, one was rejected three weeks ago and nobody noticed, and the only way to find out is to open every sub-account, go to the Trust Center and check. A2P 10DLC registration is a regular part of my work for agencies, and that sub-account by sub-account checking takes a lot of time.

HighLevel's answer, announced on LevelUp Day 2026, is the Agency Trust Center. This guide covers what it is, who can use it, how to work through it step by step, and how to use the rejection reasons it shows to get stuck registrations approved. Every fact about the feature comes from HighLevel's own help article and LevelUp Day post, linked at the bottom.

What the Agency Trust Center is

Until now, A2P registration in HighLevel lived only inside each sub-account, at Settings, Phone System, Trust Center. That still works and is not going away. The Agency Trust Center sits on top of it at agency level and pulls every sub-account's registrations into one place. HighLevel describes it as complementing the sub-account Trust Center, not replacing it.

It has three tabs:

Who it is for (and who cannot use it yet)

• Agencies on HighLevel's $497/month plan. HighLevel's help article says the Agency Trust Center is currently only on this plan. HighLevel's Founder plan page lists the "A2P Console" among the features only available in the Founder plan. If you are on a lower plan, you will not see it, and you carry on using each sub-account's own Trust Center.
• Agency Owners and Agency Admins only. Other agency users and sub-account users do not get access to the agency-level console. If a team member handles A2P for you, check their role before you tell them to look for it.
• Agencies with US clients who text. A2P 10DLC is the US carrier registration for business texts sent from standard 10-digit US numbers. If your clients only text in the UK or other countries, this console is less relevant to you.

For what else is on the $497 plan, see my guide to the GoHighLevel Founder plan.

Before you start

• Check your plan and role. You need the $497/month plan and an Agency Owner or Agency Admin login.
• Know what "fully approved" means. HighLevel only counts a sub-account as Fully Approved when both its Brand and its Campaign are approved or verified. A sub-account with an approved Brand and a pending Campaign is not done yet.
• Keep the sub-account Trust Center handy. For the detailed "View required fixes" breakdown on a rejected Campaign, HighLevel's rejections help article still points to the sub-account at Settings, Phone System, Trust Center, Brands & Campaigns.
• Have the client's real business details ready if you plan to start a registration for them. HighLevel warns that the business name, EIN, address and other identity details must match official records, or the Brand can be rejected.

Step by step: manage A2P for every sub-account from the Agency Trust Center

Step 1: Open the Agency Trust Center

Log in to your HighLevel agency account (Agency View), go to Settings, Phone Integration and open Trust Center (A2P). You will see three tabs: Overview, Brands and Campaigns. If you cannot see it, check that you are on the $497/month plan and logged in as an Agency Owner or Agency Admin.

Step 2: Read the three summary cards

On the Overview tab, check Fully Approved (sub-accounts where both the Brand and Campaign are approved or verified), In Review (with a split of Brands and Campaigns under review) and Rejected (with separate counts for rejected Brands and Campaigns). The counts are per sub-account, not per registration attempt.

Step 3: Set the date range and refresh

Use the Date Range selector at the top right of the Overview, for example Last 30 Days, then click the refresh icon to load the latest figures.

Step 4: Work through the rejection reasons

Look at the Brand Rejection Reasons and Campaign Rejection Reasons sections. Each reason shows how many sub-accounts failed for it. Click the arrow next to a reason, or click a Brand or Campaign rejection count on the Rejected card, to jump to the affected registrations.

Step 5: Fix and resubmit rejected Brands

Open the Brands tab and use the Rejected filter, or search for a sub-account. The table shows the Brand SID, sub-account, status, Brand type, attempts left and the latest rejection reason. Open the Actions menu on a row and, where the status allows it, choose Fix and Resubmit. Check the attempts left before you resubmit.

Step 6: Fix and resubmit rejected Campaigns

Open the Campaigns tab and filter by Rejected. The table shows the messaging service, sub-account, Campaign status, connected Brand, use case and rejection reasons. Use the Actions menu and choose Fix and Resubmit where available. Fix every listed reason first, and if a field such as the use case cannot be edited, you may need a new Campaign.

Step 7: Start a registration for a sub-account

On the Brands tab, click Start registration, choose the sub-account, fill in the business and registration details, review them and submit. The details must match the business's official records. Track progress afterwards on the Brands and Campaigns tabs.

Chat Widget or Self-Serve: what the comparison tells you

The Overview tab has a section called How your sub-accounts are registering. It splits your registrations by how consent is shown to the carriers:

• Chat Widget: consent is collected through HighLevel's website Chat Widget and stored automatically.
• Self-Serve: the business provides its own proof of consent, such as its own opt-in form or website.

For each method you see how many sub-accounts submitted with it and what share were approved, out of those that have had a final decision. HighLevel's help article gives a made-up example to explain the screen: 15 of 22 registered sub-accounts on Chat Widget with a 90% approval rate, and 7 on Self-Serve with 29%. That is an illustration from HighLevel, not real data, but it shows how to read the section. If your own numbers show one method doing much better across your clients, that is worth acting on.

Two cautions from HighLevel's own FAQ: the Chat Widget does not guarantee approval, as every registration still has to meet carrier requirements; and the two methods differ because of how consent is evidenced, so a low Self-Serve rate usually points to weak opt-in evidence rather than the method itself.

Common rejection reasons, and what HighLevel says to fix

The Overview lists the rejection reasons hitting your sub-accounts. HighLevel's help article gives these examples: for Brands, the business name not matching the EIN, opt-in consent not properly evidenced, and a business category not eligible for 10DLC; for Campaigns, a description that does not match the use case, opt-in consent not properly evidenced, and a website that could not be verified.

The fixes below come from HighLevel's A2P Campaign rejections help article. Here are some of the codes listed there.

A simple weekly A2P routine for agencies

This is my own suggestion for using the console, not a HighLevel feature:

1. Monday: open the Overview, set the date range to the last 30 days and refresh. Note the Rejected count for Brands and Campaigns.
2. Click each rejection count and work through the list, worst first. Anything with few attempts left gets checked by a person before resubmitting.
3. Check In Review items that have been sitting for a long time. HighLevel says not to resubmit or create another Campaign while a review is in progress, so this is about chasing information, not pressing buttons.
4. Look at the Chat Widget versus Self-Serve numbers once a month and decide which method you will use for new clients.
5. Keep your own note of what you changed and when. CSV export is not in the first version, so the console will not give you a report to send clients.

Limits and things to watch

• Plan and role only. $497/month plan, Agency Owners and Agency Admins only, per HighLevel's help article.
• No CSV export yet. HighLevel's FAQ says CSV export is not available in the initial version.
• Counts are per sub-account. The summary cards count sub-accounts, not registration attempts, so one sub-account with several failed attempts still shows as one.
• Campaigns need an approved Brand. You cannot create a Campaign before the Brand is approved.
• Fees still apply. The console does not change A2P registration or vetting fees. HighLevel keeps these in its A2P fees article; check it before you tell a client what resubmitting will cost.
• Carriers decide, not HighLevel. HighLevel provides the registration flow, but carriers and their registration partners make the final approval or rejection decision.
• Client data. The console shows every client's business details in one place. Think about who in your team really needs Agency Admin access.

This is one of a long list of LevelUp 2026 releases. See the full list, with the status of each one, in my LevelUp 2026 roundup, and the AI side of the event in my LevelUp Day AI agents and Voice AI post. If you would rather manage sub-accounts by typing plain English instructions, have a look at the GoHighLevel MCP server.