A2P 10DLC Campaign Registration Rejected – Twilio Support

Issue

Notice: Beginning September 15, 2026, A2P 10DLC verification and registration move to a single, unified content and messaging policy shared across Twilio's Toll-Free Verification and A2P 10DLC programs. As part of this change, Twilio is introducing new, more specific rejection error codes and refining several existing ones so that the reason for a rejection, and the exact fix, is clearer. See Error Code Changes Effective September 15, 2026 for more details.

Why was my A2P 10DLC Campaign registration rejected? If your A2P 10DLC Campaign registration request is rejected for eligible reasons, you need to correct and resubmit your request. For a full list of eligible rejection reasons see below. If eligible, you can re-submit your Campaign registration after correcting the identified content violation by deleting and resubmitting the campaign.

Product

Programmable Messaging

Environment

legacy Twilio Console

Resolution

Rejection types eligible for resubmission 🔗

Each of the below rejection codes are eligible for resubmission. To resolve these issues, please take the corrective action(s) outlined in the table below, and then re-submit your Campaign registration request with the updated information.

Error Code	Rejection category	Rejection reason	Correction needed
30886	Invalid Campaign Description	Campaign description does not thoroughly explain the purpose of the campaign or description does not match the use case.	Verify that the campaign description is accurate and detailed. If you are an ISV registering a direct offering to your customers, please indicate that in the campaign description. Resubmit campaign for review.
30893	Invalid Sample Message Use Case	Sample messages are either not provided, unclear, or content does not match the campaign use case.	Verify that sample messages are accurate and detailed. Sample messages should reflect actual messages to be sent under campaign and indicate templated fields with brackets. At least one of the sample messages needs to include your business name. Use case and campaign description need to match campaign description.
30892	Invalid Sample Message - Public URL Shorteners	Public URL shorteners are not accepted. The website URL included in the sample messages was either from a public URL shortener or is non-secured.	Remove public URL shorteners from sample messages.
30891	Invalid Website URL	Invalid URL was provided for registration. Websites need to be functioning. If this is a registration pre-launch, it needs to be indicated in campaign description.	Verify that provided websites are functioning or detail is provided if the registration is for a pre-launch website.
30896	Opt-in Error	Opt-in message workflow is not sufficient for campaign type and consent is required or opt-in is shared with 3rd parties.	Verify opt-in meets CTIA's guidelines. All methods of opt-in need to be listed. If opt-in is collected through a paper form or behind a login, please provide a hosted link to the image of opt-in. If opt-in occurs on a website, please provide a link to the website. The website needs to have a privacy policy and terms of service. Ensure opt-in is not shared with 3rd parties.
30887	Opt-out Error	Campaign indicated collecting and processing consumer Opt-Outs, but the workflow is unclear, missing opt-out keywords or opt-message.	Verify that opt-out workflow is accurate and update Message Flow (labeled as 'How do end-users consent to receive messages' while submitting) description with opt-out process.If opt-out is managed, add opt-out keywords and update opt-out message to to include acknowledgement of opt-out request, confirmation that no further messages will be sent, and brand name.
30890	Subscriber Help	HELP message reply does not contain brand name, phone number, or email address.	Verify that subscriber help message contains brand name, phone number, or email address. Message needs to guide customers on who them can contact after replying "help".
30889	Embedded Phone Number	Embedded phone number use is selected, but is not reflective in the sample message.	Verify embedded phone number selection is accurate. Update the Sample Messages with Embedded Phone Number or update Embedded Phone Number selection.
30888	Age Gate Not Present / Not Acceptable	Age gate is not present.	Verify and add a robust age gate to your website or opt-in policy.
30881	Invalid Brand Support Email	Support email is not associated with the brand. The brand support email was either invalid or associated with a public domain email.	Verify brand support email is valid and not associated with a public domain email.
30894	Invalid Brand Information	Campaign registration needs to be associated with the brand behind the campaign. If you are an ISV registering a direct offering, campaign description needs to indicate a direct offering.	Verify brand information is valid.
30895	Direct Lending - Campaign and Content Attribute Error	Campaign is for direct lending or loan arrangement and is missing content attribute indicating direct lending.	Verify direct lending or loan arrangement is selected for campaign registration. If the campaign is not related to direct lending or loan arrangement, please update the campaign description.
30903	Incorrect Sole Prop Brand Registration	Brand behind the campaign does not meet the small business Sole Proprietor (EIN) criteria set by TCR and mobile carriers. Campaign can not be registered with a Sole Proprietor use case.	Register the brand as a standard brand and register a standard or acceptable campaign use case that aligns with the registered brand’s classification.
30907	Website URL Validation Issue	Website URL does not match the campaign description or Brand information.	Confirm the website aligns with the registered Brand and Campaigns.
30908	Compliant Privacy Policy Required	A compliant privacy policy was not provided in the Message Flow or could not be located on the website.	Verify privacy policy is accessible to end-users and include a direct link to the privacy policy with the Message Flow.
30909	CTA Verification Issue	Call to Action with the campaign could not be verified.	Provide complete CTA information and all possible methods end-users consent to messaging.

