Contact centre
Five deployables across three generations, all over the shared ContactCentre database.
Recommendation
Converge on the generation 2 pair, give the ContactCentre database a named owner (stage 4), and retire the earlier generations as their remaining traffic moves.
The family
| Repo | Role | Health | Entanglement | Note |
|---|---|---|---|---|
| phenix-contact-centre-wcf | Retire | 29 · red | kernel | First generation, WCF |
| phenix-contact-centre-web | Retire | 47 · red | kernel | First generation web |
| phenix-contact-centre-api | Consolidate | 50 · amber | loosely attached | Second generation, dormant since 2024 |
| phenix-contact-centre-2-api | Survivor | 39 · red | kernel | Current generation API |
| phenix-contact-centre-2-web | Survivor | 54 · amber | kernel | Current generation web |
| phenix-contact-api | Review | 79 · green | kernel | Overlapping contact API over the same database |
Actions
Consolidate phenix-contact-centre-api into the surviving contact centre path
Second generation, dormant since 2024. Converge on the generation 2 pair, give the ContactCentre database a named owner (stage 4), and retire the earlier generations as their remaining traffic moves.
Impact: Removes a duplicated capability
proposedRetire phenix-contact-centre-wcf
First generation, WCF. Part of the Contact centre consolidation: Converge on the generation 2 pair, give the ContactCentre database a named owner (stage 4), and retire the earlier generations as their remaining traffic moves.
Impact: A migration never paid for, a pipeline decommissioned and an attack surface removed
proposedRetire phenix-contact-centre-web
First generation web. Part of the Contact centre consolidation: Converge on the generation 2 pair, give the ContactCentre database a named owner (stage 4), and retire the earlier generations as their remaining traffic moves.
Impact: A migration never paid for, a pipeline decommissioned and an attack surface removed
proposed