Related Guides: Create a 10DLC Campaign, 10DLC Campaign Tips & Tricks



Overview
This guide will help you navigate the fields needed when registering a 10DLC campaign for your customers. For further details, please refer to our 10DLC and The Campaign Registry overview article.


Use Cases

In most cases your customer's will benefit from the "Low Volume Mixed"  ("LVM") use case. It allows for selecting a mix of up to five sub-use cases, avoiding stricter options that may cause message delivery issues, should any message violate a specialized use cases narrow purpose. Its large messaging allowance permits up to 2,000 outbound messages per day at rate up to 75 messages per minute, which surpasses the usage of an average SMB customer. It also benefits from an easier approval process without needing the extra vetting services, required by some other use cases. Financially, it's also among the least expensive options available.

These features make the LVM use case an easy choice for most customers and is the default configuration when creating a campaign in the RingOS portal.

Special Use Cases are available. However, the TCR sometimes treats these as sensitive or critical in nature and often requires additional Vetting or pre/post registration approval by the Mobile Network Operators ("MNO's"). Any additional requirements may vary per MNO. Please contact our Partner Success Team for assistance with any other use cases.



Low Volume Mixed - Sub Use Case Options:
These options are available for all “Verified” brands without needing extra vetting or approval.

1. 2FA: Authentication, verification, or one-time passcode.
2. Customer Care: Account management and customer support interactions.
3. Fraud Alert Messaging: Alerts regarding potential fraudulent activity.
4. Marketing: Promotional or marketing content communication.
5. Public Service Announcement: Informational messages to raise awareness about important issues.
6. Delivery Notifications: Updates on the status of product or service deliveries.
7. Polling and Voting: Surveys and non-political polling/voting campaigns.
8. Security Alert: Notifications about compromised system security and necessary actions.
9. Higher Education: Messaging on behalf of colleges, universities, and educational institutions.

Campaign Description

The campaign description should clearly state the campaign's objectives and usage, answering:

• Who you are
• Who you want to reach
• Why you are sending messages

A well-defined campaign description helps ensure clarity and compliance during the registration process.

Campaign Sample Message

Provide sample messages that are specific to the campaign and represent different scenarios. Ensure that the messages reflect the selected sub-use cases. These samples should illustrate typical interactions to give a clear picture of the campaign’s content.

Call-to-Action / Message Flow

A Call-to-Action (CTA) invites recipients to opt-in to a messaging campaign, explaining how consent is obtained. If phone numbers are collected for opt-in, detail how they were acquired. Be precise and descriptive.

The CTA should make it clear how users consent to receive messages, ensuring transparency and compliance.

Campaign and Content Attributes

During registration, you must confirm whether the campaign includes specific attributes by answering ‘Yes’ or ‘No’. These fields are final and cannot be changed once submitted.

• Direct Lending or Loan Arrangement: Check ‘YES’ if the campaign involves loans or financing, including third-party arrangements, such as auto dealerships offering financing.
  • Examples include car, truck, or boat dealerships arranging financing or loans.
• Age-Gated Content: Indicate if the campaign includes content restricted by age as defined by Carrier and CTIA guidelines.

Terms & Conditions:

Confirm that the campaign will not be used for affiliate marketing, adhering to TCR’s strict anti-spam policies.