Rejection types ineligible for resubmission 🔗

Each of the below rejection errors are due to forbidden messaging categories, and are therefore ineligible for resubmission. Please note that in addition to A2P 10DLC Messaging content restrictions, any use cases that violate Twilio's Acceptable Use Policy or Messaging Policy are also not allowed on Twilio's platform, regardless of number, sender type and destination country.

Notice: Users who disagree with their rejection can Contact Support to request an appeal. In your request, please include the details of your appeal and the subject line "10DLC Campaign Appeal for (your business name or number)".

Error Code	Rejection Category	Rejection reason
30883	Content Violation - SHAFT - Sex	Submission included content such as nudity, pornography, sex toys, or other adult content
30883	Content Violation - SHAFT - Hate	Submission included speech that is hateful, profanity, violent, incites violence, or similar speech
30883	Content Violation - SHAFT - Alcohol
30883	Content Violation - SHAFT - Firearms	Submission included:Firearms, Ammo, Gun Ranges (Common for guns to be sold at Gun Ranges)
30883	Content Violation - SHAFT - Tobacco / Vape	Submission included products such as: Cigarettes, Cigars, Tobacco Products (Chew, etc), Vape, Vape Juice, or similar items
30883	Content Violation - SHAFT - Marijuana / CBD	Submission included products such as: Cannabis, Marijuana, CBD, THC, Hemp or similar items
30884	Spam/Phishing	Spam/Fraud team has flagged the number/business/traffic for spam or phishing.
30885	High Risk	Spam/Fraud team has flagged the number/business/traffic for fraud or deceptive marketing. Privacy policy or Terms associated with the campaign may indicate that SMS opt-in consent or phone numbers are being shared with third parties or affiliates.
30897	Disallowed Content	Submission included:disallowed content types, such as Loan Marketing, 3rd party debt collection, gambling, sweepstakes, stock alerts, cryptocurrency, risk investments, debt reduction, credit repair, 3rd party lead generation, federally illegal substances. Privacy policy or Terms associated with the campaign may indicate that SMS opt-in consent or phone numbers are being shared with third parties or affiliates.
30882	Terms & Conditions	Campaign does not meet Terms and Conditions.
30898	Excessive EIN	Same EIN is used for multiple brands. Only register minimum number of brands per EIN and do not resubmit until brand registration is updated.

New Granular Error Codes - March 23rd, 2026 🔗

Effective March 23rd, 2026 the following new error codes were introduced to provide more precise rejection reasons compared to the previous general codes. Instead of receiving a broad code like 30883, 30885, or 30897, you’ll be given a code that specifically identifies the issue.

The general catch-all code 30883, which covers specific SHAFT categories such Sex, Hate, Alcohol, Firearms, and Tobacco will now have distinct error codes. These content categories are restricted or prohibited under CTIA messaging guidelines. The restrictions are applicable to campaign descriptions, sample messages, website content, and any linked URLs.

Furthermore, there are specific high-risk and disallowed error codes that take the place of the general 30884 or 30885 codes, identifying particular risk categories.

