# MSG-060 — The opt-in confirmation must be the first message sent

> The confirmation must precede any other messaging to a newly opted-in consumer.

- **Rule ID:** MSG-060
- **Layer:** Message content (`MESSAGE_CONTENT`)
- **Checks:** `campaign.message_flow + campaign.optin_message`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI judgement over the submitted form
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** CTIA, TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/message-content/msg-060/

## Why this rule exists

Leading with marketing to someone who has just given a number, before confirming what they joined, inverts the relationship the confirmation exists to establish. CTIA sequences it deliberately: acknowledge first, then send.

## How to fix it

Sequence the confirmation ahead of any campaign content in your automation, and describe that ordering in the message flow.

## Example of a compliant value

```text
On opt-in we immediately send the confirmation; campaign content begins with the next scheduled send.
```