Layer 1
Voice runtime
Answers the phone. Any voice platform that suits your line, swappable later.
RoomsTelephonyWebhooks
Platform
One layer between your calls and your systems.
Voice platforms change. Your customer data already has a home. CloaFlow sits in between and keeps the work moving.
Architecture
Three layers. Each has one job.
Mixing runtime events, business data and review decisions is how voice projects get brittle. We keep them apart.
Layer 2
CloaFlow
Keeps the index of what happened, what needs a person, who owns it and what they decided.
Review queueOwnersAudit trailSource links
Layer 3
Your systems
Your CRM, ERP and order tools stay the record for customers, prices and stock.
CustomersOrdersPolicies
Data
What we keep, and what stays with you.
CloaFlow keeps
- What happened on each call
- Requests and the fields that are missing
- Owners, notes and decisions
- A link back to the source record
Stays in your systems
- Full customer and account records
- Prices and stock levels
- Call recordings and audio
- Anything the agent doesn't need to do its job
01
Calls, not runtimes
The model is built around calls and requests, so the voice stack can change underneath.
02
Links over copies
Sensitive detail stays at the source and loads only when someone authorised opens it.
03
People decide
Review state lives apart from what the agent did, so no decision is automatic.
04
Nothing silent
From capture to done, every change leaves a trace your team can read.
Rollout
Start narrow. Prove it. Widen.
One or two call types first, real calls in a pilot, then more once the review queue behaves.