Service Experience Intelligence · 2026-03
Identity and password flows appear in unresolved interactions.
| Case ID | Customer ID | Date | Source | Evidence |
|---|---|---|---|---|
| SE-001 | ENTITY-0001 | 2026-03-02 | ticket | Recovery link expired twice |
| SE-005 | ENTITY-0005 | 2026-03-13 | survey | Recovery required multiple verification steps |
| SE-001-M010 | ENTITY-0001 | 2026-03-10 | ticket | Recovery link expired twice |
Queue delay is visible in chat evidence.
| Case ID | Customer ID | Date | Source | Evidence |
|---|---|---|---|---|
| SE-002 | ENTITY-0002 | 2026-03-04 | chat | Customer waited during evening peak |
| SE-007 | ENTITY-0007 | 2026-03-21 | call | Queue delay exceeded issue handling time |
| SE-002-M011 | ENTITY-0002 | 2026-03-11 | chat | Customer waited during evening peak |
Use queue-aware routing and proactive wait messaging.
| Case ID | Customer ID | Date | Source | Evidence |
|---|---|---|---|---|
| SE-002 | ENTITY-0002 | 2026-03-04 | chat | Customer waited during evening peak |
| SE-007 | ENTITY-0007 | 2026-03-21 | call | Queue delay exceeded issue handling time |
| SE-002-M011 | ENTITY-0002 | 2026-03-11 | chat | Customer waited during evening peak |
Reduce recovery steps and add contextual guidance.
| Case ID | Customer ID | Date | Source | Evidence |
|---|---|---|---|---|
| SE-001 | ENTITY-0001 | 2026-03-02 | ticket | Recovery link expired twice |
| SE-005 | ENTITY-0005 | 2026-03-13 | survey | Recovery required multiple verification steps |
| SE-001-M010 | ENTITY-0001 | 2026-03-10 | ticket | Recovery link expired twice |
Users request clearer explanations of fees and statements.
| Case ID | Customer ID | Date | Source | Evidence |
|---|---|---|---|---|
| SE-003 | ENTITY-0003 | 2026-03-06 | call | Fee label was not understood |
| SE-006 | ENTITY-0006 | 2026-03-17 | chat | Agent clarified statement terminology |
| SE-003-M012 | ENTITY-0003 | 2026-03-12 | call | Fee label was not understood |