Educational guide only. This is not legal advice and does not guarantee Twilio, carrier, or campaign approval. Requirements can change. Have qualified counsel review your final implementation.
Explain the real product or service and tell visitors exactly what happens next. The offer, business identity, and message use case should match the A2P campaign.
Use the same registered sender name customers see in text messages.
Describe the actual service, audience, and follow-up.
Publish complete business and contact details in the footer.
Example lead form
Request your consultation
Complete the fields below. SMS consent is optional and is not a condition of purchase.
Why this structure works
Make consent obvious and easy to verify.
1
Unchecked and optional
Both controls start unchecked in the DOM. Neither is required, and the visitor can continue without selecting either one.
2
Separate by use case
Marketing consent is not bundled with informational, scheduling, service, or support messages.
3
Disclosures are adjacent
Message type, frequency, rates, HELP, STOP, and direct policy links appear at each consent action.
GoHighLevel build notes
Use a separate checkbox custom field for marketing consent and informational consent.
Confirm both checkbox fields are unselected by default and not marked required.
Build separate workflow entry conditions for each consent selection. A marketing workflow must not enroll a contact who selected only informational texts.
A phone number in a contact record is not proof of SMS consent.
Preserve the selected field, source/form URL, consent timestamp, and version of the disclosure shown.
Keep the full disclosure visible; do not hide it in a tooltip, pop-up, or footer.
Test the live page in a private browser window and take a full-page screenshot for the reviewer file.