Debt relief and credit repair stay prohibited even with first-party consent

The requirementstatement

Debt consolidation, debt reduction and credit repair content is refused whether or not the sender collected the consent itself.

Severityseverity: BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
When it bitesphase: Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject: campaign.description + campaign.sample[] + campaign.message_flow
Where it liveslayer: Message contentMESSAGE_CONTENT
How Ekas settles itdetectability: DeterministicDETERMINISTIC; Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
What the fix involvesfailureClass: Hard stopHARD_STOP; Not remediable. Resubmitting will not help, and anyone offering to fix it is selling you a rejection.
Who requires itauthorities: TwilioBirdInfobipSinch
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

Consent is the answer to almost everything else in this framework, so operators reasonably assume it is the answer here too — and it is the one place it is not. Carriers refuse these categories on the business model rather than on the permission, because the consumer harm they are protecting against is the service itself: the fees, the credit damage and the misrepresentation happen to people who did agree to hear from the sender. Stating it as its own rule matters because the neighbouring first-party carve-outs are real, and a user who has just read that a creditor may chase its own invoice will otherwise conclude the same reasoning rescues a debt-settlement offer.

How to fix itremediation

Do not answer this by strengthening the consent record — a signed opt-in, a recorded call and a double opt-in all leave the verdict where it is. The campaign is registrable only without the debt-relief and credit-repair service in it, so remove those lines from the description, the samples and the flow, and register on whatever else the business does.

Provider rejection codescodes

The code you get back when this rule is what failed, and whether that provider lets you resubmit.

Provider	Code	Resubmit
Twiliogen2	30949	No
Twiliogen2	30950	No

Notesnotes

MSG-DEBT is the semantic screen and is what catches euphemism; this is the deterministic backstop, and it exists because the objection users actually raise is consent rather than wording. Matching on an explicit lexicon on purpose: the point is to answer the consent question before a round trip is spent on it, not to be the primary detector.

Rules you will hit next

6 other rules read campaign.description + campaign.sample[] + campaign.message_flow. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.

MSG-137No unsolicited bulk messagingBlockingBLOCKING MSG-161SHAFT screening covers every campaign field, not a sample of themBlockingBLOCKING MSG-164No underage, non-consensual or illegal sexual themesBlockingBLOCKING MSG-170No content promoting, glorifying or inciting violenceBlockingBLOCKING MSG-182No explosives, fireworks or pyrotechnics contentBlockingBLOCKING MSG-183No weapons that are not legal in all fifty statesBlockingBLOCKING

All message content rules

MSG-221 is one of 122 message content rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.