Architecture
Design the operating system, not just the channel
Contact centre architecture now spans CRM, real-time interaction, data, identity, AI, workforce tools and the controls that hold them together.
Start with boundaries
Define which platform owns customer context, interaction state, routing, knowledge, automation and reporting. Ambiguous ownership becomes duplicate data, conflicting workflow and expensive workarounds.
Separate the planes
The experience plane, control plane and data plane change at different speeds. Designing them separately helps teams modernise without tying every decision to one vendor release cycle.
- Experience plane: customer and colleague journeys
- Control plane: policy, routing, identity and orchestration
- Data plane: records, events, analytics and evidence
Design for operations
A sound diagram must become an operable service. Include monitoring, fallback, release ownership, supplier boundaries and the people who will manage exceptions.
Architecture references
Use the reference material to compare platform patterns and prepare better buyer questions.