Sandton Lender Rollout

A lender journey that needed tighter identity steps

The client was a central Johannesburg lender serving online applicants in Sandton and nearby business districts. Their team wanted a remote video identity step that fit neatly into the digital onboarding flow, with a trained agent guiding the customer, checking the ID document, comparing the face on screen, and recording the session in a controlled way.

The brief was practical rather than flashy. They already had a working application process, but the identity step needed clearer scripting, cleaner handover points and a better path for staff who would support applicants once the video check was live. The main concern was keeping the process steady for users on phones and laptops, not forcing them into extra admin or a clumsy detour.

Because the rollout touched operations, support and product teams, we kept the work tight. We looked at where the customer enters the video session, what the agent sees, which prompts appear on screen and how the internal teams record a completed or failed check. That kept everyone speaking about the same journey instead of three different versions of it.

Constraints that shaped the release plan

Sandton applicants often finish finance forms on mobile during a short break, so the experience needed to stay compact. The lender also needed a method that could handle different identity document conditions, varied camera quality and a mix of first time users and people already familiar with live verification. Small delays or unclear prompts would have created extra load for the support team.

• Short guided session flow that did not overrun the application journey
• Clear capture points for ID document, face match and liveness checks
• Agent wording that stayed consistent across all verification teams
• Escalation steps for poor image quality, mismatch cases and incomplete sessions
• Internal records that supported audit trails and customer follow-up notes under the client's own controls

We also had to work around system boundaries. The lender wanted the video check to sit beside existing onboarding screens, not replace them. That meant careful integration planning, clear field mapping and agreement on what data moved where. A loose setup would have created more admin later, so the project leaned on structure from the start.

Mapping the journey before any live calls

We started with workflow mapping and integration planning. The first pass traced the applicant journey from the moment a customer reached the verification stage to the point where the account could move forward. From there, we set out the screen prompts, the agent script, the evidence capture points and the handover rules for cases that needed manual review.

Jared worked on API coordination with the client's technical team, while Anele shaped the training content so the operational staff understood the sequence end to end. Sibusiso set the quality checks for session review, and Leila helped define the agent side of the live process so the calls stayed calm, direct and consistent. Megan handled client side coordination around reporting and change requests, and Thabo kept the overall rollout aligned with the lender's commercial timeline.

We did not treat the project as a single handover. It was built as a working process that needed to hold up under real applicant traffic. So the scripts, checks and reporting points were all tied back to the same operating picture. No piece sat on its own, which made the whole thing easier to manage when the first sessions went live.

Training and release work across three weeks

The rollout took place in stages over three weeks. Week one covered workflow mapping, integration planning and script design. In week two we moved into staff training, pilot launch support and quality monitoring, with live sessions checked against the agreed process. Week three focused on change request support and go live stabilisation, so the lender's team could refine wording, routing and exception handling where needed.

• Week 1: process mapping, system handover points and technical coordination
• Week 2: training sessions, pilot checks and live session review
• Week 3: release tuning, reporting updates and escalation refinement

The training sessions were not just a walk through slides. We worked through actual session flow, the way an agent requests document capture, how to handle a blurred image, and what to do when the face comparison does not line up cleanly. Staff also practised the tone used with applicants so the process felt firm but not cold. That mattered, because a rushed voice on a video call can unsettle people fast.

What changed once the video step was in place

Once the phased release settled, the lender had a clearer path for online applicant checks. The video session gave the team a live view of the customer, a direct way to inspect the identity document and a more controlled way to record the outcome. Support staff also had fewer grey areas to deal with because the script and escalation points were better defined.

For the business, the useful part was not just the verification itself. It was the structure around it. Reporting became easier to follow, the pilot period exposed weak spots early, and your internal teams had one shared reference point when a session needed review. That sort of clarity saves time later, even if the first setup takes some careful work.

The lender also gained a process that could be extended to other branches of the application journey without starting over. Midway through the rollout there was a small wording adjustment in the agent prompts, and once that was tightened the session flow settled nicely. Nothing dramatic, just the sort of fix that stops a minor snag becoming a recurring call.

What we would carry into a similar rollout

If a similar lender project lands on the table, we would keep the same order: map the journey first, train the team before broad release, then use a controlled pilot to catch rough edges. That sequence gave the Sandton rollout enough structure to hold together without making it stiff.

• Keep the agent script short enough for real users on mobile screens
• Set escalation rules before live sessions begin
• Review the video check in context, not as a standalone task
• Build reporting with operations in mind, not only compliance notes

We would also keep the change request path open for the first few weeks of live use. Small wording changes, routing fixes and reporting adjustments are normal on a job like this. It is better to catch them while the process is still fresh than to leave the team working around an awkward step for months.