Compliance operations
Answer the question you will actually be asked: what happened to this request?
revoq's console is organized around review, not dashboards for their own sake. Start from a reference number or a phone number and read the whole story in one place.
Request review
One request, one complete history
- Identity of the request
- Reference number, website, brand, and masked phone number.
- What was asked
- The scope the consumer selected and the channels it covers.
- How it was verified
- Verification method, provider, mode, and the time the code was confirmed.
- What was shown
- The published form and disclosure version presented at the time.
- Where it went
- Every connection the request was queued to, with each attempt and reply.
- What is left
- Whether an exception is still open and what a person needs to do about it.
Delivery monitoring
Exceptions are work items, not silent failures
When a destination fails or replies in a way your rules do not recognize, the request stays visible until someone resolves it.
Attempt history
Every attempt with its status, sanitized response, matched rule, latency, and next retry time.
Requeue and retry
An administrator can requeue a request — for example after a connection was fixed or newly activated.
Resolution notes
Closing an exception requires a note, and the note is recorded permanently alongside the delivery.
Connection health
Recent failures, last successful delivery, and whether a connection is paused pending a fresh test.
Change controls
Material changes to a connection pause it and reset its test state, so traffic never silently follows an unverified configuration.
Administrative audit history
Configuration and access events are recorded, including cross-organization access by revoq staff during support.
Status vocabulary
The same words everywhere
Console, review screens, and this site use one vocabulary so nothing gets softened in translation.
- 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.
Access and separation of duties
Who can see and do what
- Administrators configure websites, connections, and team access, and can requeue deliveries.
- Analysts review requests, delivery history, and evidence without changing configuration.
- Tenant isolation is enforced in the database, not only in the interface.
- Full phone numbers are protected in storage; review screens work from masked values.
- revoq staff access to an organization for support is itself recorded as an auditable event.