Error Code	Rejection Category	What It Means	Correction Needed
30909	Opt-In and Consent	Your Call-to-Action/Message Flow cannot be verified by reviewers	Provide complete CTA information and all methods end-users use to consent. If behind a login, provide hosted screenshots.
30913	Opt-In and Consent	Marketing consent must be collected separately from informational/transactional consent	Add separate consent for promotional messages. If you only send transactional messages, clarify this in your campaign description.
30917	Opt-In and Consent	You selected multiple opt-in methods but did not describe all of them	Update your opt-in workflow description to cover every method listed.
30923	Opt-In and Consent	Messaging consent is bundled into mandatory terms or agreements	Ensure opt-in is a separate, optional action. Consumers must be able to decline messaging and still use your service.
30924	Opt-In and Consent	Consent language is missing required disclosures (frequency, opt-out, rates)	Add all four: message type, frequency, "message and data rates may apply," and STOP instructions near the opt-in checkbox.
30925	Opt-In and Consent	Opt-in form is missing a checkbox, or the checkbox is pre-selected	Add an unchecked-by-default checkbox specifically for SMS consent.
30931	Opt-In and Consent	Opt-in form mechanics prevent consumers from declining messaging	Add an explicit skip option or unchecked checkbox. A single button must not grant all permissions including messaging.
30932	Opt-In and Consent	Privacy policy indicates opt-in data is shared with third parties for marketing	Update your privacy policy to explicitly state that mobile information will not be shared with third parties for marketing purposes.
30919	Website	Website lacks sufficient business information or messaging disclosure	Add: company name, description of services, contact information, privacy policy, and mention of your SMS messaging program.
30920	Website	Website is just a form (lead capture, sign-up) without business context	Add business context around your form: company name, what your business does, contact information.
30921	Website	Website requires a login -- reviewers cannot access it	Create a publicly accessible page describing your business and messaging program.
30922	Website	Website does not meet verification requirements (under construction, non-standard URL)	Provide a functioning, standard URL. If pre-launch, note this in campaign description and provide screenshots.
30914	Business Identity	Sole proprietor campaign content does not match registered name	Align campaign description, sample messages, and website with the sole proprietor name you registered.
30915	Business Identity	Registered as sole proprietor but using a corporate name (LLC, Inc.)	Re-register as a standard brand using your EIN and corporate information.
30918	Business Identity	DBA (Doing Business As) name does not match legal name on file	Update brand registration to include your DBA name before resubmitting.
30926	Business Identity	Campaign references multiple companies or brands	Register separate campaigns for each brand. Each brand needs its own campaign.
30927	Business Identity	Opt-in evidence shows a different company than the one registered	Ensure opt-in evidence (screenshots, URLs) shows the exact company name matching this campaign's brand registration.
30971	Business Identity	Contact email uses a personal domain (gmail, yahoo) instead of official business domain	Register and use a business email address (e.g., name@yourcompany.com).
30972	Business Identity	Contact person listed is not an authorized representative of the business	Update the contact to an authorized representative of the registered business.
30910	Use Case	Registration fields contain non-English language	Campaign registration fields must be in English. Provide English translations of sample messages alongside originals.
30911	Use Case	Same text was copy-pasted across multiple registration fields, or all sample messages are identical	Each field (description, sample messages, message flow) must contain unique content. Each sample message must be distinct.
30912	Use Case	Use case appears to be personal/P2P messaging, not A2P	Describe what software or platform triggers the messages and how it serves your customers.
30916	Use Case	Selected lead generation but described lead nurture (or vice versa)	Lead generation = initial outreach to acquire new leads. Lead nurture = ongoing engagement with existing leads. Choose the one that matches.
30928	Use Case	Social influencer/public figure communications are not a valid use case	Register as a business entity and frame your campaign around your business use case (e.g., e-commerce, event notifications).
30929	Use Case	Emergency alert notifications are not permitted through A2P 10DLC	Emergency alerts are not a valid A2P 10DLC use case. Contact support for alternatives.
30930	Use Case	Your brand has reached the 100-campaign limit	Deregister unused campaigns in the Twilio Console to free up capacity.
30940	Disallowed	Cannabis, CBD, marijuana, or illegal substances
30941	Disallowed	Prescription drugs or controlled substances
30942	Disallowed	Loan marketing (payday, auto title, personal loans)
30943	Disallowed	Third-party debt collection
30944	Disallowed	Gambling or betting
30945	Disallowed	Sweepstakes or contests
30946	Disallowed	Stock alerts or investment signals
30947	Disallowed	Cryptocurrency trading or token promotions
30948	Disallowed	High-risk investment opportunities (forex, binary options)
30949	Disallowed	Debt reduction or consolidation services
30950	Disallowed	Credit repair services
30951	Disallowed	Third-party lead generation or multi-level marketing (MLM)
30952	Disallowed	Non-federally compliant use case
30953	SHAFT	Sex or adult content
30954	SHAFT	Hate speech, violence, or offensive content
30955	SHAFT	Alcohol promotions
30956	SHAFT	Alcohol content without a robust 21+ age gate
30957	SHAFT	Firearms, fireworks, or explosives
30958	SHAFT	Tobacco or vape products
30959	High Risk	Fraudulent or misleading content detected
30960	High Risk	Campaign identified as a known phishing campaign
30961	High Risk	Website or URL has a high-risk domain reputation
30962	High Risk	Deceptive marketing practices (false urgency, bait-and-switch, fake endorsements)
30963	High Risk	Campaign uses public URL shorteners (bit.ly, tinyurl, etc.)
30964	High Risk	Campaign URLs use HTTP instead of HTTPS
30995	Registration Issue	Your account has reached the maximum Messaging Services Phone Number limit	Reach out to Support

