Outbound & SMS Permissions

These registrations get your organization approved to run outbound voice and SMS campaigns through Guava. They're required — you can't make outbound calls or send SMS without them — and several have prerequisite relationships, so the order matters. All registrations are managed from the Guava Compliance page.

Carriers and SMS aggregators require businesses to register before they can send outbound voice or SMS traffic — it's part of how the industry combats spam and fraud. Guava handles the submission and coordination on your behalf; you fill out a form on the Compliance page, and we route it to the right reviewer.

There are four registrations:

• Outbound Dialing Registration — first step; one-time, prerequisite for everything else
• Use Cases — one per business purpose; required for SMS Campaign + Analytics Provider
• SMS Brand Registration — one-time, org-wide; required to send SMS
• SMS Campaign Registration — one per use case; required to send SMS

Outbound Dialing Registration

Outbound Dialing Registration is the first step in the compliance process and a prerequisite for everything else. This is a Know Your Customer (KYC) form that collects your business identity, point of contact, compliance contact, call setup details, and telecom compliance information.

To get started, open the Guava Compliance page and fill out the Outbound Permissions form under General Forms. Once submitted, the form enters a review queue for the Guava team. Upon approval, your organization will be enabled for outbound dialing, and you'll gain access to the rest of the compliance registrations.

The form requires the submitter to have authority to control or manage the company and bind it to agreements. US-based businesses only; a valid EIN is required.

What you'll need to provide:

1. Business Identity: Legal business name, business type, industry, EIN, physical address, and website.
2. Point of Contact: The person authorized to enter into agreements on behalf of the company — name, email, phone, and job title.
3. Compliance Contact: A contact for compliance-related communications (may be the same as the point of contact).
4. Call Setup: The types of calls you plan to make (outbound, inbound, WebRTC), a description of your use cases, your phone number plan, and whether your use case involves PHI or cardholder data.
5. Telecom Compliance: FCC Robocall Mitigation Database (RMD) registration status, TCPA/TSR certification, consent method, Do Not Call Registry validation, and internal DNC list practices.

Use Cases

A Use Case is a named grouping that ties together your campaigns, SMS campaign registration, and analytics provider attestation under a single business purpose. Each use case has a name (e.g., "Collections", "Appointments") and a type selected from a standard list of 45 categories (e.g., Abandoned Cart, Appointment Reminders, Lead Generation, Telehealth, Survey/Research).

Use cases exist because different outbound activities often serve different purposes, and compliance registrations — particularly SMS campaign registration and analytics provider attestation — are scoped per use case. For example, if your organization runs both appointment reminder campaigns and marketing campaigns, those are two separate use cases, each with their own SMS campaign registration and analytics attestation.

To create a use case, go to the Guava Compliance page and click "+ New Use Case" in the Use Cases section. You'll provide a name and select a type. You can then assign your existing campaigns to the use case and submit the SMS Campaign and Analytics Provider forms for it.

SMS Brand Registration

SMS Brand Registration registers your business as an SMS brand with the carrier. This is a one-time, organization-wide registration — you only need to complete it once, regardless of how many campaigns or use cases you have. It's a prerequisite for sending SMS messages through Guava.

To register, go to the Guava Compliance page and fill out the SMS Brand Registration form under General Forms.

What you'll need to provide:

1. Brand Details: Legal company name, DBA/brand name, company type (Public, Private, US Nonprofit, US Government), EIN/Tax ID, and optional alternate identifiers (DUNS, GIIN, LEI).
2. Address: Street address, city, state, and zip code.
3. Company Info: Website, and stock symbol/exchange if publicly traded.
4. Business Contact: First and last name, email, and mobile phone.
5. Support Contact: Support email and phone number.

Once submitted, your brand registration will be forwarded to the carrier for processing. Upon approval, your organization will be assigned a business ID and your phone numbers will be associated with your brand.

SMS Campaign Registration

SMS Campaign Registration is an A2P (Application-to-Person) 10DLC campaign registration, completed once per use case. This registration tells the carrier what kind of SMS messages you'll be sending, how consumers opt in, and what your compliance keyword responses are (e.g., what happens when someone texts STOP or HELP).

To register, go to the Guava Compliance page, find the relevant use case card, and click "SMS Campaign Form."

What you'll need to provide:

1. Campaign Details: Campaign type (from the use case type list), a description of the SMS campaign, how consumers opt in (call-to-action / message flow), CTA URL, terms of service URL, privacy policy URL, and sample messages.
2. Compliance Keyword Responses: Your opt-in keywords and response, opt-out (STOP) response, and help (HELP) response. Each response must include your brand name, campaign description, and support contact info.
3. Usage Disclosures: Whether you use number pooling (50+ numbers), direct lending, embedded links (note: public URL shorteners like bit.ly or tinyurl are not permitted), embedded phone numbers, or age-gated content. You'll also confirm the campaign won't be used for affiliate marketing.
4. Traffic Profile: SMS traffic type (transactional, customer care, marketing, or mixed), associated website, message frequency, and whether the website/domain is displayed in messages.

Once submitted, the registration will be forwarded to the carrier for processing. Upon approval, SMS will be enabled for your organization and your compliance keyword responses (opt-in, opt-out, help) will be configured.

Summary