On this post
Key takeaways
| Stage | What this looks like | Signs you’re here |
|---|---|---|
| 1. Multichannel support | Multiple support channels operate independently. |
|
|
How to move from Stage 1 to Stage 2: Connect channels under a single, unified inbox |
||
| 2. Connected omnichannel support | Integrated customer-facing channels allow context to travel with the customer. |
|
|
How to move from Stage 2 to Stage 3: Use AI to build an intelligence layer between your knowledge systems |
||
| 3. AI-native omnichannel support | A unified integration architecture, enabled by AI, connects all customer-facing and internal channels. |
|
Lorem Ipsum
| Mode | Type | Purpose | Example |
|---|---|---|---|
| Operational (backward-looking) | Descriptive | Summarizes what happened across support interactions. | Average response time dropped from 8 hours to 3 hours after a new triage workflow was introduced. |
| Diagnostic | Explains why a specific outcome occurred. | A spike in ticket volume traces back to a specific product release that introduced a bug in the onboarding flow. | |
| Strategic (forward-looking) | Predictive | Forecasts what is likely to happen based on data patterns. | Declining sentiment scores across three consecutive tickets from an enterprise account signal elevated churn risk ahead of renewal. |
| Prescriptive | Recommends what to do about it based on what the data is saying. | An at-risk account triggers an automated alert that is routed to the CSM, including context and recommended next steps, before the customer escalates. |
| Reactive CXA | Proactive CXA |
|---|---|
| 1. Ticket submitted | 1. Customer searches for an answer |
| 2. Routed to a team | 2. AI intercepts the query and serves a verified, knowledge-grounded response |
| 3. Agent searches for context | 3. Ticket never submitted |
| 4. Wrong documentation surfaces | 4. For tickets that do come through, AI surfaces the right context at case creation |
| 5. Escalated or resolved | 5. Agent resolves faster, with fewer handoffs |
| 6. Knowledge base stays static | 6. Every interaction feeds back into knowledge base gap detection |
| 7. Support leader reacts to trends | 7. Intelligence signals surface churn risk and sentiment shifts in real time |
