Most stuck claims weren’t system failures. They started with missing details.
My first research, before I had the title. As a Research Analyst supporting a U.S. healthcare clearinghouse, I looked past individual tickets to ask why some customers kept raising them, and found the problem usually began long before the claim.
The contextClaims stuck between hospitals, insurers and patients
COVID-19 hit just as I started. Inquiries surged. Payments and claims moving between hospitals, insurance companies and patients were getting stuck, and my day-to-day work was claims support: tracing why a claim had stalled across different portal systems, and keeping customers updated.
Solving tickets one by one wasn’t going to reduce them. So I started asking a different question.
Why do some customers raise many tickets, while others never raise one?
What I didFrom thousands of tickets to a research report
What I foundThe ticket was the last step, not the first
Most tickets traced back to errors or gaps in customers’ details, often months before the claim was made.
Two paths that ended in a stuck claim
What happenedSmall fixes, and a bigger change for me
- My manager and team passed the findings to the client. A few statuses were changed in the CRM we used, and there were discussions on how customers should be kept updated.
- Alongside this, I trained new team members with process and tools questionnaires, Q&A sessions and one-to-one remote sessions.
The frustration I heard in customers’ voices came less from the people and more from unclear information and broken processes. I wanted to fix those at the root, so I took UX research courses and moved into UX research.
Reconstructed from memory. The client and data are anonymised, with no figures beyond what I recall.