Bellville Membership Rollout

Bellville applicants, less paper chasing

The client was a membership-based service in Bellville handling applications from people who were not walking into a counter with printed forms in hand. Their onboarding team needed a better way to review ID documents, check that the person on screen matched the document, and keep a proper record of the step before membership was approved.

The brief was practical. They wanted remote ID review that could slot into an existing online application flow, with clear guidance for applicants and a process their staff could repeat without guesswork. The service also needed help training teams that dealt with online proofing at branch and head-office level.

• Client type: membership service with online onboarding
• Town: Bellville, with users across South Africa
• Core need: guided video identity review before account opening
• Support required: integration planning and staff training

What the rollout had to deal with

The main constraint was consistency. The client did not want different people running different checks in different ways, because that quickly creates gaps in record keeping and uneven customer treatment. They also needed a process that would work for applicants in Cape Town, Johannesburg, Pretoria, Durban and Gqeberha without asking the applicant to do anything complicated.

We mapped the workflow from first application to final decision, then shaped the video session around the points where a trained verifier needs to look closely. That included ID document capture, face comparison, liveness checks and consent handling inside a recorded process. The team also needed a clean handover between the applicant experience and the internal review steps.

• Keep the session short and guided
• Reduce avoidable back-and-forth for staff
• Keep records organised for internal audit trails
• Fit the process around existing membership systems

The flow we put in place

We worked on workflow mapping first, then moved into integration planning so the client could see where the verification step would sit in the wider onboarding journey. The video session followed a simple structure: the applicant entered the session, the agent guided the capture of the ID document, the agent compared the image on the document with the person on screen, and the session record was stored for the client’s internal use.

API coordination formed part of the handover, because the client wanted the verification status to move into their own systems without manual re-keying. We also helped shape agent script design so the wording stayed steady, especially when applicants were unsure what to hold up to the camera or how to position the document. That reduced unnecessary pauses and kept the review focused on the evidence in front of the agent.

For the client’s operations team, the other value was control. They had an approach they could train, monitor and refine, rather than relying on informal checks that changed from one staff member to the next.

Training the people who would run it

The Bellville team wanted more than a technical handover. They needed staff to understand how the sessions should feel, what to watch for, and when to escalate a file for a closer look. We built training around the real working day, not a neat theory version of it.

Training covered how to introduce the session, how to ask for a clear view of an ID document, how to deal with glare or a poorly framed camera, and how to keep the applicant moving without losing the quality of the review. We also covered quality monitoring and refresh training so the process would not drift after launch.

• Agent script design for consistent session wording
• Staff training for operational teams and supervisors
• Quality monitoring to spot avoidable errors
• Escalation design for files that need extra review

Launch staging over five weeks

The rollout ran in stages over five weeks. The first stage focused on workflow mapping and integration planning. The second stage covered the session structure, script writing and internal reviews. The third stage moved into staff training, pilot launch support and practical adjustments once live use began.

During the launch stage, we stayed close to the operational detail that matters in a membership environment. That meant checking how the verification step sat next to the rest of the onboarding journey, where staff needed clearer instructions, and where reporting had to show the status of pending and completed reviews. Go live stabilising was part of the final stage, because the process needed to settle into daily use without creating noise for the support team.

The client also wanted a clean path for change requests. When their internal process shifted, they needed a way to update scripts, routing or reporting without having to rebuild the whole flow.

What settled after go live

Once the process was running, the client had a steadier way to proof applicants before opening accounts. The main improvement was organisational: staff could see the same sequence each time, applicants were guided through the session, and the verification step no longer depended on loose instructions passed around between teams.

For a membership model, that matters because the onboarding decision sits close to the point where trust is formed. The remote video review gave the Bellville team a clear method for checking identity details, capturing consent and keeping a record in line with their own internal controls and broader South African customer due diligence expectations.

The result was not a noisy reinvention of the whole membership journey. It was a tighter process, better handled, with fewer moving parts for the staff who had to run it every day.

What we would use again in a similar Bellville rollout

We would follow the same work order: map the process first, create the scripts next, then prepare the team before the pilot begins. That sequence gave the client room to spot weak points early, and it kept the launch from becoming a scramble.

We would also keep the reporting simple. A membership team does not need cluttered outputs, it needs clear status tracking, escalation visibility and a record that helps the internal team work through files properly. The same approach works well when the verification flow has to serve different towns and different staff groups without losing consistency.

• Start with workflow mapping before any technical handover
• Train supervisors and agents on the same script set
• Build escalation rules before the pilot begins
• Keep reporting clear enough for daily operations