HighLevel's Pre-Built A2P Chat Widget flow now supports businesses that send both promotional and informational SMS. The new Mixed message type automatically assigns the Low Volume Mixed Campaign use case and generates a widget with separate consent choices for each messaging category. This guide explains what changed, how the dual-consent experience works, and how to select Mixed during Campaign registration.

Choose Mixed only when your messaging program genuinely includes both promotional and informational/non-marketing messages. Your Campaign use case, description, sample messages, consent flow, and live messaging should remain aligned.

What is Mixed Use-Case Support for Chat Widget Flow?

Mixed use-case support adds a Mixed message type to HighLevel's Pre-Built A2P Chat Widget registration flow. It is designed for a single messaging program that needs to send both marketing/promotional and transactional or informational messages.

Previously, businesses that needed both message categories could not use the Pre-Built Chat Widget path for that scenario and had to use a more manual registration experience. Mixed support brings this use case into the guided Widget-First flow.

When Mixed is selected, HighLevel automatically sets the Campaign use case to Low Volume Mixed and generates a Chat Widget with independent consent choices for marketing and informational messaging.

Key Benefits of Mixed Use-Case Support

Mixed support extends the guided Widget-First registration experience to messaging programs that combine promotional and informational communication. This simplifies configuration while keeping consent categories clearly separated.

• One Guided Flow: Register a mixed messaging program through the Pre-Built Chat Widget experience.
• Separate Consent: Collect marketing and informational/non-marketing permission independently through the same widget.
• Automatic Use Case Assignment: Selecting Mixed automatically sets the Campaign use case to Low Volume Mixed.
• Active Opt-In: Neither consent checkbox is pre-selected, so contacts actively choose the communication they agree to receive.
• Protected Compliance Content: Required disclosures and compliance-sensitive fields remain system-controlled and locked.
• Fewer Manual Configuration Errors: The guided setup reduces the number of compliance elements that must be entered manually.

How the Mixed Message Type Works

The message type describes the communication your Campaign is designed to send. Mixed should be selected when the same messaging program genuinely combines promotional content with transactional or informational communication.

The Chat Widget flow now includes:

• Marketing / Promotional — sales, offers, discounts, newsletters, and similar promotional communication.
• Transactional / Non-Marketing — appointment reminders, order confirmations, service updates, and similar informational communication.
• Mixed — one messaging program that includes both categories.

Marketing and Informational Consent in the Mixed Widget

The Mixed Chat Widget separates marketing consent from informational consent so contacts can make a clear, active choice about the messages they want to receive. This helps align future communication with the permission the contact actually provided.

The generated widget includes:

• One consent checkbox for informational/transactional messages.
• One consent checkbox for marketing/promotional messages.
• A separate disclosure block associated with each consent option.
• No pre-selected consent checkboxes.

A contact can choose informational messaging only, marketing messaging only, or both. Your outbound messaging should respect the individual consent selections stored for that contact.

System-Controlled Compliance Content

The Pre-Built A2P Chat Widget keeps compliance-sensitive content controlled by HighLevel so the live opt-in experience remains aligned with the Campaign submitted for review. Mixed widgets follow the same protected structure as other Widget-First Campaigns.

System-controlled elements include required content such as:

• Consent disclosure language
• STOP and HELP information
• Message-frequency notices
• Message and data rate disclosures
• Required consent checkboxes
• Other compliance-sensitive fields generated by the registration flow

These required elements cannot be edited or removed. Supported appearance settings can still be adjusted where available.

Important Compliance Considerations

The generated Mixed widget simplifies consent configuration, but Campaign approval still depends on the complete registration accurately representing the business, messaging purpose, consent method, and messages recipients will receive.

• Match the real messaging program: Select Mixed only when both promotional and informational communication will actually be sent.
• Keep samples aligned: Sample messages should reflect the types of communication included in the Mixed Campaign.
• Respect consent boundaries: Marketing and informational consent are independent choices.
• Do not modify locked disclosures: Required compliance content generated by the Pre-Built flow is intentionally protected.
• Keep the submitted page accessible: The Chat Widget must be live and publicly viewable on the page provided during registration.
• Avoid competing SMS opt-ins on the submitted page: The Pre-Built Chat Widget should be the only form on that submitted page collecting SMS consent.
• Maintain website compliance: Ensure required Privacy Policy, Terms & Conditions, and business information are available before submission.

How To Setup Mixed Use-Case Support for Chat Widget Flow

Mixed uses the existing Pre-Built A2P Chat Widget registration workflow, with the new message-type selection determining the Campaign classification and dual-consent widget structure. Complete the Mixed-specific steps below, then continue through the standard Widget-First registration process.

Step 1: Open Campaign Registration

Campaign registration is managed from the Trust Center after the applicable A2P Brand requirements have been completed.

1. Open the applicable sub-account.
2. Go to Settings → Phone System → Trust Center.
3. Continue to A2P Campaign registration.
4. Use the Chat Widget Setup flow.

Step 2: Select Mixed

Selecting Mixed tells the registration flow that the Campaign will include both promotional and informational messaging. HighLevel then assigns the corresponding Low Volume Mixed use case automatically.

1. Continue to the Messaging Use Case step.
2. Select Mixed.
3. Confirm the Campaign Use Case is automatically set to Low Volume Mixed.
4. Continue through the guided Campaign questions.

Step 3: Review the Generated Mixed Chat Widget

The widget preview confirms that the required dual-consent structure has been generated before the widget is installed on the submitted website page.

Verify that the generated widget includes:

• A separate informational/transactional consent checkbox
• A separate marketing/promotional consent checkbox
• Disclosure language for each consent type
• No pre-selected consent choices

Step 4: Complete the Remaining Widget-First Setup

The Mixed option changes the messaging classification and consent structure, but widget installation, website review, Campaign submission, and status monitoring continue through the established Pre-Built A2P workflow.

1. Review the generated widget.
2. Apply any permitted appearance customizations.
3. Install the Chat Widget on the submitted website page.
4. Confirm the submitted page and website meet the applicable compliance requirements.
5. Review the Campaign details and sample messages.
6. Correct any issues identified before submission.
7. Submit the Campaign and monitor its status in the Trust Center.

Frequently Asked Questions

Related Articles