> For the complete documentation index, see [llms.txt](https://docs.aloop.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aloop.icustomer.ai/plays/guardrails-and-suppression.md). # Guardrails and suppression The platform rules every play inherits: one cadence per contact, suppression above everything, honest counts, and a kill switch. Every play inherits the same platform rules. None of them are per-play options to remember; they are the floor. ## One active cadence per contact A person is in at most one active outreach cadence at a time, across all plays. When two plays want the same contact, priority arbitration decides and the other play waits, so nobody gets three sequences from three motions in the same week. This is enforced at the platform, not promised by configuration. ## Suppression overrides everything Your suppression list is absolute: it beats play logic, autonomy grants, and enthusiasm. Suppressed records are excluded before anything reaches a destination, and suppression flags travel with your data into every channel. Existing customers, opted-out contacts, do-not-touch accounts, once suppressed, no play argues. ## Consent and scope A record goes to a channel only with the identifier *and* the consent that channel requires: email consent for outbound, platform-appropriate hashed identifiers for ads. No consent, no send, silently and every time. ## Your CRM is protected Plays update records; they never overwrite sales-owned fields, never reassign ownership (they alert, you route), and never delete. Merges and other irreversible moves surface as proposals for a human. See [Identity](/audience/identity.md). ## Honest counts Match rates are reported as **matched**, what the destination actually accepted, never as uploaded. If a channel matched 60 percent of a cohort, you see 60 percent. ## Caps and the stop Spend and volume caps bound every play, and pausing or stopping is immediate, from the play, from chat, from a pulse. Stopping a play never deletes its history: the runs, decisions, and outcomes stay on the record. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.aloop.icustomer.ai/plays/guardrails-and-suppression.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.