SMS Opt-in Form Template
Build a text list that can survive an audit. The form captures express consent as its own deliberate choice, with topics the subscriber picked.
Texts land where email never does, but only with your explicit say-so. Choose what you want, know the terms, and opt out with one word whenever you like.
SMS is the most regulated channel in mainstream marketing for a plain reason: texts are intrusive, and the law treats the subscriber's permission as the product. An SMS list built without care is a liability with a send button. This opt-in form is arranged so every number on your list arrives with the paperwork already done.
Consent as an act, not an assumption. The consent block is a required single choice whose one option spells out the full deal: recurring automated marketing texts, consent not a condition of purchase, message and data rates, reply STOP to cancel. The subscriber has to select it, nothing is pre-ticked, and the form cannot be completed around it. That deliberate tap, stored with the response, is the kind of express-consent record that carrier audits and TCPA-style complaints turn on. Export the CSV and you hold a consent ledger: the number, the wording agreed to, and the moment it was submitted.
Why topics come before consent. The multi-select does two jobs. Commercially, it segments your sends from day one, since the person who chose only "back-in-stock alerts" churns fast if you text them daily deals. Legally and culturally, it reframes the exchange: the subscriber is configuring a service instead of handing over a phone number. Lists built this way carry lower STOP rates, and STOP rates are the metric carriers police.
So few identity fields, on purpose. A phone number and an optional first name are the whole roster. SMS personalization beyond a name seldom repays the friction at opt-in, and the phone block's structured input keeps numbers clean enough for your sending platform's import. Everything else is absent by design: no email cross-capture, no birthday, no address, because mixing channel consents in one form muddies both records.
What this form leaves to your platform. Listel records the opt-in, while your SMS platform sends the messages and processes STOP replies. Pipe new opt-ins to that platform with a webhook, signed and retried on failure, or by CSV import, and keep the consent record here as your audit trail. This split, form as consent ledger and platform as sender, is the setup compliance reviewers like to see.
Who builds a text list this way. Ecommerce brands build flash-sale lists with it, restaurants run waitlist and daily-special texts, gyms and clinics send reminders, and creators keep drop-based release schedules.
Localize the wording. Localize the consent wording to your jurisdiction and program terms, including frequency and program name, swap the topics for your real message types, and keep the intro's promise about STOP behavior true in your sending platform. The form's honesty is what makes the list durable.
Frequently asked questions
Does this form satisfy express-consent requirements?
It captures the right artifact: an unticked, required, affirmative choice with full program terms, stored per response. Confirm the wording against your jurisdiction and program specifics with counsel.
How do opt-ins reach my SMS sending platform?
Add a webhook so each opt-in POSTs to your platform or middleware in real time, or export CSV and import on your cadence. Keep the form responses as your standing consent ledger.
Why is the consent a single choice instead of a checkbox?
A required single-choice option forces a deliberate, recorded act of agreement, with nothing pre-ticked and nothing implied. That deliberateness is what makes the record defensible.
Can I verify the numbers are real?
The phone block enforces plausible formats, and the spam stack (honeypot, timing, proof-of-work) blocks automated junk. True number verification via confirmation text happens in your SMS platform after import.