Skip to content
revoq

Consent revocation, end to end

A revocation is only worth as much as the record behind it.

When someone asks what your company did about one specific opt-out, the answer has to be a record, not a recollection. This page describes what that record has to contain and how revoq produces it.

Book a revoq ReviewPlatform overview

The four obligations

Received, verified, delivered, documented

Most opt-out tooling handles the first step and hopes the rest was implied. Each of these is a separate thing you may have to demonstrate.

Received
The request reached a channel you control, with the date, time, and the exact disclosure text the consumer saw captured at that moment — not reconstructed from a later version of your page.
Verified
The number the request is about is confirmed to be reachable by the person making the request. revoq sends a one-time code and records the request as verified only after that code is confirmed.
Delivered
The suppression reached every system that can place a call or send a text: your dialer, your messaging platform, your lead buyers or partners. Delivery is an outbound event with a response, not an internal flag.
Documented
The whole sequence is reproducible later from an append-only record, including the attempts that failed and what the destination said in reply.

Capture

What revoq records the moment a request arrives

  • The phone number in normalized US form, plus the channel scope the consumer chose — calls, texts, or both.
  • The verification event: the one-time code challenge and its confirmation, timestamped.
  • The disclosure version displayed on the branded page at submission time.
  • A reference number the consumer keeps and your team can search on.
  • The website or partner property the request came through, so multi-brand programs stay separable.

Deliver

Delivery states, named honestly

revoq refuses to collapse these into one word. Attempted is not accepted, and accepted under a configured rule is not a legal acknowledgment by the destination.

Queued
The verified request is waiting for its turn at a configured destination.
Delivery attempted
revoq built and sent the request from its own servers.
Response received
The destination replied, and the reply is recorded in sanitized form.
Accepted under the configured response rule
The reply matched the success rule set up for that destination. It is not a legal acknowledgment by the destination.
Inconclusive
A reply arrived but did not match the configured success or failure rule.
Failed
The destination reported an error, timed out, or was unreachable.
Blocked
revoq refused to send — for example a prohibited network target or a paused connection.
Awaiting resolution
An exception is open and a person still needs to close it out.

Destinations are configured as delivery connections — a native connector, a custom suppression API, or a signed developer webhook — and each one has to pass a live test before it can receive real requests. See delivery connections for how routing and fan-out work.

Prove

What a reviewer sees months later

  • A request timeline: submitted, verified, queued, attempted, and the response recorded for each destination.
  • Sanitized destination responses, retained as evidence rather than summarized away.
  • Exceptions that were opened, who resolved them, and when.
  • Exports for a date range, with masked and unmasked variants gated by role.
  • An append-only audit history, including actions revoq support performed on the organization's behalf.

The operational side of this lives in compliance operations.

Questions

Common questions about revocation records

Stay current

Follow the developments that change this

revoq publishes reviewed summaries of agency and court developments affecting consent, revocation, and suppression, written from the primary documents.

Or read all news and updates. These summaries are informational and are not legal advice.

Bring a real request and we will walk its record end to end.

Book a revoq Readiness ReviewWhy revoq