Which 8 fields belong in a consent record?
| Field | Why it matters |
|---|---|
| Phone number | Subscriber identifier and suppression target |
| Timestamp | Sequence and applicable disclosure record |
| Source | Popup, checkout, keyword, QR, event, or other path |
| Disclosure version | What the person saw at capture |
| Program / brand | Sender and campaign expectation |
| Confirmation state | Whether the subscription response completed |
| Consent status | Current eligibility for the relevant program |
| Opt-out record | Suppression timing and keyword evidence |
What should the first reply accomplish?
The confirmation should identify the sender and match the promise made at capture. It should state material program information required by the applicable rules and make help and opt-out behavior clear. Exact language needs provider and counsel review. The operating goal is consistency across the call to action, disclosure, reply, and future content.
How should imported numbers be handled?
Do not treat possession of a phone number as permission to market by text. An import needs a documented source, consent basis, program match, and suppression check. If evidence is missing, isolate the records and ask counsel to review them before any promotional send. A clean database can still contain unusable consent.
Which tests happen before launch?
- Subscribe through every live source on a real mobile device.
- Capture the disclosure, timestamp, source value, and confirmation reply.
- Test HELP and common opt-out keywords under the configured provider behavior.
- Confirm that suppression reaches campaigns and automations.
- Check that re-entry rules do not silently reactivate an opted-out number.
Pair this checklist with SMS list-growth operations, the A2P 10DLC guide, and compliance support.