Sender ID Verification reference#
This reference describes the fields and values used for Sender ID Verifications in the DIDWW User Panel. The fields shown during creation and on the verification details page depend on the verification type, destination, and status.
General#
The following fields and values apply to all Sender ID Verifications.
Filters#
Filter |
Filter condition |
Description |
|---|---|---|
Name |
Contains text input |
Filters by verification friendly name. |
Sender ID |
Contains text input |
Filters by Sender ID. |
Country |
Searchable single-select filter |
Filters by target country. |
Searchable single-select filter |
Filters by verification status. |
|
Searchable single-select filter |
Filters by Sender ID Verification type. |
|
SMS Trunk |
Searchable single-select filter |
Filters by assigned outbound SMS trunk or verifications without an assigned SMS trunk. |
Identity |
Searchable single-select filter |
Filters by assigned business identity. |
Address |
Searchable single-select filter |
Filters by assigned business address. |
Filter conditions#
Filter condition |
Description |
|---|---|
Contains text input |
Matches values that contain the entered text. |
Searchable single-select filter |
Allows one value to be selected from a searchable list. |
Sender ID Verification fields#
Field |
Description |
|---|---|
Friendly name |
The account-level name used to identify the verification. |
Reference ID |
The short reference shown below the friendly name on the Verifications page. |
Campaign ID |
The unique UUID assigned to the verification and shown on its details
page. In the API, this value is used as |
The current verification status. |
|
Reject reason |
The reason changes are required. Note This field is shown when the verification status is Changes Required. |
Reject comment |
Additional information about the changes required for the verification. Note This field is shown when the verification status is Changes Required. |
The Sender ID Verification type. |
|
Target countries |
The destination countries covered by the verification. |
SMS Trunk |
The outbound SMS trunk associated with the verification. When no SMS trunk is assigned, the Verifications page shows SMS: none and the verification details page shows a dash. |
Identity (Business) |
The business identity assigned to the verification. |
Address |
The business address assigned to the verification. |
Sender IDs |
The Sender IDs covered by the verification. For Carrier verifications,
this is the immutable, system-generated value in the |
Next billing price |
The next verification charge. This field is shown before an approved verification has a renewal price. |
Renew price |
The recurring price for an active verification. |
Renew date |
The next scheduled renewal date. A dash is shown when no renewal date is scheduled. |
Order ref |
The order reference associated with an active verification, shown as a link to the order. |
Verification type values#
Type |
Description |
|---|---|
Alphanumeric |
Verifies a Sender ID containing letters and numbers. |
Long-code |
Verifies one or more active Long-code DID numbers for A2P SMS. |
Toll-Free |
Verifies one or more active US Toll-Free DID numbers for A2P SMS. |
Carrier (Dynamic) |
Verifies messaging traffic for a supported country. The recipient-facing Sender ID is assigned dynamically by the destination carrier. DIDWW also generates an immutable Sender ID for submitting traffic. |
Status values#
Status |
Description |
|---|---|
New |
The verification has been created, but its review has not started. |
In Process |
The submitted verification is being reviewed. |
Active |
The verification is approved and can be used for the approved business, destination countries, and messaging purpose. |
Changes Required |
The verification requires changes or additional information before review can continue. |
Pending Closure |
Closure has been requested and is being processed. |
Closed |
The verification is closed and can no longer be used to send messages. |
Use case type values#
The use case type identifies the general purpose of the messages. Available values may depend on the verification type and destination country.
For US 10DLC registration, use cases are grouped into standard and special use cases.
Select from the following standard use cases. These are common message categories that typically do not require additional MNO vetting:
Value |
Description |
|---|---|
2FA (OTP) |
Authentication and one-time passcodes. |
Account Notification |
Account updates, billing notices, and password reset messages. |
Customer Care |
Customer service and support messages. |
Delivery Notification |
Notifications about delivery status. |
Fraud Alert Messaging |
Fraud or suspicious activity alerts. |
Higher Education |
Messages from colleges, universities, and other educational institutions. |
Low Volume Mixed |
Low-volume messages that cover more than one use case. |
Machine to Machine (M2M) |
Automated communication between devices or systems without a human recipient. |
Marketing |
Promotional and marketing content. |
Mixed |
Messages that cover more than one standard use case. |
Polling and Voting |
Interactive campaigns such as polls or surveys. |
Public Service Announcement |
Government or civic alerts. |
Security Alert |
Alerts for system or user security. |
Special Use Cases are sensitive and may require pre/post-registration approval by mobile network operators (MNOs). Requirements vary depending on the carrier.
Value |
Description |
|---|---|
Charity |
Non-profit organizations sending donation-related messages. |
Emergency |
Critical public safety or health notifications. |
Social |
Messages from social platforms or apps. |
Alphanumeric verification#
An Alphanumeric Sender ID Verification registers a Sender ID containing letters and numbers for the selected target countries. The information requested during creation can vary according to the selected countries and their identity requirements.
Verification setup fields#
These fields are shown in the General step when creating an Alphanumeric Sender ID Verification.
Field |
Description |
|---|---|
Friendly name |
The account-level name used to identify the verification. |
Target countries |
A predefined country group for which the Sender ID is being verified. Selecting any country in a group selects the entire group; countries cannot be added or removed individually, and groups cannot be combined. Pricing and Identity Requirements apply once to the whole group. |
Sender ID |
The Alphanumeric Sender ID being verified. The value must contain 2 to
11 characters and can use |
Identity (Business) |
The business identity assigned to the verification. |
Address |
The business address assigned to the verification. |
Verification details fields#
These fields are shown in the Verification details step when creating an Alphanumeric Sender ID Verification.
Field |
Description |
|---|---|
Legal Company Name |
The legal name of the business that will use the Sender ID. |
Website |
The website associated with the business and messaging use case. |
The category that best describes the messages sent with the Sender ID. |
|
Campaign description |
A specific description of the messaging purpose and content. |
How will consumers opt in? |
A description of the complete consumer opt-in flow or the script used by an agent to obtain consent. |
Sample content messages #1 |
A representative example of the messages that will be sent. |
Sample content messages #2 |
A second representative example of the messages that will be sent. |
Long-code verification#
A Long-code Sender ID Verification registers eligible DID numbers for A2P SMS in the selected target countries. An active eligible DID number is required in each selected country.
Verification setup fields#
These fields are shown in the General step when creating a Long-code Sender ID Verification.
Field |
Description |
|---|---|
Friendly name |
The account-level name used to identify the verification. |
Target countries |
The destinations for which the Sender IDs are being verified. |
Identity (Business) |
The business identity assigned to the verification. |
Address |
The business address assigned to the verification. |
Sender ID selection fields#
Field |
Description |
|---|---|
Available source numbers |
Active DID numbers that support Outbound A2P SMS, are compatible with the selected business identity, and are not assigned to another Sender ID Verification. |
Allowed source addresses |
The DID numbers selected for this verification. |
Standard verification details fields#
These fields are shown in the Verification details step when the selected target country does not require a country-specific form.
Field |
Description |
|---|---|
Legal Company Name |
The legal name of the business that will use the Sender IDs. |
Website |
The website associated with the business and messaging use case. |
The category that best describes the messages sent with the Sender IDs. |
|
Campaign description |
A specific description of the messaging purpose and content. |
How will consumers opt in? |
A description of the complete consumer opt-in flow or the script used by an agent to obtain consent. |
Sample content messages #1 |
A representative example of the messages that will be sent. |
Sample content messages #2 |
A second representative example of the messages that will be sent. |
United States 10DLC verification details fields#
These fields are shown in the Verification details step when United States is selected as the target country. They collect the business and campaign information required for US A2P 10DLC registration.
Field |
Example |
Description |
|---|---|---|
Legal Company Name |
|
Enter the full legal name of the company. |
DBA (Doing Business As) or Brand Name |
|
Enter the brand name if it differs from the legal name. |
Business entity type |
|
Choose the legal structure of the entity (e.g., Private Company, Charity/Non-profit Organization, Publicly Traded Company). |
Stock symbol (if applicable) |
|
If the company is publicly listed, provide the stock ticker symbol. |
Stock exchange (if applicable) |
|
If the company is publicly listed, provide the stock exchange. |
Vertical type |
|
Select the business category that best describes your organization (e.g., Retail, Financial Services, Healthcare). |
Website |
|
Enter the business website. All links must include the full URL starting
with |
|
Account status updates, password resets. |
|
Campaign description |
Billing Notifications |
Provide a concise summary of the campaign. This should outline the campaign’s primary objectives, the type of message content that will be sent, and the intended target audience. |
How will customers opt in? |
Through my website, Through my app, Verbal agreement, or Physical form |
Select one or more methods used to obtain consent. |
Provide screenshots or scans of the opt-in form |
|
Upload supporting files when Through my app or Physical form is selected. Multiple files can be attached. |
Detailed opt-in flow description |
Checkout Page Consent |
Describe each step of the opt-in process or provide the exact script used by an agent to obtain consent. Include the channel, wording, and confirmation step. |
I confirm that my opt-in flow requires mandatory, manual user confirmation to receive messages based on the campaign and allows users to freely opt out. |
Selected |
This confirmation is required before the verification can be submitted. |
Opt-In Keywords |
|
Specify acceptable keywords. |
Opt-In Message |
|
Include an acknowledgement that the user accepted an invitation, the brand name, message frequency disclosure, the standard Message and Data Rates May Apply disclaimer, and STOP and HELP instructions. |
Opt-Out Keywords |
|
Common unsubscribe terms that subscribers can use to leave the campaign at any time. |
Opt-Out Message |
|
Include the brand name, acknowledgement of the opt-out, and confirmation that no further messages will be sent. |
Help Keywords |
|
Standard terms that subscribers can use to receive assistance. |
Help Message |
|
Include the brand name, support contact details, and a statement that standard messaging rates may apply. |
Sample content messages #1 |
DIDWW: |
Provide an example that reflects the type of SMS content your campaign will send. The message must include the brand name, representative message content, and opt-out and help instructions. |
Sample content messages #2 |
DIDWW Alert: |
Provide a second example that reflects the type of SMS content your campaign will send. The message must include the brand name, representative message content, and opt-out and help instructions. |
URLs included in messages |
|
List the URLs included in SMS content. All URLs must include the full URL
starting with |
Phone numbers included in messages |
|
List the clickable or static phone numbers included in SMS content. |
Link to privacy policy |
|
Provide a direct URL to the privacy policy. The privacy policy must explicitly state that subscriber data will not be sold or shared with third parties. |
Link to Terms and conditions |
|
Provide a direct URL to the terms and conditions. The link must include
the full URL starting with |
Note
For US A2P 10DLC registration, the business or brand name must appear in the opt-in, opt-out, help, and sample messages. The opt-in message must also disclose the message frequency, applicable message and data rates, and HELP and STOP instructions.
Toll-Free verification#
A Toll-Free Sender ID Verification registers an eligible US Toll-Free DID number for A2P SMS. An active US Toll-Free DID number is required on the DIDWW account.
Verification setup fields#
These fields are shown in the General step when creating a Toll-Free Sender ID Verification.
Field |
Description |
|---|---|
Friendly name |
The account-level name used to identify the verification. |
Identity (Business) |
The business identity assigned to the verification. |
Address |
The business address assigned to the verification. |
Sender ID selection fields#
Field |
Description |
|---|---|
Available source numbers |
Active DID numbers that support Outbound A2P SMS, are compatible with the selected business identity, and are not assigned to another Sender ID Verification. |
Allowed source addresses |
The DID numbers selected for this verification. |
Verification details fields#
These fields are shown in the Verification details step when creating a Toll-Free Sender ID Verification.
Field |
Description |
|---|---|
Business Registration Number |
The Employer Identification Number (EIN) for a business registered in the United States, or the government-issued business registration number for a business registered outside the United States. |
Legal Company Name |
The legal name of the business that will use the Toll-Free Sender ID. |
The legal classification of the business. |
|
Business registration type |
The type of registration number entered for the business. |
Website |
The complete website URL associated with the business and messaging use
case, including the |
Fortune 500 or 1000 company? |
Indicates whether the business is listed in the Fortune 500 or Fortune 1000. |
The category that best describes the messages sent with the Toll-Free Sender ID. |
|
Campaign description |
A specific description of the messaging purpose and content. |
How will customers opt in? |
One or more consent methods: Through my website, Through my app, Verbal agreement, or Physical form. |
Provide screenshots or scans of the opt-in form |
Supporting files for the opt-in process. This field is shown when Through my app or Physical form is selected, and accepts multiple attachments. |
Detailed opt-in flow description |
A step-by-step description of the opt-in process or the exact script used by an agent to obtain consent. Include the channel, wording, and confirmation step. |
I confirm that my opt-in flow requires mandatory, manual user confirmation to receive messages based on the campaign and allows users to freely opt out. |
Confirms that consent requires a manual action and that recipients can opt out. This checkbox is required before submission. |
Sample content messages #1 |
A representative message containing the business or brand name, expected message content, and applicable HELP and STOP wording. |
Sample content messages #2 |
A second representative message containing the business or brand name, expected message content, and applicable HELP and STOP wording. |
URLs included in messages |
All URLs expected to appear in messages sent under the verification. Listing these URLs helps prevent message blocking. |
Phone numbers included in messages |
All phone numbers expected to appear in messages sent under the verification. Listing these numbers helps prevent message blocking. |
Description |
A description of where customers can find the Toll-Free numbers, such as the business website, online advertisements, or application store listings. |
Screenshots (optional) |
Supporting screenshots showing where the Toll-Free numbers are published. |
Message volume type |
Indicates whether the monthly message volume is existing or projected. |
Estimated quantity |
The estimated total number of messages sent each month. |
Promotes commercial product? |
Indicates whether the messages promote a commercial product. Available values are Yes, No, and Unsure. |
Was this traffic previously on another messaging service? |
Indicates whether the messages are new or were previously sent through another messaging provider. |
Previous content copy |
Representative messages, including HELP and STOP wording, used with the previous provider. Shown when the traffic was previously sent using a short code or long number. |
Number(s) used with previous vendor |
The sending numbers used with the previous provider. Shown when the traffic was previously sent using a short code or long number. |
Link to privacy policy |
The complete URL of the business privacy policy, including the
|
Link to Terms and conditions |
The complete URL of the terms and conditions that apply to the messaging
service, including the |
Business entity type values#
Value |
Description |
|---|---|
Private Profit |
A privately owned for-profit business. |
Public Profit |
A publicly traded for-profit business. |
Non Profit |
A nonprofit organization. |
Government |
A government organization. |
Sole Proprietor |
A business owned and operated by one individual. |
Carrier verification#
A Carrier Sender ID Verification approves a business and its messaging use case for supported destinations where the Sender ID is assigned dynamically. You do not select or enter a Sender ID. The destination carrier assigns it when the SMS message is delivered.
Verification setup fields#
These fields are shown in the General step when creating a Carrier Sender ID Verification.
Field |
Description |
|---|---|
Friendly name |
The account-level name used to identify the verification. |
Target countries |
A predefined country group for which the messaging traffic is being verified. Selecting any country in a group selects the entire group; countries cannot be added or removed individually, and groups cannot be combined. Pricing and Identity Requirements apply once to the whole group. |
Identity (Business) |
The business identity assigned to the verification. |
Address |
The business address assigned to the verification. |
Verification details fields#
These fields are shown in the Verification details step when creating a Carrier Sender ID Verification.
Field |
Description |
|---|---|
Legal Company Name |
The legal name of the business that will send the messages. |
Website |
The website associated with the business and messaging use case. |
The category that best describes the messages that will be sent. |
|
Campaign description |
A specific description of the messaging purpose and content. |
How will consumers opt in? |
A description of the complete consumer opt-in flow or the script used by an agent to obtain consent. |
Sample content messages #1 |
A representative example of the messages that will be sent. |
Sample content messages #2 |
A second representative example of the messages that will be sent. |