SMS Messaging
Set up reusable SMS sender identities, programs, and consent disclosures.
What this controls
SMS Messaging stores the provider-neutral customer-facing setup that forms can reuse across one website:
- the sender or brand name recipients recognize;
- the messaging program and its purpose, message type, and frequency;
- the default phone country;
- the exact consent disclosure and related policy links.
This setup does not connect a phone provider or enable sending by itself. Manage Twilio credentials, sending numbers, carrier readiness, and test messages under
Set up SMS messaging
Open SMS Messaging
Open Website Settings → SMS Messaging.
Create the website setup
Select Set up SMS messaging. Add the public sender name, program name, message type, purpose, expected frequency, default phone country, and optional policy links. Terms and Privacy use the standard link selector, so you can choose an existing website page or a full external URL.
Review the disclosure
Generate or enter the exact unchecked checkbox disclosure customers should see. Confirm the sender, purpose, frequency, STOP, HELP, and consent-not-required-for-purchase language before creating the setup.
Connect a provider
Open Integrations and configure Twilio or another supported provider and sending number before attempting live messages.
The identity, program, and disclosure are saved once for this website. Forms still require an explicit form-level opt-in configuration so collecting a phone number never silently grants texting permission.
Creating this setup stores the records in Hiveality only. It does not send the data to Twilio, Zernio, a carrier, or a recipient. The stored records are used later as consent evidence and dispatch configuration when an authorized SMS operation actually occurs.
Add SMS permission to a form
- Add a Phone field to the form.
- In the form’s Settings tab, find the compact SMS opt-in row under Tags & Lists.
- Select Add or Configure and connect the phone field and consent checkbox to the intended website program.
- Keep consent optional unless the entire form exists specifically for SMS enrollment.
- Publish and submit a test entry before using that permission in a Flow.
Forms without a phone field and without an existing SMS configuration do not show SMS controls. Checkout, quiz, and booking phone collection also remains separate from SMS permission unless a future surface explicitly displays and records an SMS disclosure.
Related Help Docs
Was this helpful?