A2P DeskEvidence-grade A2P preflight

Product docs

A2P Desk getting-started guide.

A practical guide for agencies using A2P Desk to prepare client evidence, run preflight checks, manage rejection context, and export submission-ready workflow materials.

Open dashboardBack to home

1. Create a workspace

  • Start from the dashboard, create an agency workspace, and activate the account from the email link.
  • Use the workspace for agency-side review. Client-facing intake links are separate and should only be shared with the intended client.
  • Keep authentication emails, billing emails, and product follow-ups in a monitored inbox.

2. Add a client campaign

  • Enter the client legal/business name, DBA context, website, opt-in URL, privacy policy URL, terms URL, use case, message flow, and sample messages.
  • When acting as an agency, preserve the correct direct-customer or reseller/partner identity context.
  • Do not store unnecessary tax documents or sensitive client files unless they are needed for the evidence workflow.

3. Collect intake and evidence

  • Create an intake link when a client needs to provide URLs, consent copy, screenshots, or supporting files.
  • Review submitted intake before running preflight checks.
  • Upload opt-in screenshots, policy snapshots, terms pages, and related proof only when you have permission to process the evidence.

4. Run preflight

  • Run the scanner to check missing privacy and terms URLs, opt-in evidence, SMS non-sharing language, sample-message issues, restricted-content risk, and other known blockers.
  • Treat findings as workflow support, not final legal or carrier advice.
  • Use lifecycle status and reason fields to mark fixed, ignored, or accepted-risk findings with agency context.

5. Export packs and reports

  • Create a submission pack after evidence has been reviewed and the latest scan reflects the current client state.
  • Use the HighLevel submission handoff inside the pack to paste campaign description, message flow, opt-in disclosure, URLs, sample messages, business identity, and reseller context into the current HighLevel form.
  • Download the PDF or copy reviewer notes into the provider workflow after agency review.
  • Enable, revoke, or regenerate public report links when sharing readiness status with a client.

6. Billing and integrations

  • Use `/managed-a2p-desk` for the $500/mo Managed A2P Desk and $499 Rescue Review offer details. Managed and rescue payments are manually confirmed by Stripe invoice or payment link before work starts.
  • The free scanner is for light validation. Starter and credit-pack workflows unlock higher limits through Stripe checkout.
  • HighLevel location sync and client import are designed for agency workflows once the provider app is authorized.
  • Use `/highlevel-marketplace-install-onboarding` when installing from the HighLevel Marketplace and running the first real client through preflight.
  • Use `/highlevel-a2p-partner-client-onboarding` when a HighLevel implementation partner, SaaS agency, or operations team needs a first-client workflow for evidence review and handoff notes.
  • Use `/highlevel-a2p-business-identity-reseller-context` when an agency needs to keep client brand, direct-customer or reseller context, website, authorized contact, and opt-in evidence aligned.
  • Use `/highlevel-a2p-ein-tax-id-mismatch` when legal name, EIN or tax ID, CP 575 or 147C records, DBA, address, representative, business email, or new-EIN timing needs review.
  • A2P Desk does not submit registrations on your behalf unless a managed or rescue service is separately agreed.

7. Trust and data requests

  • Use the dashboard Trust & Data section to create tracked access, export, correction, deletion, or security requests.
  • Do not include passwords, API keys, card numbers, or unnecessary client PII in trust-request details.
  • Deletion requests are reviewed before destructive action so billing, audit, fraud-prevention, and security retention needs are handled deliberately.

8. TCR rejection-code guides

  • Use `/a2p-rejection-reason-decoder` when a provider or carrier rejection reason needs a quick code-to-next-step triage pass.
  • Use `/a2p-sample-message-checker` when sample messages need a quick brand, placeholder, link, opt-out, restricted-content, and use-case alignment pass.
  • Use `/a2p-privacy-terms-url-requirements` for the privacy policy and terms URL checklist tied to new Twilio API campaign submissions after June 30, 2026.
  • Use `/highlevel-a2p-campaign-description-examples` when campaign descriptions, message flows, consent language, and sample messages need to tell the same HighLevel A2P story.
  • Use `/highlevel-a2p-business-identity-reseller-context` when business identity, DBA, reseller/partner context, authorized contact, and client evidence need review.
  • Use `/highlevel-a2p-ein-tax-id-mismatch` when brand vetting appears blocked by legal-name, EIN, tax-ID, DBA, address, representative, business-email, or newly issued EIN mismatch.
  • Use `/highlevel-a2p-multi-account-opt-in-rejection-workflow` when many client accounts are stuck on similar opt-in, CTA, privacy, terms, sample-message, or consent-evidence blockers.
  • Use `/highlevel-a2p-appointment-reminder-sample-messages` when appointment confirmations, reminders, reschedules, STOP/HELP language, and transactional sample-message boundaries need review.
  • Use `/highlevel-a2p-customer-care-sample-messages` when support follow-ups, account help, status updates, STOP/HELP language, and mixed-use boundaries need review.
  • Use `/highlevel-a2p-lead-follow-up-sample-messages` when new-lead replies, estimate follow-ups, consultation follow-ups, STOP/HELP language, marketing boundaries, and consent/use-case alignment need review.
  • Use `/highlevel-a2p-missed-call-text-back-30909` when a missed-call text-back campaign is rejected because CTA, message-flow, or consent-path evidence cannot be verified.
  • Use `/highlevel-ai-a2p-validation-agency-workflow` when comparing HighLevel's native AI validation with the agency-side evidence workflow around it.
  • Use `/highlevel-a2p-opt-in-proof-rejected` when HighLevel opt-in evidence, consent checkboxes, policy links, or sample messages need a pre-submission review.
  • Use `/highlevel-a2p-opt-in-checkbox-language-examples` when checkbox copy, optional consent, marketing/non-marketing separation, privacy and terms links, and STOP/HELP disclosures need review.
  • Use `/sms-privacy-policy-non-sharing-language` when client privacy policy copy creates mobile-data sharing or SMS disclosure concerns.
  • Use `/twilio-a2p-errors-30933-30934` when a Twilio API-style campaign path is missing privacy policy or terms URL fields.
  • Use the TCR 30911 guide at `/tcr-errors/30911` when campaign descriptions, message flows, or sample messages look duplicated.
  • Use the TCR 30913 guide at `/tcr-errors/30913` for bundled marketing-consent cleanup before resubmission.
  • Use the TCR 30914 guide at `/tcr-errors/30914` for business identity, DBA, website, and brand-name mismatch review.
  • Use the TCR 30919 guide at `/tcr-errors/30919` for website, opt-in, privacy, terms, and SMS program evidence gaps.
  • Use the TCR 30940 guide at `/tcr-errors/30940` for cannabis/CBD content that usually needs stop-or-rescope handling.
  • Use the TCR 30960 guide at `/tcr-errors/30960` for phishing-like account, credential, or urgent-login campaign risk.
  • Treat the guides as source-backed workflow support only, not legal advice or an approval guarantee.