The organisation needed one customer support suite for customers, support agents, and product teams. The existing journey divided email and portal tickets, customer context, queues, SLAs, internal notes, attachments, knowledge articles, known issues, and release communication between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
A complete customer support suite shaped around customers, support agents, and product teams
The organisation needed one customer support suite for customers, support agents, and product teams. The existing journey divided email and portal tickets, customer context, queues, SLAs, internal notes, attachments, knowledge articles, known issues, and release communication between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
Discovery followed the full journey from the first customer or staff action to its operational and commercial close. That exposed the handoffs between support workspace, knowledge base, and service levels, including the exceptions that a feature list would have missed.
- Map the people, decisions, and records across the whole customer support suite.
- Separate firm customer support rules from habits created by the old tools.
- Agree what the first release must complete from end to end.
The product joined support workspace, knowledge base, and service levels without blurring roles
Keep the complete customer conversation in support, connect reviewed product knowledge, and send only bounded engineering context into development work.
In the customer support suite, each audience receives a focused home while the underlying state remains shared. The interface shows what needs attention, who owns the next action, and why work is blocked, while secondary detail stays available for review without crowding everyday tasks.
- Design the primary journey for every audience named in the brief.
- Give exceptions, corrections, and cancellations an explicit route.
- Use realistic records to test the complete flow before widening the surface area.
Angular, ASP.NET Core, PostgreSQL formed one supportable customer support suite
The architecture follows business ownership rather than the navigation menu. Angular, ASP.NET Core, PostgreSQL share versioned contracts, server-side permissions, observable integrations, and one authoritative record for the decisions behind knowledge base.
In the customer support suite, slower or external work runs through durable jobs with idempotent handling and visible failure states. Logs retain the organisation, actor, and product record needed to investigate a problem without guessing from a generic error message.
- Angular supports the primary product surface.
- ASP.NET Core owns a bounded part of the product journey.
- PostgreSQL keeps operational data and handoffs reviewable.
The release had to prove the whole customer support suite, not one polished screen
Customers receive a coherent response and support teams can move from question to diagnosis, knowledge, and resolution in one workspace. The release plan therefore followed representative work across every audience and the complete path through support workspace, knowledge base, and service levels.
Acceptance for the customer support suite included ordinary work, missing inputs, repeated requests, failed integrations, permission boundaries, and the route back to a trustworthy state. The team checked whether staff could understand and recover from a problem without direct database help.
- Run the busiest realistic journey from start to operational close.
- Rehearse a failed integration and a repeated customer action.
- Confirm that every role sees only the work and data it owns.
- Trace a management result back to the records that produced it.
What the work established
Customers receive a coherent response and support teams can move from question to diagnosis, knowledge, and resolution in one workspace.
- 01
The customer support suite now gives customers, support agents, and product teams one shared operating record.
- 02
Support workspace, knowledge base, and service levels follow the same product rules.
- 03
The system makes ownership and exceptions visible instead of hiding them in manual follow-up.
- 04
The product can grow from clear workflow, data, and service boundaries rather than isolated features.