Staying compliant: TCPA, opt-outs, and quiet hours best practices
How SAMI keeps outbound automation TCPA-safe with locked opt-outs, quiet hours, and A2P registration.
Outbound calling and texting comes with real legal obligations. SAMI builds the most important TCPA guardrails directly into your bots, your outcomes, and your messaging setup so the safe path is also the default one.
How SAMI locks the compliance backbone
When a SAMI Bot can place outbound calls, SAMI takes control of the enrollment actions for every call outcome — and you can't remove them. Cancel, pause, and "do not contact until" are locked per outcome and re-applied automatically when you publish, so a hot transfer always stops the cadence and a deferred lead is always paused until the time they asked for.
The most important lock is the Opt-Out outcome. When a lead asks to stop, SAMI applies do-not-contact on all channels, which suppresses calls, texts, and emails for that contact. This lock is universal: it applies whether a bot is outbound or inbound-only, because honoring an opt-out is an organization-wide TCPA obligation, not a per-bot setting.
Do-not-contact on all channels for an Opt-Out is mandatory and permanent. Don't lift it unless the lead re-engages and clearly re-consents — and never wire a new channel into a cadence as a way around it.
Open any bot from SAMI Bots and review the Outcomes section to see exactly what fires for each disposition. You can layer on extra actions — a note, a tag, a notification — but the locked enrollment and opt-out actions stay put.
Quiet hours: calls and callbacks stay inside the window
SAMI keeps outreach inside an allowed time window so you're not dialing or texting leads at 11 p.m. For v1, callback hours are fixed at 8 a.m.–8 p.m. in your organization's timezone, and your bots will only agree to schedule a callback inside that window. A lead who asks for a 6 a.m. call gets booked for a compliant time instead.
Set your organization's timezone correctly so the 8 a.m.–8 p.m. window lands on your leads' local clock. You can review delivery and callback behavior in each bot's editor under SAMI Bots.
Keep consent and deliverability clean with A2P
Carrier rules (A2P 10DLC) decide whether your texts get delivered at all. Registering your brand and campaign keeps messages flowing and demonstrates you're sending with consent.
Open SMS compliance
Go to SMS compliance in Settings. Only organization owners can manage A2P registration.
Submit your business information
Complete the brand details — legal business name, business type, EIN or tax ID, address, and contact info. SAMI creates the messaging service and registers your brand from this one guided flow.
Register your campaign
Add your campaign details describing how you message leads. SAMI saves the campaign while the brand is in review, then submits it once the brand is approved.
Check status before sending at scale
Use the refresh action to pull the latest brand and campaign status from the provider. Confirm the brand is approved and the campaign is verified before running large sends.
Keep message templates in Templates clear and truthful, and make sure contacts have opted in where required. Clean consent plus an approved campaign is what protects your deliverability long term.
When a lead replies or opts out, pair these guardrails with a workflow that pauses automation so a person owns the live thread. You can build that in Workflows, and watch conversations land in your Inbox.
Related articles
Last updated 2026-06-21