L1 · ANALYSIS
Read an interaction
Run any of the eight modules on a transcript, a batch or a period, and get the typed result back with its evidence.
The part of the platform that does something. A finding becomes a task, a call, a message or an escalation, and the doing is logged the same way the reading is.
[01 / THE PROBLEM]
Analysis at full coverage produces more findings than any team can carry by hand. The bottleneck moves from knowing to doing, and doing is where most quality programmes quietly stop.
WHERE FINDINGS GO TODAY
WITH FLOWS
Flows is in build. What follows is the design we are building against, not a description of a shipped feature. The registry and the audit behaviour are settled; the canvas is where the work is.
[02 / ANATOMY]
Every flow is a versioned graph, stored as data rather than as code. Publish a version and it becomes immutable, so a run from March can still be read against the flow that actually produced it.
A schedule, a platform event, an inbound webhook, a spoken question, a manual run, or another flow finishing.
The filter that decides whether this run matters. Team, driver, severity, business hours, tenant holiday calendar.
One entry from the registry. Every action declares its inputs, its outputs, its confidence and how far it reaches.
Anything that affects a named person stops here and waits for a human. The gate is in the registry, not in the flow.
Voice, SMS, email, Slack, Teams, Notion, push or a signed webhook out. One audit entry per send.
A worked example: quality detects an auto-fail on a compliance item, the flow checks it is inside working hours, drafts a coaching plan, holds it for the team lead's approval, and sends it to Slack when they accept. Four steps, one log, nothing sent that a person did not agree to.
[03 / REGISTRY]
The registry is the contract. Each entry names its schema, its blast radius and its idempotency key, which is what stops a retried run from sending the same message twice.
L1 · ANALYSIS
Run any of the eight modules on a transcript, a batch or a period, and get the typed result back with its evidence.
L2 · INTELLIGENCE
Trends, statistical checks, KPI computation, forecasts. Every number carries the interactions it was built from.
L3 · ACTION ENGINES
Coaching plans, training modules, process maps, knowledge articles, drafted against the finding that called for them.
CHANNELS
Voice, SMS, email, Slack, Teams, Notion, push, webhook out. Per-tenant credentials, rate limits and retries.
CRM · TICKETING
Zendesk, Salesforce, HubSpot, Intercom, Freshdesk. Read a record, update a field, open a ticket.
CONTROL FLOW
Conditions, loops, delays, parallel legs and error paths, so one flow can carry a real process.
GOVERNANCE
Constitution actions are first-class: redact before send, request approval, attach the AI disclosure.
STORAGE
Files, exports and reports written to your own storage, with the signed bundle attached.
[04 / VOICE]
REV is the voice surface on the same registry. A manager driving home asks how a team did yesterday and gets an answer computed from the interactions, not read off a cached slide.
01 · ASK
Top driver this week, yesterday's quality by team, where the calibration drift is. The answer comes from a computation the console can show you afterwards.
02 · ACT
Running an analysis or booking a coaching session needs spoken confirmation, and the approval is logged with the call. A2 keeps a low-confidence answer from sounding certain.
03 · CALL BACK
One auto-fail today, the coaching plan is drafted, press 1 to review. The call opens by saying it is an AI, because A7 makes that mandatory rather than polite.
Voice runs on EU telephony, with transcription and speech generation on our own hardware. Nothing about a call has to leave the region it was made in.
[05 / CANVAS]
Three modes on one canvas, because the person who designs a flow and the person who has to explain it later are rarely the same person.
BUILD
The registry is the sidebar. Every node shows what it needs and what it returns, so a wiring mistake is visible before the flow runs rather than after it sent something.
DESCRIBE
"Every morning at eight, run root cause on yesterday's DSAT tickets and email Mike a summary." The nodes drop in, then you correct them by hand. Nothing runs until you publish.
WITNESS
Pick a run from the timeline, watch the executed branch light, open any node for its exact input, output, confidence, prompt and duration. This is the transparency surface, and it is the same data the audit chain exports.
[06 / RAILS]
Every rail below is enforced in the registry, so a flow cannot opt out of one by being written a different way.
4
BLAST RADIUS CLASSES
Read only, internal write, external send, worker affecting. The last one always needs a human.
1
KILL SWITCH PER FLOW
One call disables a flow. Runs in flight land in the dead-letter queue rather than half-finishing.
60
RUNS PER HOUR, BY DEFAULT
A cap you raise on purpose. A misconfigured trigger costs you a log entry, not a phone bill.
0
DOUBLE SENDS
Every action carries an idempotency key derived from its inputs, so a retry repeats the outcome, not the message.
Flows is included with Enterprise and with REVEAL Local. On Professional and Business it is an add-on, with REV voice on a shared number. Platform licences follow the standard models · the full model table lives on the platform page, and pricing happens on a call with your own numbers.
[07 / CONSOLE]
Open the console.The analysis Flows acts on is live today. Walk the modules, then tell us which finding you would want carried to someone automatically.