Technology
Purpose-built technology,
operated as one service.
Vee is not a stack you assemble. The layers exist to run one process, and they are operated together by the same team that owns the outcome.
The stack, from voice to control.
Each layer answers a different question. The process only performs when all of them do.
- 01Conversation layerVoice and dialogue in real time.
- 02Process orchestrationDecisions, states and next actions.
- 03Telephony and connectivityGetting the call through.
- 04Data and integrationsCase status in, actions out.
- 05Analytics and controlVisibility, QA and change.
Six capability areas.
Technology is organised around what the process needs, not around product categories.
Voice AI and conversation
Turn-taking, interruption handling, latency and prosody as performance variables.
LLM and orchestration
Model choice, grounding and deterministic control where risk demands it.
Telephony and connectivity
Reachability, routing, numbers and throughput.
Integrations and data exchange
Connecting contact to case status and downstream action.
Analytics and reporting
Case, interaction, status and outcome visibility.
Operating platform
The layer that runs, monitors and changes the process as one service.
Owned, partnered and open.
A managed service can combine its own technology with partner components and open standards without becoming a stack the client has to run.
Owned technology
Built for the operating model
- LectorUX voice interaction
- Brilliance StateGuard control layer
- DialogJourney dialogue design
- Vee Analytics reporting
Partner technology
Selected per process
- Language models per use case
- Telephony and connectivity providers
- Speech and synthesis components
- Infrastructure and hosting
Open standards
How it connects
- SIP for voice
- REST and webhooks for data
- SFTP and structured files
- Standard identity and access
Control is part of the architecture.
Technology that cannot be explained, versioned and stopped is not enterprise technology.
- Deterministic behaviour where the process touches a customer’s outcome.
- Versioned scenarios, models and content.
- Human escalation as a first-class path through the stack.
MATRIX is a direction, not a badge.
From executing contact to operating customer-contact effectiveness.
MATRIX describes where the platform is heading: customer-journey memory, multi-touch paths, controlled adaptation and outcome-linked insight.
It is presented as a future direction and is not claimed as a blanket current capability. What is live is stated per capability.
Direction of travel
- 01Customer-journey memory
- 02Dynamic multi-touch paths
- 03Controlled adaptation
- 04Insight and decision support
The layers in detail.
Each layer is documented on its own page, with the process it serves.
Connectivity
Visibility
Bring us the process and the systems around it.
We will show which layers carry the performance and which are commodity.