Practical Perspectives · Smartchoice Technology
Make Member Enquiries Easier to Follow
Connect the conversation with the work needed to resolve it.
In medical scheme administration, a member or healthcare provider rarely reaches out just to chat. They call because an event has occurred: a specialist claim was short-paid, a chronic medication authorisation was declined, or a dependant requires urgent hospital pre-authorisation. Frontline contact teams are expected to listen, diagnose the issue, and initiate resolution—often under intense pressure.
Yet in many administration environments, the contact record remains completely detached from the underlying administrative work. The call is logged as an unstructured text block in a generic customer relationship tool, while the actual resolution relies on manual emails, scattered sticky notes, or informal handoffs to claims assessors. When the conversation and the work are disconnected, service delivery breaks down.
Record the Purpose: Unbundle Multi-Request Interactions
A single contact session is seldom about just one thing. A member frequently calls with an overarching concern, but in the course of a four-minute conversation, they may ask three distinct questions:
- Why was their recent pharmacy claim deducted from their Medical Savings Account rather than their chronic benefit?
- What is their remaining balance for day-to-day dental treatment?
- How can they register a newborn dependant on their existing scheme option?
Treating this entire exchange as a single monolithic "general enquiry" guarantees that secondary requests fall through the cracks. Once the primary query is addressed, the remaining tasks are easily forgotten or delayed. Service teams need structured workflows that capture multiple distinct purposes within a single interaction record. When each request is classified and tracked independently, frontline staff can dispatch specific tasks to the relevant back-office queues—such as membership underwriting or chronic medicine desks—without losing sight of the broader conversation.
Keep the Context: Maintain a Defensible, Shared Thread
There is nothing more frustrating for a scheme member than calling back two days later only to encounter an agent who has no record of the previous discussion. Forcing members to repeat complex clinical or financial histories damages trust and extends call queues unnecessarily.
Meaningful service delivery requires that every interaction carries its full operational context forward:
- Timestamped Case History: An immutable audit trail showing precisely when the enquiry was initiated, who handled it, and what actions were taken.
- Direct Integration with Core Records: Frontline staff should not switch across five disparate terminal windows to locate membership status, benefit entitlement, or recent claims processing files. Context must be surfaced alongside the active ticket.
- POPIA-Compliant Governance: Notes and historical data must be accessible to any authorised team member stepping into the enquiry, while safeguarding sensitive health information under the Protection of Personal Information Act.
When the full context is preserved, any agent on the floor can pick up the thread instantly, review the status of pending back-office handoffs, and provide the caller with an authoritative update.
Review Resolution: Look Beyond Handling Time
Many contact centres continue to evaluate performance through a single legacy metric: Average Handling Time (AHT). When agents are incentivised solely on short calls, unresolved work can be passed between teams. Review resolution quality alongside handling time, including whether each request was completed and whether the member needed to contact the team again.
Connect enquiries with resolution
Bring member enquiries, relevant information and follow-up work together with Smartchoice Member Service.