Opt-outs, time windows, and frequency limits are enforced in code — not delegated to the AI's judgment. If compliance intercepts a message, the AI never sees it.
When a contact sends STOP, the opted_out flag is set permanently in the database with a timestamp. That record is never deleted — its existence is the proof that prevents re-messaging.
Time window and frequency rules are enforced in code on every message — no manual monitoring required. The platform handles Australian Spam Act requirements automatically.
Conversations with no contact activity for 7 days are closed automatically. No follow-up is sent after the window expires — the contact is treated as disengaged.
How it works: Measured from the last inbound message, or last outbound if no inbound exists.
Non-opt-out messages are blocked after 30 days from the last contact activity. Only opt-out responses can be received after the window — no outbound is permitted.
How it works: Both windows enforced in code before any AI call — not left to AI judgment.
Outbound bump frequency is controlled by the campaign's bump_intervals array. The scheduler will not enqueue further bumps once the cap is reached — contacts are never over-messaged.
How it works: max_bumps derived from array length — no separate field to keep in sync.
Every compliance check — whether it passes or intercepts — writes an audit log entry with contact ID, check type, outcome, matched keyword, and timestamp. Exportable as CSV.
How it works: Required for regulatory inspection. Available to client admins from the operator platform.
We'll walk you through a live campaign — opt-outs, windows, and audit log included.