Governance & consent
One consent state, not another one.
Support intersects with consent in several places: chat, behavioural context, analytics and identity. Resolivo reads the consent state that already exists rather than building a second system that will eventually disagree with the first.
What connects
A read connection to the consent state for a visitor or customer, consulted before any consent-gated capability runs.
What crosses the boundary
- Received: consent state per visitor or customer, by purpose.
- Received: changes to consent, applied immediately.
- Sent: nothing. Resolivo does not record or alter consent.
- Received: the record that consent was checked, for audit.
What this lets you do
- Gate behavioural session context on real consent rather than an assumption.
- Honour a withdrawal immediately across every support surface.
- Evidence that consent was checked before context was shown.
- Avoid a second consent banner on the support widget.
Setting it up
- 1Link the workspaces.
- 2Map purposes to the capabilities they gate.
- 3Confirm behaviour when consent state is unknown — the default is to withhold.
- 4Verify a withdrawal takes effect immediately.
Permissions
Read-only on consent state. Resolivo never records, infers or modifies consent, and treats an absent state as a refusal rather than as permission.
What you can ask once this is connected
- “May I show session context for this customer?”
- “Has this customer withdrawn consent?”
- “Which capabilities are gated for this visitor?”
Where it stops
Reading consent is not obtaining it. Collecting consent, proving it and honouring requests are the consent system's job; Resolivo's obligation is to respect the answer, including when the answer is no.
Governance & consent
Others in this category.
Take better care of every customer.
Give your team the context, knowledge and AI they need to resolve problems properly — and know who needs attention before they ask.
Keep the mailbox you already use · The AI is never metered · [email protected]