Contents
Listen to any insurance contact centre for an hour. Count the calls. You will hear the same question, asked dozens of different ways:
"Where's my claim?"
"Has my document been received?"
"When will I get my payout?"
"What's happening with my case?"
These status enquiries represent 30-50% of inbound call volume for most insurance operations. They require no expertise to answer. They consume handler time that could go to complex cases. And they frustrate customers who would rather check themselves than wait on hold.
This is the highest-value automation opportunity in insurance customer service. Not because the calls are difficult, but because there are so many of them.
The Anatomy of a Status Call
Before automating status enquiries, understand what actually happens during these calls.
Identity verification takes 60-90 seconds. Policy number, name, date of birth, postcode. The handler confirms the caller is who they claim to be before sharing any information.
System lookup takes 30-60 seconds. The handler navigates to the claims system, finds the right record, and reviews the current status.
Status explanation takes 60-120 seconds. The handler translates system status codes into plain language. "Your claim is with our assessment team" or "We're waiting for the third party's insurer to respond."
Follow-up questions add another 60-120 seconds. "How long will that take?" "Is there anything I can do to speed it up?" "Who should I contact if I don't hear back?"
Total call time: 4-6 minutes for information that could be displayed on a screen in seconds.
Multiply by hundreds of daily calls. The waste is staggering.
Why Customers Call Instead of Self-Serving
If status information could be delivered faster through self-service, why do customers call? The reasons reveal what self-service must overcome.
They do not know self-service exists. Many insurance operations have customer portals that show claim status. Usage is typically dismal. Customers forget they have an account. They cannot remember login credentials. They do not think to check before calling.
The portal experience is poor. Insurance portals often require desktop browsers, complex authentication, and navigation through multiple screens. Customers on mobile devices (which is most of them) face friction at every step.
Portal status is unclear. System status codes like "In Progress" or "Under Review" tell customers nothing useful. Without context, customers call to ask what the status actually means.
They want reassurance, not just information. Sometimes "where's my claim?" really means "is everything okay?" or "have you forgotten about me?" A status code does not provide emotional reassurance. A conversation does.
Self-service that actually works must address all of these barriers.
Chat and WhatsApp: The Self-Service Channels That Work
The solution is not a better portal. It is meeting customers in channels they already use, with interfaces that feel natural.
Why Chat Works
Web chat requires no login, no app download, no remembered credentials. The customer clicks a button and starts typing. Friction approaches zero.
Chat handles the status enquiry flow naturally:
- Customer asks about their claim
- AI asks for policy number or claim reference
- AI verifies identity with security questions
- AI retrieves and explains current status
- AI answers follow-up questions
The entire interaction takes 90 seconds instead of 5 minutes. The customer gets immediate answers. No hold time. No callbacks. No frustration.
Why WhatsApp Works
WhatsApp has 2 billion users. Your customers already have it installed. They already know how to use it. They already check it dozens of times daily.
A WhatsApp message asking "what's happening with my claim?" feels more natural than calling a phone number or logging into a portal. The response arrives as a notification. The customer can read it whenever convenient.
WhatsApp also enables proactive updates. Instead of waiting for customers to ask, send status changes automatically. "Your claim has moved to the assessment stage" arrives before the customer thinks to check.
Why These Channels Beat Portals
Traditional customer portals suffer from a fundamental problem: customers must remember they exist and choose to use them. That choice requires effort: finding the URL, logging in, navigating to the right section.
Chat and WhatsApp invert this dynamic. The customer reaches out through familiar, frictionless channels. The AI handles everything else. No accounts. No passwords. No navigation.
The result: dramatically higher adoption and dramatically lower call volume.
Building the Status Enquiry Flow
Effective claim status self-service requires more than a chatbot that reads database fields. It requires thoughtful conversation design.
Identity Verification
Before sharing any claim information, verify the caller's identity. This is not optional. Regulatory requirements and basic security demand it.
A typical verification flow:
AI: "I can help you check your claim status. First, can you give me your policy number or claim reference?"
Customer: "My policy is ABC123456"
AI: "Thanks. For security, I need to verify some details. What is the postcode on your policy?"
Customer: "M1 2AB"
AI: "And your date of birth?"
Customer: "15th March 1985"
AI: "Perfect, I've verified your identity. Let me check your claim status."
This takes 30-40 seconds via chat. Faster than the phone equivalent, and the customer does not wait on hold first.
Status Translation
Raw database status codes mean nothing to customers. "CLM_STAT_04" is useless. Even supposedly human-readable statuses like "In Progress" or "Pending Review" are too vague.
Effective status responses include:
- What stage the claim is at in plain language
- What is currently happening (who is doing what)
- What happens next (the next step in the process)
- Expected timeline (when something should happen)
- Any blockers (if the customer needs to do something)
Compare these responses:
Bad: "Your claim status is: Under Review"
Good: "Your claim is currently with our assessment team. They're reviewing the damage report from the garage. We expect their assessment to be complete within 2-3 working days. Once that's done, we'll contact you with next steps. You don't need to do anything right now."
The good response takes more words but answers the real question: what is actually happening with my claim?
Handling "I Need to Speak to Someone"
Not every status enquiry can be fully resolved by AI. Some customers want human contact regardless of what the AI says. Some situations genuinely require human judgement.
Build explicit paths for these cases:
Escalation triggers:
- Customer explicitly requests human agent
- Claim has been in same status for extended period
- Claim involves injury or significant dispute
- Customer expresses frustration or distress
- Status indicates exception or problem
Warm handoff: When escalation is needed, transfer context with the customer. The human agent should see everything: the conversation so far, the claim details, the customer's apparent concern. No cold transfers. No repeated explanations.
Proactive Status Updates
The best status enquiry is one that never happens. If customers receive updates before they think to ask, they do not need to check.
Configure automatic updates for key status changes:
- Claim received and being processed
- Claim assigned to handler
- Additional information needed (with clear instructions)
- Assessment scheduled or completed
- Decision made
- Payment initiated
- Payment completed
Send these via the customer's preferred channel. WhatsApp for those who have opted in. SMS for others. Email as fallback.
Proactive updates do not just reduce inbound volume. They improve customer experience. Customers feel informed and cared for rather than forgotten.
Integration Requirements
Self-service status checking requires integration with your claims management system. The AI needs real-time access to:
- Policy data for identity verification
- Claim data for status information
- Document data to confirm receipt of submissions
- Timeline data to provide expected dates
- Handler data to route escalations appropriately
This integration must be read-only for security. The AI can retrieve information but cannot modify claim records (except for logging the interaction).
If your claims system has an API, integration is straightforward. If it does not, screen scraping or database queries may be necessary. Either way, the integration project is finite and the returns are substantial.
Measuring Impact
Deploy status self-service and measure ruthlessly. The metrics that matter:
Deflection Rate
What percentage of status enquiries are fully resolved by AI without human involvement? Target 70-80% for straightforward status checks. The remaining 20-30% involves genuine complexity or customer preference for human contact.
Resolution Time
How long does the average status enquiry take via self-service versus phone? Self-service should be 3-4x faster. If it is not, something is wrong with the conversation design.
Customer Satisfaction
Survey customers after self-service interactions. Are they satisfied with the experience? Would they use it again? Low satisfaction indicates problems to fix: unclear status explanations, frustrating verification, or missing information.
Call Volume Reduction
Track total inbound call volume before and after deployment. Isolate status enquiries specifically if possible. A successful implementation should show measurable reduction within weeks.
Repeat Contact Rate
Do customers who use self-service call back about the same claim? High repeat contact rates suggest the AI is not providing complete information. Customers check via chat, do not get what they need, and call anyway.
Common Pitfalls
Implementations fail for predictable reasons. Avoid these mistakes:
Hiding the Channel
Self-service only works if customers find it. Prominent placement matters. Chat widgets should be visible on every page of your website. WhatsApp numbers should appear on policy documents and email signatures. Every phone IVR should mention the option.
Requiring Login
If customers must log in before chatting, usage collapses. Identity verification during the conversation is sufficient. Do not add unnecessary friction.
Providing Useless Status Information
"Your claim is being processed" tells customers nothing. If your AI cannot explain what is actually happening, customers will call to ask. Invest in status translation logic.
Ignoring Emotional Needs
Status enquiries often carry emotional weight. The customer is not just asking for information; they are worried, frustrated, or anxious. AI responses should acknowledge this. "I understand waiting for news about your claim can be stressful" costs nothing and matters to customers.
Making Escalation Difficult
Some interactions need humans. If customers cannot easily reach a person when needed, they become frustrated with the entire self-service experience. Clear escalation paths protect both customer satisfaction and AI reputation.
The Compound Effect
Reducing status enquiry volume has effects beyond the calls themselves.
Handler capacity increases. Every status call not taken is capacity available for complex work: disputed claims, complaints, exceptions that require judgement. Your most skilled handlers stop spending time on "your claim is in progress."
Wait times decrease. Fewer total calls means shorter queues for calls that do come through. Customers reaching humans get faster service.
Customer satisfaction improves. Instant status access feels better than hold queues. Proactive updates feel better than wondering. The overall perception of your service quality rises.
Costs decline. Fewer calls, shorter calls, lower cost per interaction. The savings fund further improvements or drop to the bottom line.
These effects compound. Better service leads to better retention. Lower costs enable competitive pricing. The status enquiry automation project pays for itself and keeps paying.
Starting the Implementation
Begin with the simplest, highest-volume status enquiry: "where's my claim?"
Configure chat and/or WhatsApp with:
- Identity verification flow
- Claims system integration
- Status translation for your most common claim states
- Escalation path to human handlers
- Basic analytics
Deploy to a subset of traffic initially. Monitor closely. Fix issues. Expand gradually.
Within weeks, you will see call volume shift. Within months, the new channel becomes how customers prefer to check status. The phone calls that remain are the ones that actually need human attention.
That is the goal: humans for complexity, AI for status checks. Technology doing what technology does well, freeing people to do what people do well.
Your customers are asking "where's my claim?" hundreds of times per day. Give them an answer that does not require holding on a phone line.
Ready to deflect status enquiries?
SwiftCase Switchboard provides AI chat and WhatsApp that integrates directly with your claims system. Customers check status instantly. Your team focuses on complex work.
Book a demo | Learn about Switchboard | See the insurance solution