Evidence must travel by the route the submission target actually offers

The requirementstatement

Evidence must reach the reviewer through the channel the submission target provides, whether an upload field, a TCR attachment, or a URL inside the flow.

Severityseverity: HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase: Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject: evidence channel + campaign.message_flow
Where it liveslayer: CampaignCAMPAIGN
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: Supply evidenceTERMINAL_EVIDENCE; Needs proof only you hold: a screenshot, a recording, a scan of the form people signed.
Who requires itauthorities: BandwidthTelnyxBird
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

Every platform exposes exactly one evidence channel and none of them is the same: one has a multimedia upload field, one attaches the form to TCR, one accepts files only in its console and needs a URL in the payload when you use the API. Evidence lodged in the wrong place is not late or malformed — it is invisible, and the rejection reads as though nothing was ever attached.

How to fix itremediation

Use your target's channel: Bandwidth's "CTA, Privacy Policy and/or Terms and Conditions Multimedia Upload" field; a TCR attachment on the express-consent form for Telnyx; Bird's console attachments, or the proof URL inside the messageFlow JSON when you submit by API because attachments there are UI-only. Done when the evidence is reachable from the submission itself rather than from your own console.

A compliant exampleexample

Submitting to Bird by API: messageFlow ends with "Opt-in proof: https://cdn.acmecoffee.com/compliance/optin.png" because attachments cannot be sent over the API.

Common mistakespitfalls

Attaching in the console and submitting by API is the combination that silently loses the evidence: the file is visible to you and absent from the payload the reviewer receives.

Notesnotes

Three catalog rows, one obligation with the destination as its parameter — Bandwidth's upload field (CMP-131), Telnyx's TCR attachment (CMP-133) and Bird's API workaround (CMP-134). Written as one rule because a submitter has exactly one target and needs exactly one instruction; three rules would report the same gap three times with two of them irrelevant. We can see that evidence exists and whether the flow text carries a URL, but not which UI field a file was uploaded through, so the check settles the observable half and the remediation carries the rest.

Rules you will hit next

Other campaign rules at the same severity. A registration is judged as a whole, not rule by rule.

CMP-016Contact email and phone must contain no spacesHighHIGH CMP-023Declared embedded links must come with a sample URLHighHIGH CMP-041The description must say how often the messages comeHighHIGH CMP-042A programme that asks for money must say soHighHIGH CMP-048Emergency framing requires the emergency use caseHighHIGH CMP-051A first-party lender must use the phrase the reviewer looks forHighHIGH

All campaign rules

CMP-131 is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.