People & authority
Consent is read, never assumed.
Whether a contact may be emailed for marketing, called, or identified individually from website behaviour — read from your consent system at the point of use, per channel. An absent or unreadable state is treated as a refusal, and no agent can override it.
What connects
Your consent management platform, through its API.
What crosses the boundary
- Into the platform: the consent state relevant to the channel being used.
- Out of the platform: nothing. This platform records no consent of its own.
- Never: writing or inferring a consent state.
What this makes possible
- Decides per channel whether a contact may be engaged at all
- Gates individual-level website intent behind the visitor's own choice
- Applies a withdrawal immediately across every motion
Setting it up
- 1Authorise a read-only connection.
- 2Map each channel to the consent category that governs it.
- 3Confirm the behaviour on an unreadable state — refusal is the default and cannot be changed to permit.
Permissions
Read-only. We do not request the ability to record, alter or infer consent. Your consent system remains the only place a person's choice is held.
Where it stops
The platform stores no consent state of its own — it reads yours, per use. If your consent system is unreachable, the channels that depend on it refuse rather than proceeding on a cached answer. Failing open is not a configuration option. A withdrawal takes effect at the next read, which is immediate rather than on a schedule.
People & authority
Others in this category.
Make sure every opportunity gets a next action.
Let AI handle the repetitive engagement, keep follow-up moving, and bring your team in when a customer needs a real conversation.
Agents identify themselves on every call · Nothing commits without you · [email protected]