Configure SMS compliance
Disclaimer: This article describes Zenoti capabilities that SUPPORT compliance with the named regulation. It is NOT legal advice. You are responsible for confirming your own regulatory obligations with your legal counsel and for determining whether Zenoti's settings are sufficient for your jurisdiction and use case.
Zenoti supports the SMS regulatory requirements that apply to most wellness and beauty businesses. This article focuses on the two regimes Zenoti automates: the European Union General Data Protection Regulation (GDPR) as enforced in France, and the United States Federal Communications Commission (FCC) and Telephone Consumer Protection Act (TCPA) opt-out-confirmation requirements. It also acknowledges other regional regimes that operate-on-the-platform organizations must address with their own counsel and Zenoti support.
Required role: Owner or Administrator. Required permission: Permission to edit notification compliance settings at the organization level. The exact permission name varies by RBAC configuration β verify with your security admin which role grants edit access to Configuration > Notifications.
On this page
- GDPR β France SMS marketing quiet hours
- FCC and TCPA β SMS opt-out confirmation
- How opt-out keywords work
- Opt-out scope and how to restore delivery
- Marketing message send window
- Multi-region considerations
- Verifying compliance behavior
- Related articles
GDPR β France SMS marketing quiet hours
When your organization's country is set to France, Zenoti automatically blocks SMS marketing notifications during the periods prohibited by French GDPR guidance. This is a fixed regulatory rule β the window is set by the regulation, not by an organization setting:
- Overnight (8:00 PM to 8:00 AM) β marketing SMS cannot be sent between 8 PM and 8 AM.
- Sundays β marketing SMS is blocked all day.
- Public holidays β marketing SMS is blocked on holidays.
How it works
Zenoti enforces the quiet-hours block at send time. If a marketing SMS is scheduled to go out during a blocked period, the system either queues it to be delivered after the quiet period ends or suppresses it, depending on your organization's send-window settings.
Transactional SMS (appointment confirmations, reminders, OTP, payment receipts) is not blocked by the GDPR quiet-hours check. Only marketing-category notifications are subject to the block.
What you configure
Disclaimer: Confirm with legal counsel that your organization's marketing send-window meets local regulatory requirements. Zenoti enforces the schedule you configure but does not certify regulatory compliance.
- Go to Configuration > Notifications.
- Confirm the Country is set to France if your organization operates in France. Country determines whether the GDPR quiet-hours rules apply.
- Maintain your organization's holiday calendar so that national holidays are recognized and marketing SMS is suppressed on those dates.
Note: The 8 PMβ8 AM overnight block, the Sunday block, and the holiday block are applied automatically for France-region organizations. They are not user-configurable β the window is fixed by the regulation, not by a marketing send-window setting.
FCC and TCPA β SMS opt-out confirmation
The FCC and Telephone Consumer Protection Act (TCPA) require businesses that send SMS in the United States to send a one-time confirmation message when a recipient opts out of transactional SMS (for example, by replying STOP, UNSUBSCRIBE, or END to any business SMS).
Zenoti provides a single built-in template to satisfy this requirement: the SMS Opt out confirmation message template, found under Customer Opt-in templates. There is no separate "opt-in success" template and these templates do not carry numeric notification-type IDs.
How it works
When a guest replies with a predefined opt-out keyword, Zenoti opts the guest out of marketing text messages across the zone the sending center belongs to β not only from the number they replied to.
- Flags the guest as opted out of marketing text messages for that zone. Subsequent marketing text messages from any center in the zone are suppressed until the guest opts back in.
- Sends the SMS Opt out confirmation message template once, confirming the opt out.
- Keeps the guest's consent state updated in their profile so that opt-in requests from support teams or integrations are handled correctly.
Customizing the opt-out confirmation template
Disclaimer: The default SMS Opt out confirmation message template content satisfies FCC/TCPA opt-out-confirmation requirements out of the box. If you customize the wording, retain the core confirmation semantics required by the regulation. When in doubt, confirm changes with your legal counsel before publishing.
You can customize the wording while keeping the required confirmation semantics.
- Go to Configuration > Notifications.
- Locate the SMS Opt out confirmation message template under Customer Opt-in templates and click Edit.
- Edit the message body. Ensure the wording clearly confirms that the guest has been removed from text-message lists and cannot be messaged further until they re-subscribe.
- Save the template.
Important: Do not disable this template. The FCC/TCPA opt-out confirmation is a regulatory requirement, not a marketing preference. Zenoti sends the confirmation even when a guest has opted out of text messages.
How opt-out keywords work
A guest does not need to reply with a keyword as the entire message body. Zenoti treats a reply as an opt-out if it contains any of the recognized opt-out keywords anywhere in the text β even when the keyword appears inside ordinary free text (for example, "please stop sending me messages" triggers the same opt-out as a bare STOP reply).
The complete list of recognized opt-out keywords is:
| Keyword | Effect |
|---|---|
STOP |
Opts the guest out of marketing text messages across the sending center's zone |
STOPALL |
Opts the guest out of marketing text messages across the sending center's zone |
UNSUBSCRIBE |
Opts the guest out of marketing text messages across the sending center's zone |
CANCEL |
Opts the guest out of marketing text messages across the sending center's zone |
END |
Opts the guest out of marketing text messages across the sending center's zone |
QUIT |
Opts the guest out of marketing text messages across the sending center's zone |
To see which keyword a guest used β and to confirm which opt-out event fired β review the guest's replies in the Guest Replies view within Configuration > Notifications. The view shows the inbound message text alongside the opt-out event it triggered, so you can identify the exact keyword that caused the opt out.
Note: Because keyword matching is substring-based, a guest who writes a conversational reply containing any of the words above will be opted out. If a guest contacts your center to report they were unintentionally opted out, see Opt-out scope and how to restore delivery below.
Opt-out scope and how to restore delivery
An opt-out triggered by a keyword reply is registered against the zone that the sending center belongs to β not against the individual phone number the guest replied to, and not against the guest's profile across your whole organization.
This means:
- A guest who sends a stop keyword is opted out of marketing text messages from every center in that center's zone, not only from the number they replied to.
- The same guest continues to receive marketing messages from centers in a different zone.
- From the guest's perspective this can look inconsistent β they replied STOP but still receive messages from another location. That is the zone boundary, not an error.
How to restore delivery after an unintended opt-out
If a guest wants to resume receiving marketing text messages after opting out, ask the guest to send a recognized opt-in keyword from their own device.
Turning the guest's marketing text-message preference back on in their profile clears the opt-out in exactly the same way, and the product does not prevent staff from doing this. The re-consent requirement is therefore procedural rather than system-enforced β obtain the guest's explicit re-consent before changing that preference, as the note below sets out.
Recognized opt-in keywords that restore delivery:
| Keyword | Effect |
|---|---|
START |
Opts the guest back in to marketing text messages from centers in that zone |
YES |
Opts the guest back in to marketing text messages from centers in that zone |
UNSTOP |
Opts the guest back in to marketing text messages from centers in that zone |
To guide a guest through restoring delivery:
- Ask the guest to send
START(orYESorUNSTOP) as a text message to the number that sent them messages from your center. - Zenoti receives the opt-in keyword, turns the guest's marketing text-message preference back on in their profile, and clears the opt-out for centers in that zone. No further action is needed in the guest's profile.
- Confirm delivery has resumed by sending a test message or checking the guest's consent state in their profile.
Important: Do not attempt to restore a guest's opt-in state by editing their profile directly without the guest's explicit re-consent. Regulatory requirements under the TCPA require that re-consent originate from the guest. Confirm the appropriate re-consent method with your legal counsel.
Tip: If guests at a sibling center still receive messages after opting out elsewhere, check whether the two centers are in the same zone. The opt out covers the zone, so a sibling center in a different zone continues to send. Direct the guest to send
STARTto re-subscribe.
Marketing message send window
The marketing send-window controls govern the hours during which Zenoti sends marketing SMS. They apply globally to the organization, independent of GDPR requirements:
- Marketing SMS scheduled during the window is sent immediately.
- Marketing SMS scheduled outside the window is queued until the window opens, or suppressed per your organization's delivery policy.
- The effective send-window is the intersection of your organization setting AND any mandatory regulatory quiet hours (for example, the France-region Sunday block).
Zenoti does not implement a per-recipient "max messages per day" cap at the organization settings level. Per-recipient frequency control is managed by marketing-campaign targeting rules and by each guest's marketing consent state. See Configure marketing settings for campaign-level frequency control.
Multi-region considerations
Zenoti operates in multiple jurisdictions and routes outbound SMS through region-aware providers. Beyond the France GDPR and US FCC/TCPA regimes covered above, organizations sending SMS in additional regions must address the local regulatory regime. Zenoti's product team and account managers can advise on configuration; help articles do not enumerate per-region steps because the operational requirements (registration, sender-ID, consent records) are typically performed outside Zenoti.
| Jurisdiction | Regulatory regime | What organizations need to do |
|---|---|---|
| India | DLT (Distributed Ledger Technology) registration with TRAI; KYC (Know Your Customer) document submission; sender-ID and template-ID registration with the operator | Contact your Zenoti account manager to confirm DLT enrollment. Provide the registered DLT sender ID. |
| United States (in addition to FCC/TCPA opt-out) | A2P 10DLC carrier registration (brand and campaign registration with The Campaign Registry) | Contact your Zenoti account manager to register your brand and campaigns. Without 10DLC registration, US SMS is unreliable through major carriers. |
| Canada | CASL β express consent + sender identification | Maintain consent records and an unsubscribe mechanism. Confirm campaign content with your legal counsel. |
| Australia | Spam Act 2003 β express or inferred consent + functional unsubscribe | Maintain consent records and ensure each marketing SMS includes an unsubscribe instruction. |
Authoritative sources: For current rules, consult the regulator directly: TRAI (India), The Campaign Registry (US 10DLC), CRTC (Canada), ACMA (Australia). Zenoti staff cannot provide legal advice; this article acknowledges the regimes so that you raise the right questions with your compliance counsel.
Verifying compliance behavior
After configuring compliance settings, verify behavior end-to-end before relying on it in production:
- Test the opt-out flow: Send an SMS to a test number, reply STOP, and confirm that the SMS Opt out confirmation message template is delivered once and that subsequent marketing text messages to that guest are suppressed.
- Test the zone scope: Send an SMS from a second center in the same zone to the same test guest and confirm those messages are suppressed too. Then repeat from a center in a different zone and confirm delivery still succeeds there.
- Test the opt-in restoration flow: From the opted-out test number, reply
STARTand confirm that delivery resumes and the guest's consent state is updated in their profile. - Test the send-window block: Schedule a marketing campaign outside your configured send window and confirm the SMS is delayed until the window opens.
- Test the Sunday block (France only): Schedule a marketing SMS for Sunday at any time and confirm it is suppressed or delayed to Monday.
- Monitor the credit usage dashboard: Opt-out confirmation SMS consumes SMS credit. Include it in your credit forecast. See Monitor notification credit usage.