Short code verification form
Your Dotdigital Customer Success representative can provide you with this form. You must add any new traffic or messaging that has been added since the short code was originally registered.
​
Even if your campaign is not changing, you must complete this form.
​
Additionally, you must bring your campaign, opt-in, privacy policy, and terms and conditions up to date to reflect updates to section 3 of the CTIA requirements. Our form helps guide you through these requirements.
​

Common Short Code Administration (CSCA) lease receipt
Your current provider can provide you with this receipt. We need this receipt in order to request the migration to Dotdigital.

US Short code transfer request
Your current provider must set up this transfer. We cannot initiate this request from our side.
​
This request must be submitted prior to initiating the migration to Dotdigital. Your Customer Success representative can provide you with the account number to transfer the lease to upon request.
​

Target migration date
The target migration date must be at least 15 business days from the date that we submit the completed migration request.
​
The migration request cannot be submitted until the steps above have all been completed.

If the sending number will change, send a final message from the current number before the cutover. This message gives subscribers advance notice that future messages will come from a different number.

The final message should include the brand name, the new sending number, customer support contact information, and a clear opt-out method. Including these details helps reduce confusion, supports trust, and gives customers a compliant path to stop messages if they no longer want them.

Send before switching traffic so customers have time to notice the change. Write it clearly and simply, without extra promotional content. The goal is operational notice rather than marketing engagement.

Update or migrate all existing opt-out data into Dotdigital before you begin any outbound traffic on the new sending number. This ensures that customers who previously unsubscribed do not begin receiving messages again simply because the sending number changed.

Not migrating suppression and opt-out records creates compliance and customer experience risks. A subscriber who’s already opted out may view a message from the new sender ID as unsolicited, which can increase complaints, spam reports, and carrier filtering.

Verify that keywords such as STOP, HELP, and START are configured correctly on the new sender ID. This helps maintain continuity for compliance workflows and support interactions after the cutover.

The first live message from the new sending number should reinforce the transition announced in the final message from the old sender ID. This message should introduce the new sender, remind customers why they receive texts, and set expectations for message frequency and purpose.

This introductory message should also state that message and data rates may apply, include customer support information, and explain how to opt out. These elements help establish trust with the new sender identity and reduce the chance that recipients will mistake the message for spam or phishing.

Keep the transition simple and transparent so customers immediately understand that the sender is changing but the brand relationship is not.

Avoid overly promotional language; clear notices support trust and comprehension during sender migration.

Preserve suppression lists and compliance workflows before sending live traffic from the new sending number.

1: Introduction

2: Governing bodies

3: Compliance

4: Register your number

5: Opt-ins and consent