Consumer experience

A short, honest opt-out that a person can finish in under a minute.

The consumer flow is deliberately plain: no account, no marketing upsell, no hidden steps, and no promises revoq cannot keep on your behalf.

The flow

Four screens, in this order

Enter a US mobile number. The page shows the company's name and what the request covers before anything is submitted.
Confirm the one-time code sent to that number. This is how revoq establishes that the person making the request controls the number.
Choose what to stop — marketing calls, marketing text messages, or both — within the channels that company has enabled.
Receive a reference number on screen. It identifies the request in the company's records if the consumer follows up later.

Design choices

There is nothing to sign up for. The one-time code is used to verify the number for that request and nothing else.

The flow asks for a phone number and a scope selection. It does not ask for a name, address, or account number to process a request.

The consumer sees the specific channels being stopped, in the company's own branding, with the disclosure text that company published.

Labelled fields, keyboard operation, visible focus, and error messages that say what to do next.

The same flow runs on a revoq-hosted page or inside the company's own site, restricted to domains that company approved.

If verification cannot be completed, the consumer is told plainly rather than shown a false confirmation.

What is recorded

Everything below is captured at the moment it happens, and is not editable afterward.

Reference number: The identifier shown to the consumer and used in the company's records.
Masked phone number: Displayed and reported in masked form; the full number is protected in storage.
Verification: The method, provider, and exact time the one-time code was confirmed.
Selected scope: Calls, texts, or both — exactly as the consumer chose it.
Presented version: Which published form and disclosure version the consumer actually saw.
Request source: Whether the request came from the hosted page or an embedded placement, and on which website.