HighLevel Marketplace onboarding

Install A2P Desk from the HighLevel Marketplace, then run one real client through preflight.

Use this guide when an agency owner, admin, implementer, or snapshot seller wants to install A2P Desk and test the workflow on one real client case before making it part of recurring SMS launch readiness.

Open Marketplace listing Back to home

Last updated: June 8, 2026

Before you install

Pick one client where the A2P work is real enough to expose the evidence gaps your team normally has to chase down manually.

Install from an agency or sub-account context you are authorized to manage.
Use a real agency workspace so the first scan, intake link, evidence upload, and submission pack reflect how your team actually works.
Choose one client case with website, opt-in, privacy policy, terms, sample messages, message flow, and rejection context available for review.
Do not paste passwords, API keys, government documents, card details, or unnecessary client PII into A2P Desk.

What the permissions mean

A2P Desk uses narrow read-only HighLevel Marketplace permissions for location discovery and installation context so agencies can map or import the right client workspace.

locations.readonly lets the app list authorized locations and read basic location details needed for mapping.
marketplace-installer-details.readonly supports installation context and marketplace-assisted setup tracking.
No write scopes are requested for contacts, opportunities, workflows, calendars, payments, SMS sending, or client CRM records.
A2P Desk does not send SMS, submit A2P registrations automatically, alter HighLevel workflows, or bypass provider review.

First client onboarding path

The first install should end in a concrete agency decision: does this workflow reduce blind resubmissions enough to use for future clients?

Open the dashboard, refresh HighLevel locations, then map an existing A2P Desk client or import one authorized location as a draft client.
Add the client's website, opt-in URL, privacy policy URL, terms URL, campaign description, message flow, consent language, and sample messages.
Upload or request evidence such as the opt-in screenshot, policy snapshot, terms page, and the exact rejection phrase when one exists.
Run preflight, review findings, mark lifecycle decisions with reasons, then create a submission pack for agency review.

When to ask for help

Use founder-led preflight when the client is already in a rejection loop or the agency needs a second set of eyes before another paid resubmission.

Route messy active rejections through `/concierge-preflight` after removing unnecessary personal data from notes and evidence.
Use the opt-in proof, privacy/terms URL, SMS privacy language, and TCR-code guides when the blocker is already clear.
Track the exact rejection code, provider wording, and before/after evidence so repeated patterns can improve future scanner coverage.
Preflight workflow support only. Not legal advice. No approval guarantee from A2P Desk, HighLevel, Twilio, TCR, carriers, or any provider.