Notification Preferences
Members have separate preferences for Email, SMS, and Voice notifications. A notification attempt is eligible only when its rule enables that channel, the Member's channel preference is on, the notification source is subscribed, and the Member has a usable contact for it. Provider acceptance or delivery is not guaranteed. These preferences govern notifications; they are not permission to contact a member for unrelated outreach.
How It Works
All of these checks must pass for a send attempt:
| Check | Required state |
|---|---|
| Rule or notification channel | Enabled |
| Member's channel preference | On |
| Member's subscription to this source | On |
| Contact details for the channel | Usable |
If any check fails, that delivery is skipped.
Email needs an email address, SMS needs a phone that can receive texts, and Voice needs a phone number. An eligible attempt can still fail at the provider or carrier. Voice notification calls are not yet available; see Notifications for channel availability.
Change a Member's Preferences
- Open Members.

- Select a member, then open the Details tab.

- In Notifications, turn Email, SMS, or Voice on or off, then choose Save changes.

- Confirm the saved preferences on the member details page.

A channel without a usable contact cannot be enabled in the form. If a previously enabled preference becomes unreachable after contact details change, the form shows a warning and keeps the stored preference so you can turn it off. The send-time gate skips an unreachable channel without clearing that preference.

Stop One Notification Source
A notification email shows which Action or Routine triggered it. Choose Manage / unsubscribe from this notification, then confirm Unsubscribe. Opening the link alone does not change your preference.
This stops that source for you across email, SMS, browser push and the notification inbox. It does not stop other sources or change another recipient's preferences. You can unsubscribe even if someone else created the Action.
Open Membership and find Notification subscriptions to subscribe again. Turning a subscription on still respects your separate channel preferences. Workspace admins also see Edit Action and, for Routine notifications, Edit Routine. Those links open the source with its normal access checks.
CSV Imports and Defaults
When importing members, include notify_sms, notify_email, and
notify_voice columns to set explicit preferences. See
Importing Members for the CSV format.
Defaults depend on how the Member is created. The Members form shows text and voice on once a phone number is entered, and email on from the start. An import that leaves those columns out turns email on, and turns text and voice on when the row's phone number is that member's own. A number someone else already holds stays an extra contact and does not turn voice on. A workspace that records enrollment consent can turn voice on without a phone. A value you set is kept. Changing a phone number or email address later does not change a preference already saved. A phone number does not by itself mean it can receive text. Voice calls reach any kind of line.
SMS Keyword Opt-Out
When a Member texts STOP to a workspace number, that workspace's SMS notification preference is turned off. When the sending brand can be resolved, SMS from that brand is also suppressed until the Member texts START. Turning the preference back on does not clear STOP suppression; a STOP to one brand does not opt the Member out of every sender. See Phone & Voice for keyword details.
A texted STOP also stops the AI phone calls your automations place, because under US rules opting out by text also opts a Member out of automated calls. A call your staff place is not blocked. Texting START lifts it.
For event, workflow, and recipient selection, see Notifications.
Spoken Opt-Out on a Call
Add Contact Opt-Out to a Workflow or Task to use the standard spoken opt-out flow on phone calls. This ability is optional and is never added automatically. You can use your own contact-preference flow instead. Existing Workflows do not receive this ability automatically. Without it, the AI receives no standard spoken opt-out tools or instructions. Your Workflow must provide the contact-preference flow you choose.
With the ability enabled, when a caller asks not to be contacted again, the AI records the request right away and reads a fixed confirmation. For the caller's phone number in this workspace, the request:
- turns off the Voice, SMS, and WhatsApp preferences of the Members with that number. Email is unchanged.
- records a stop for calls and texts on the Contact consent record. Like a texted STOP, it blocks the AI phone calls and automated texts your automations send to that number. A call your staff place is not blocked.
If the caller says on the same call that it was a mistake, the AI cancels the request. The stop no longer applies, and the preferences it turned off come back on, unless another stop for that number, such as a texted STOP, still applies. Once the call ends, the request stands. If the call was part of a workflow, the Member's Assignment ends when the call does.
Members → Contact consent lists each request as "Recorded by the Agent on a call" and "Pending review · In effect": the stop already applies. A request the caller cancelled is marked "Retracted by caller on the call" and "Not in effect".
CRM Opt-Outs
If your team records opt-outs in HubSpot or Salesforce, a sync rule can turn off the matching channel in Gravity Rail on the next inbound sync. CRM sync only turns channels off; changing the value back in the CRM does not turn a channel on. See HubSpot Sync and Salesforce.
SMS sender restrictions
Below Notifications, SMS sender restrictions lists the workspace phone numbers a Member cannot receive SMS from because of a provider opt-out. It shows each phone number and its brand. These restrictions still apply when the Member's SMS preference is on. A missing or unreadable sender status appears as unavailable. Viewing this panel requires permission to read Members and workspace phone numbers.
Related
- Escalation & Human Handoff — Configure who gets notified on escalation and which channels to use
- Routines — Run automated actions on a schedule, such as reminders and recurring reports
- Actions — Trigger automated tasks based on events
- Members — Add, edit, and manage workspace members
- Members API — Update the notification preference fields programmatically