A remote proofing flow for membership enrolment
The client was a healthcare membership team in Gqeberha handling new sign-ups, policy updates and member detail changes for people who were not always able to visit in person. They wanted a process that let a customer join a short guided video session, show an ID document clearly, and allow a trained agent to compare the face with the document before the account moved forward.
The brief was practical. The team needed live proofing that could support remote onboarding, while still fitting the way their staff worked, the way their systems captured records and the way their internal checks were documented. There was also a need to keep the customer experience calm and structured, because many members were joining from home, from offices or from mobile connections around Gqeberha and other South African centres.
We treated the rollout as an operational project rather than a software only task. That meant mapping the full journey from invitation to session start, through ID capture, face comparison, consent steps and the storage of verification records. It also meant paying attention to the handover points between the agent, the member services team and the system administrators who kept the process moving.
- Client type: healthcare membership team
- Location: Gqeberha, with remote members across South Africa
- Use case: remote sign-ups and member detail updates
- Core method: guided video session with ID document review and face comparison
What had to fit the way a healthcare team works
The main constraint was consistency. In healthcare administration, the team cannot leave document quality or session handling to chance, because the supporting record has to stay clear long after the call ends. We therefore designed the flow around simple agent prompts, clear screen order and a consistent record trail for each session.
Another issue was staff confidence. The client wanted their own team to understand when to start a verification, how to manage a poor image, how to handle an interrupted connection and how to note an escalation without making the member repeat the whole process. That required a usable script, not just a policy note.
We also had to keep the process suitable for busy working hours. Some members joined from offices, others from home and some from quieter areas where network quality shifted during the day. The process needed to stay workable even when the connection was uneven or the first capture was not usable.
- Clear consent prompts before the session moved into document capture
- Agent guidance for face comparison and liveness checks
- Record keeping aligned to internal governance and POPIA aware handling
- Escalation paths for unclear documents or interrupted sessions
The rollout plan and the people on it
We ran the rollout in stages over six weeks. The first phase was workflow mapping, where Jared Jantjies and Thabo Mokoka worked through the customer journey with the healthcare team and identified where the old process slowed down or left gaps. From there we shaped the verification steps, the escalation points and the information that the team would need to capture in the record.
Naledi Adonis and Megan Vermaak then focused on operations and client handling, making sure the internal process matched the way the membership team already handled sign-ups and account changes. Anele Nortje prepared the training material, while Sibusiso Gamieldien reviewed the quality checks that would sit around each session. Leila Petersen handled the agent-side verification flow, especially the parts where consistency mattered most.
The practical build included integration planning, API coordination, agent script design, staff training, pilot launch support and go live stabilising. We also set out refresh training and change request support so the client could adjust the process later without losing control of the core steps.
- Week 1 and 2: workflow mapping and integration planning
- Week 3: script design, escalation design and pilot preparation
- Week 4: staff training and quality checks
- Week 5 and 6: pilot launch support, reporting review and stabilising
How the verification process was shaped
The customer journey was built around a guided video session that a member could complete without travelling to a branch. The agent asked the member to show the ID document in a controlled way, then checked the document details against the face on screen. Where the image was unclear, the agent used a scripted retry step rather than guessing.
We included liveness checks in the flow so the interaction did not rely on a static image alone. The session logic also covered consent and record keeping, so the healthcare team had a proper audit trail for each verification and could store the outcome in line with their internal process. That was important because membership records often need to support follow-up queries, updates and future service steps.
The result was a cleaner working pattern for the client team. Instead of chasing back-and-forth document copies and trying to interpret uneven images, the staff had one guided sequence that they could run the same way each time. It also gave the healthcare team a more controlled route for remote sign-ups and detail changes, which suited members in Gqeberha and beyond.
- Face comparison against the live video session
- Liveness checks to reduce obvious presentation risk
- Document capture rules for clearer review
- Consistent note taking for escalation and outcome recording
Training that matched the actual call flow
Training was not limited to theory. We worked with the client team on live scenarios, common member mistakes and the points where agents needed to slow the call down. Anele Nortje led the training structure and Jared Jantjies covered the parts that touched the system connection, while Megan Vermaak helped align the service language to the membership team’s own tone.
The training covered more than the verification itself. Staff were shown how to explain the reason for the session, how to keep the member informed while the ID is being checked and how to handle a change request without breaking the record trail. We also built refresh training content so the team could revisit key steps when new staff joined or when the process was updated.
That approach helped reduce drift. Once a script is in place, teams can slowly slide into shortcuts if the process is not revisited. The refresh sessions and quality monitoring gave the client a way to keep the standard steady without making the work heavy or awkward for frontline staff.
- Agent script design with plain prompts and clear handoffs
- Training for first-time users and refreshed staff
- Operational reporting for internal review
- Quality monitoring with escalation notes for problem sessions
What changed for the Gqeberha team
By the end of the rollout, the healthcare membership team had a remote proofing process that fit their onboarding and update work without forcing every member into an in-person step. The flow was more structured, the capture process was clearer and the team had better control over how the session was opened, checked and recorded.
The biggest value was practical. The team could support remote sign-ups and updates with a proper identity check, while keeping the process understandable for staff and members. The project also gave them a foundation for future change requests, since the integration and escalation pieces were already thought through instead of bolted on later.
If we were running a similar rollout again, we would keep the same sequence of workflow mapping, pilot launch support and close quality review. That combination gave the client a solid operational base, and it worked well for a healthcare setting where document accuracy and record handling matter every day.
- Remote sign-ups became easier to manage
- Member detail updates followed one controlled flow
- Staff had clearer prompts for session handling
- The client gained a supportable process for future changes
Key facts
| Project | Gqeberha Healthcare Rollout |
|---|---|
| Client type | Healthcare membership team |
| Location | Gqeberha |
| Delivery model | Remote video identity verification |
| Timeline | 6 weeks |
| Scope | Workflow mapping, integration planning, staff training, quality monitoring, pilot launch support |
