How the rollout pages are grouped
Find rollout examples for teams that need remote video identity verification fitted into a working onboarding flow. Some clients need a lighter setup for low-volume account openings, while others need a fuller process with scripts, escalation steps and staff training across several branches.
The pages are arranged by town, suburb and operating pattern so the right example is easier to find. Rosebank teams, Pretoria branches and coastal offices do not all face the same document quality, customer behaviour or internal handover points, so the rollout notes are not written as a one-size-fits-all plan.
What a rollout usually has to cover
A proper onboarding rollout is more than switching on a video link. It has to cover who joins the session, how the ID document is captured, how face comparison is handled, what happens when the image is poor and how the record is stored for the business file.
- Workflow mapping from application to verification outcome
- Integration planning for the client system or platform
- API coordination between teams
- Agent script design for live sessions
- Escalation design when the check needs a second look
- Operational reporting for managers and auditors
Service work that sits behind each implementation
The service mix changes from client to client, but the work usually sits in a few practical buckets. Some businesses need help shaping the first pilot, others want staff training after the test run and some need refresh training later when new people join the team.
- Pilot launch support for the first set of live verifications
- Quality monitoring for document handling and session discipline
- Go live stabilising when the process is under pressure
- Change request support when the onboarding flow shifts
- Refresh training for new agents or updated steps
In practice, the rollout has to respect consent, record keeping and the business’s own customer due diligence rules under POPIA and FICA related checks. That means the process needs to be clear enough for agents, but still controlled enough for the records team.
Where the rollout examples point across the country
The hub includes rollout pages for Johannesburg clients, Rosebank base work and branch setups in Pretoria, Cape Town, Durban and Gqeberha. There are also examples that reflect Midrand and Sandton operations where teams often handle more than one line of customer onboarding at the same time.
That spread matters because the same video verification service can be used in very different ways. A finance team, a brokerage office and a membership onboarding team will all ask for different scripts, different reporting views and different levels of handover between operations and compliance staff.
Who the rollout pages are meant to help
These pages are for managers, operations leads and onboarding teams who already know that the hard part is often the handover between people and systems. A rollout only works when the verification step fits the customer journey, the branch structure and the staff routine without adding confusion at the counter or in the call flow.
- Businesses onboarding customers online
- Teams needing staff training for live verification sessions
- Operations groups planning integrations with internal systems
- Managers wanting a clearer pilot and reporting structure
The best page to open first depends on the client type and the location. A Rosebank base with central admin will not face the same rollout questions as a Durban branch handling customer sign-up across a wider service area.
What the personvideo ID team handles on the ground
Our team includes people who look after operations, integration, training, quality and client support, so the rollout work can move through a proper sequence instead of sitting in one inbox. Thabo Mokoka leads the business, while Naledi Adonis, Jared Jantjies, Anele Nortje, Megan Vermaak, Sibusiso Gamieldien and Leila Petersen each cover a distinct part of the implementation flow.
That mix helps when a client needs the session script tightened, the training notes updated or the escalation path adjusted after the first live sessions. It also helps when a business needs to keep the same verification standard across more than one office, even if the customer mix shifts from suburb to suburb.