Consent revocation and compliance operations
Make every marketing opt-out count.
Consumers ask to stop marketing calls and texts in a dozen scattered ways. revoq gives your company one accountable place to receive that request, verify the phone number, deliver it to the systems you choose, and keep the record that shows what happened.
Interactive demonstration
See how revoq works
A consumer verifies their phone number, chooses what to stop, and receives a reference number. revoq records the request and securely delivers it to the systems your business already uses.
Verify
The consumer confirms control of the phone number with a one-time passcode.
Revoke
They choose phone calls, text messages, or both.
Deliver
revoq records the verified request and sends it to the business's configured destination.
Preview of the consumer experience
Stop marketing calls and texts
Reference DEMO-2K4F-8QX1 · fictional example
The demo is a simulation. No text message is sent and no opt-out request is submitted.
The problem
An opt-out that is never proven is an opt-out that never happened.
Requests arrive through forms, agents, replies, and inboxes. They land in different systems, get recorded differently, and are hard to reconstruct later. When someone asks what your company did about a specific request, the answer is usually assembled by hand.
- Requests are captured in one place per website, brand, and channel — not spread across ad-hoc forms.
- Every accepted request carries evidence that the phone number was verified before it was recorded.
- Delivery to your downstream systems is attempted from revoq's servers, with the reply written down as it came back.
- Exceptions surface as work to finish, instead of quietly failing.
How revoq works
Receive. Verify. Deliver. Document.
Four steps, each with its own record. Nothing is inferred after the fact.
Receive
One request path per website and brand.
Publish a hosted opt-out page or embed the experience in your own site. Each website has its own configuration, allowed channels, and disclosure text.
Verify
A one-time code proves control of the number.
The consumer enters a US mobile number and the code sent to it. revoq records the verification method, provider, and time — and rejects a submission that was never verified.
Deliver
Requests go to the systems you connect.
revoq sends each verified request to your suppression API or webhook, applies your field mapping, retries on failure, and keeps a full attempt history.
Document
An append-only trail your reviewers can read.
Reference number, timestamps, selected scope, sanitized destination responses, and every configuration change that affected delivery.
Built for the people who answer for it
Compliance, marketing, and engineering see the same record.
Compliance and legal
Marketing and operations
Engineering
Plain-language delivery status
revoq does not confuse attempted with accepted.
Every delivery lands in one of these states, and each state means exactly what it says.
- 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.
See revoq against your own opt-out workflow.
A readiness review walks through how requests reach you today, what your systems expect, and what a verified record would look like in your environment.