Error Code Changes Effective September 15, 2026

Beginning September 15, 2026, A2P 10DLC verification and registration move to a single, unified content and messaging policy shared across Twilio's Toll-Free Verification and A2P 10DLC programs. As part of this change, Twilio is introducing new, more specific rejection error codes and refining several existing ones so that the reason for a rejection, and the exact fix, is clearer.

What this means for you: if a submission is rejected on or after September 15, you may see one of the new error codes below instead of a broader, general code. Each new code names a single, specific issue and the action needed to resolve it. All of the new codes are eligible for resubmission: correct the identified issue and resubmit.

New error codes (effective September 15, 2026)

Error Code	Category	What it means	Correction needed
30532	Business Information	Personal use cases are not supported	Update your submission to describe a valid business use case, then resubmit.
30533	Business Information	Person-to-person (P2P) use cases are not supported	Update your submission to describe an application-to-person (A2P) use case, then resubmit.
30534	Business Information	Testing use case is missing business or program details	Provide accurate business details, including a live website, valid address, and correct contact information.; Add a detailed testing use case description with supporting documentation that identifies the recipients.; Confirm that messaging is strictly internal and that no messages will be sent to external recipients, then resubmit.
30535	Business Information	Viral messaging is missing required compliance disclosures	Limit messages to a single, non-recurring communication.; Obtain prior recipient consent and select recipients individually rather than in bulk.; Include the sender's identity, message purpose, recipient name, and an opt-out mechanism in every message.; Remove any compensation, rewards, or incentives for senders, then resubmit.
30536	Business Website	Privacy policy URL is missing or inaccessible	Provide a privacy policy URL that is publicly accessible and active.; Ensure the page includes all relevant disclosures about consumer data protection and privacy, then resubmit.
30537	Message Program Details	Business model does not match the messaging use case	Align your messaging program details with the core business model and information on your website.; Update the sample messages or website details so they are consistent, then resubmit.
30538	Message Program Details	A message sample is missing for a selected use case	Provide a unique message sample for each use case you selected, then resubmit.
30539	Message Program Details	Opt-out instructions or keywords are missing or noncompliant	Update your consent details to include standard, compliant opt-out language.; Place the instructions in plain sight on the call-to-action screen using an industry-standard phrase verbatim, such as "Reply STOP to cancel" or "Reply STOP to opt out," then resubmit.
30540	Message Program Details	Double opt-in confirmation message is required	Provide a double opt-in confirmation message that includes the brand name, program name, a "message and data rates may apply" disclosure, and help and opt-out disclosures, then resubmit.
30541	Message Program Details	Political campaign is missing an FEC or state committee ID	For federal campaigns, submit a valid FEC Committee ID. You can search committee and candidate profiles at https://www.fec.gov/data/.; For state campaigns, submit a state committee registration number or equivalent official documentation, then resubmit.
30542	Message Program Details	Political messaging must use the Political use case category	Change the submission's use case category to Political.; Ensure the message samples and description align with the Political category and include a valid Campaign Verify Token, then resubmit.
30543	Opt-In and Consent	Live opt-in link not provided	Provide the accessible link to the landing page where the live opt-in is located.; Confirm the link points to the current, publicly accessible form and matches the opt-in described in your submission.; Resubmit once the working link is included.
30544	Opt-In and Consent	Call-to-Action does not state the message purpose	Update the CTA disclosure to clearly describe the specific purpose of the messages, such as "marketing offers and promotional alerts" or "appointment reminders".; Resubmit with the updated disclosure text.
30545	Opt-In and Consent	Call-to-Action does not state message frequency	Update the CTA disclosure to explicitly state message frequency using standard phrasing such as "Message frequency varies," "1 msg per request," or "4 msgs/month".; Resubmit with the updated disclosure text.
30546	Opt-In and Consent	Opt-in agreement expired without the required changes	Provide a compliant opt-in that includes the specific modifications requested during the earlier review.; Submit proof of the fully compliant opt-in to move forward with verification.
30547	Opt-In and Consent	Call-to-Action is missing opt-out instructions	Add clear opt-out instructions to the CTA disclosure that reference a valid opt-out keyword such as STOP, UNSUBSCRIBE, END, QUIT, HALT, or CANCEL, for example "Text STOP to cancel".; Resubmit with the updated disclosure text.
30548	Opt-In and Consent	Charitable program does not separate consent for donation requests	Update the registration form to use separate, independent checkboxes for each program component.; Provide unchecked checkboxes so users can opt into informational updates without being forced to consent to donation requests, for example one checkbox for account and informational alerts and a separate checkbox for fundraising and donation messages.; Resubmit with the updated form.
30549	Opt-In and Consent	No Terms of Service link found in the opt-in flow	Include an accessible hyperlink to the Terms of Service within or immediately adjacent to the opt-in flow and the CTA disclosure text.; Resubmit once the link is in place.
30550	Opt-In and Consent	No Privacy Policy link found in the opt-in flow	Add a clear, accessible hyperlink to your compliant Privacy Policy within or adjacent to the opt-in flow and the CTA disclosure text.; Resubmit once the link is in place.
30551	Opt-In and Consent	Consent does not specify SMS or text messaging	Update the disclosure to explicitly include the terms "SMS" or "text messages", for example "By checking this box, you agree to receive SMS notifications...".; Resubmit with the updated disclosure text.
30552	Opt-In and Consent	Opt-in is not customer-facing	Submit proof of direct end-user consent, such as a customer-facing web form, paper intake form, or verbal script.; Do not use internal admin dashboards or staff-selected CRM checkboxes as opt-in proof, and resubmit with valid customer-facing proof.
30553	Opt-In and Consent	SMS is forced for two-factor authentication	Update the authentication workflow to offer at least one alternative delivery method, such as an email confirmation link, alongside the SMS option.; Resubmit once an alternative channel is available.
30554	Opt-In and Consent	Charitable donations collected insecurely over SMS	When a user texts a keyword such as "DONATE", reply with a secure HTTPS link to an external page where the donor can process payment themselves.; Remove any text-based payment collection from the messaging flow and resubmit.
30555	Opt-In and Consent	First message sent without documented prior consent	Submit visual proof of the complete opt-in sequence, clearly showing the step where the user consents before receiving the first message.; Resubmit once the full opt-in flow is documented.
30556	Opt-In and Consent	SMS consent is bundled with other communication channels	Separate SMS enrollment from all other communication channels so the user can opt into text messages independently.; Resubmit with a standalone SMS opt-in.
30557	Privacy Policy and Terms of Service	Terms of Service missing business or program name	Update the Terms of Service to explicitly state the registered business or messaging program name.; Resubmit your registration once the Terms of Service identify the business or program name.
30558	Privacy Policy and Terms of Service	Terms of Service missing message frequency disclosure	Update the Terms of Service to state the message frequency, such as "Message frequency may vary" for recurring programs.; For one-time or fixed programs, specify an exact message count.; Resubmit your registration once the message frequency is disclosed.
30559	Privacy Policy and Terms of Service	Terms of Service missing product description	Update the Terms of Service to include a clear product description outlining the types of messages subscribers will receive.; Resubmit your registration once the product description is added.
30560	Privacy Policy and Terms of Service	Terms of Service missing customer support information	Add a working support pathway subscribers can use to reach customer care directly, such as a support email address or telephone line.; Include HELP keyword instructions where applicable.; Resubmit your registration once support contact details are added.
30561	Privacy Policy and Terms of Service	Terms of Service missing opt-out information	State the cancellation keyword instructions, such as standard keywords like STOP, END, CANCEL, UNSUBSCRIBE, and QUIT.; Resubmit your registration once opt-out instructions are added.
30562	Privacy Policy and Terms of Service	Terms of Service missing message and data rates disclosure	Include explicit "Message and data rates may apply" disclosure language within the Terms of Service.; Resubmit your registration once the disclosure is added.
30563	Privacy Policy and Terms of Service	Terms of Service missing carrier liability disclosure	Add a carrier liability clause stating that wireless carriers are not liable for delayed or undelivered messages.; Resubmit your registration once the carrier liability disclosure is added.
30564	Privacy Policy and Terms of Service	Terms of Service and Privacy Policy links not near opt-in	Place direct text links labeled Terms of Service and Privacy Policy within close proximity of the call-to-action or opt-in section.; Make the links plainly visible rather than hidden inside dropdowns or pop-ups.; Resubmit your registration once the links are positioned near the opt-in.
30565	High Risk	Prescription Drugs and GLP-1s: Informational Use Only	Update your use case to strictly informational messaging, such as two-factor authentication, order and shipping updates, or account and appointment alerts.; Remove all promotional language and marketing intent from your campaign details and message samples.; Add an explicit age requirement, such as "Must be 18+ to participate," to your Terms of Service.; After making these changes, resubmit your registration for review.
30566	Disallowed Content	Academic Fraud and Cheating Services Are Prohibited	Confirm that your use case does not involve academic dishonesty, such as essay writing, exam assistance, test answer sales, ghostwriting, or impersonation services.; If your service is legitimate, update your campaign description and message samples to clearly describe your actual use case.; Once your content no longer facilitates academic dishonesty, resubmit your registration for review.
30567	Disallowed Content	Phishing and Simulated Phishing Messages Are Prohibited	Confirm that your messaging is not designed to simulate phishing or smishing attacks.; If your use case is legitimate, update your campaign description and message samples to reflect your actual messaging and remove any simulated phishing or credential-testing content.; Once your content no longer simulates phishing attacks, resubmit your registration for review.

