Custom Software · 6 min read
How I Built a Case Management System for a Service Team
A caller follows up on an open case. Their last email is in one inbox, the call recording is somewhere else, and the case status is in a spreadsheet. The person answering has to reconstruct the story before they can help. I built a case management system for the Consumer Protection Forum so that history could travel with the case.
By David Amagid ·
The design in brief
Give the team one place to see a person's history, a separate record for each case, and an advisor workspace that carries the context forward. Build the handoff into the system, so the next person can see what happened and what needs their attention.
Start with the first call and follow it through
The Forum was working across phone calls, email, contact lists, and spreadsheets. I designed the workspace around the path a request takes through the organization. Staff can find the person, review previous contact, and follow the case without piecing together the same history each time.
Email and WhatsApp are available inside the workspace. Staff can review an email thread and associate it with the relevant case. The document workflow can also prepare a Google Drive upload from the same workspace. Each integration is useful because it supports a specific step in the team's work.
Give the person and the case different jobs
A person can get in touch more than once, and each request can be at a different stage. The contact record holds the relationship history, including calls, emails, and documents. The case holds the details of the current request, including its status, related people, advisor, and files.
That separation gives staff two ways in. They can start with the person when someone calls, or open the case directly when they already know which request needs attention.
Give advisors a workspace for their own cases
I built a dedicated portal where advisors can find their cases and filter them by status. Inside a case they can listen to a recording, read the transcript, work with documents, add notes, and update the status. The information they need for follow-up is available when they open the case.
The main workspace and the advisor portal serve different jobs. The main team needs the wider picture across contacts and requests. The advisor needs enough context to act on the cases assigned to them. That difference is worth designing for early because it shapes both the screens and the permissions.
Use AI to help staff review intake
The system uses AI to transcribe recordings, summarize inquiries, and group them by topic. Staff can go back to the original conversation when a summary needs checking. They still decide how to handle the case.
I would start with this kind of task on similar projects. It has a clear input, and a staff member can compare the output with the source. The case workflow still gives the team a place to do the work and record the next step.
What I would map before building a similar system
Walk through one ordinary case with the people who handle it. Follow the request from first contact to closure, and write down what each person needs to know at the moment they take over. These are the three questions I would start with.
- Which details belong to the person, and which belong to this case?
- Who owns the next step, and what information needs to go with the handoff?
- Which channel or document workflow should connect first, based on where the team does the most manual work?
Questions to ask about a custom case management system
When is a custom case management system worth considering?
Consider it when the same request regularly moves across people, channels, and tools, and staff repeatedly rebuild its history. Map that path first. The map will tell you whether your current CRM can support it or whether you need a dedicated workspace.
What should the first version cover?
Pick one case type and cover intake, the contact and case records, assignment, and status updates through closure. Use that path to check who needs access to which information before adding more case types or integrations.