Walmer Service Rollout

Walmer brief, and the part that mattered

The client in Walmer handled higher-value service subscriptions and wanted a verification path that felt orderly for customers, not clumsy or manual. The main brief was to move account opening checks into a guided video session where an agent could confirm the applicant, inspect the ID document, and keep a record of the interaction for the client’s internal controls.

The team also needed something practical for online onboarding across South Africa, because applications were coming from different cities and the branch could not rely on in-person checks alone. We kept the flow short and direct, with the session designed around face comparison, ID capture, consent steps, and a clear handover into the client’s own account opening process.

What shaped the rollout on the client side

The rollout had a few constraints that changed the way we planned it. The client needed a process that could work with staff who were still learning the new method, and they needed a verification route that could be tied into their own records without extra clutter in the middle of the onboarding journey.

• Applications were coming in from several towns, so the process had to stay consistent.
• Higher-value accounts needed a steadier check than a basic form upload.
• The verification step had to support customer due diligence in general terms.
• Session notes and records needed to stay organised for internal follow-up.
• The client wanted a workflow their team could explain without jargon.

We mapped the service around those points rather than forcing a generic script onto the business. That kept the process usable for the staff who handled onboarding, and it reduced the chance of the same question being answered in three different ways.

How the video verification flow was arranged

We designed the session flow so the customer joined a short guided video appointment, showed the ID document on camera, and moved through a face comparison step while the agent watched for obvious mismatches or signs that the document was not being presented by the rightful person. The session also allowed for liveness checks in a general operational sense, using live interaction rather than a static image.

The client needed the process to feel calm and controlled, so the script was kept tight. The agent led the customer through each step, asked for the right document views, and captured the details needed for record keeping and follow-up. Consent handling formed part of the routine, and the session notes were structured so the client could store the information in line with its own POPIA-aware record practices.

• Guided video session with a live agent.
• ID document shown clearly on camera.
• Face comparison during the same session.
• Liveness check prompts built into the script.
• Session record kept for the client’s file trail.

Integration work and staff training across the service team

The service subscription business wanted more than a working script. It needed the verification step to fit into the wider onboarding process, so we worked through workflow mapping, integration planning, API coordination, and the points where staff would move an application forward or pause it for extra review.

Training covered the practical side of the job. We walked the client team through the agent script, the most common session interruptions, the way to handle missing document detail, and the handover path when an application needed another look. The support also included quality monitoring and escalation design, so the team had a clear route for cases that did not sit neatly in the standard flow.

• Workflow mapping for the onboarding sequence.
• API coordination for the client’s internal handoff.
• Agent script design for guided verification calls.
• Staff training for operational use.
• Escalation design for exceptions and follow-up cases.

Weeks on the project, and how the rollout settled

The project moved in stages over a short rollout window measured in weeks. We started with the service map and script structure, then moved into integration planning and training, and finally supported the pilot launch before stabilising the go-live period.

That sequence mattered because the client did not want to train first and fix the workflow later. By tightening the steps before the pilot, we reduced confusion around who did what, when a session was approved, and how the verification record was passed into the client’s internal process. The end result was a steadier daily operation and less manual patching for the team in Walmer.

Results that showed up in day-to-day work

Once the service was in use, the client had a more controlled way to handle higher-value account applications without relying on a loose chain of screenshots or half-complete notes. The verification step sat inside a proper live session, so the staff could compare the applicant with the ID document and make a better informed internal decision before account opening.

There was also a clearer standard across staff members, which mattered because service teams tend to drift when one person handles checks differently from the next. The quality monitoring layer helped keep the process steady, and the reporting structure gave the client a better sense of where sessions needed review, where customers stumbled, and where the script needed small refinements.

• More orderly verification for higher-value applications.
• Stronger session records for internal review.
• Less variation between staff members handling checks.
• Cleaner escalation when an application needed follow-up.

What we would use again in a similar rollout

For a similar job, we would follow the same sequence: map the workflow first, settle the verification script early, train staff on live cases, and only then move into pilot launch support. That kept the Walmer rollout practical, because the client could test the process while still having enough structure around it to avoid messy handoffs.

We would also keep the reporting simple and the escalation path plain. When a business is handling account applications across several South African towns, it helps to have one clear route for acceptable sessions and another for cases that need a closer look. The less clutter in the middle, the easier it is for the team to keep the work moving without second guessing every step.