Updated error codes (refined rejection reasons)

The following existing error codes have updated descriptions to reflect the current policy. The code number is unchanged; the rejection reason and guidance have been clarified.

Error Code	Updated rejection reason	Correction needed
30971	Business email must be tied to your official business domain	Use an email address on your business's official domain (for example, name@yourcompany.com).; If you do not have an official domain, register one and set up a professional business email.; If you use a free provider address, make sure that exact address is published on your official website or social media so it can be verified.

My Campaign Use Case was rejected - What can I do? 🔗

If your Campaign registration request was rejected, your next steps will depend on the eligibility of the campaign.

1. If the campaign is ineligible: You may still be able to use another Twilio product to reach your recipients.

The Twilio Sendgrid Email API is an option for many of the above use cases. For example, cannabis- or CBD-related messaging may be conducted via email, as long as you have proper age gating in place and are sending toward recipients in a locale where the substance is legal. In addition, the Twilio Programmable Voice product is not subject to the same carrier restrictions as SMS.

For more information about cannabis-related messaging alternatives, see Can I send cannabis or CBD-related messaging traffic on Twilio.

2. If the campaign is rejected for specific issues that allow for resubmission: You can address these issues, make the necessary adjustments, and resubmit the campaign for approval.

To do this, you can edit a Campaign directly in theTwilio Console or through the API.

You also have the option to delete (unregister) an A2P Campaign via the Twilio Console or API, and register a new one in its place as described in Deleting and Recreating a failed Campaign via Twilio Console.

Campaigns can also be recreated via API request. For more details see Troubleshooting Campaigns via the API.

Regardless of the reason for rejection, it is crucial that you fix any rejected campaigns promptly; otherwise, you will incur the TCR monthly fee. Deleting the rejected campaigns not only avoids unnecessary charges but also helps you maintain a clear record of your active and pending campaigns.

Additional Information

Who rejected my A2P 10DLC Campaign Registration?

Each campaign will incur a single vetting charge of $15. If your campaign gets rejected, you can edit it and resubmit, but without an extra vetting fee.

If the rejected campaign is deleted and recreated, a new $15 vetting fee will be applied.

If you believe that the campaign was rejected due to a mistake, please edit and add clarity to the campaign registration details and resubmit the campaign for review. For a full overview on the process visit our Troubleshooting A2P Campaigns guide.