Rosebank base, national reach
Our Rosebank base supports businesses that onboard customers online and need a controlled way to verify identity before an account is opened. A customer joins a guided video session, shows an ID document, and a trained agent compares the face to the document while the interaction is recorded and kept for internal records.
The work is remote, but the rollout is rarely generic. Some teams need tighter script design, others want the agent workflow mapped against existing systems, and some need reporting lines set up for branch managers, compliance teams or operations staff. That is where the regional view matters, because the practical rollout differs from one office to the next.
Cities where client teams often sit
We work with client teams based in several South African business centres, including Johannesburg, Pretoria, Cape Town, Durban and Gqeberha. Midrand and Sandton also come up often when a group has centralised operations, shared service teams or a compliance function that oversees multiple branches.
- Johannesburg clients often want higher-volume workflow planning and clearer escalation paths.
- Pretoria clients commonly ask for tighter process notes for regulated onboarding.
- Cape Town clients often need integration planning across mixed operations teams.
- Durban clients may want practical training for front-line staff and supervisors.
- Gqeberha clients often need a structured pilot before wider rollout.
Each city brings its own operating rhythm. A branch with a small team may need more hands-on training, while a larger group might need agent script design, quality monitoring and reporting lines documented in detail.
How rollout needs shift by region
Regional location affects how a video KYC process lands inside the business. A head office in Sandton may want a single process across several brands, while a branch network in Pretoria or Durban may need local supervisors to understand how to review exceptions and manage escalations. In Cape Town, a client may ask for sharper integration planning because the verification flow has to sit neatly beside a busy onboarding team.
The service itself stays consistent: guided video session, ID capture, face comparison, liveness checks, consent handling and record keeping aligned to internal policy and South African customer due diligence practice. What changes is the surrounding structure, including who trains the staff, who signs off the script, and where the operational handover sits.
Support that sits with operations, not just IT
Integration help is rarely only about systems. It also touches staff training, escalation design, quality monitoring and go live stabilising, especially where a business has several branches or regional teams. Our work with client regions often starts by mapping the process in plain language so operations, compliance and technical staff are looking at the same flow.
- Workflow Mapping for the current onboarding path
- Integration Planning for internal systems and handovers
- API Coordination where technical teams need detail
- Staff Training for agents, supervisors and admin staff
- Operational Reporting for ongoing checks and reviews
That mix helps when a project spans more than one city. A Johannesburg team may be ready for a pilot launch while another branch still needs refresh training and change request support before the wider rollout is sensible.
Training looks different in each office
Training is shaped around the people who actually run the process. Some client teams need agent script design and short practical sessions for new staff. Others need quality assurance routines written out clearly, so the same standard is used in every region. When a business has staff in Rosebank, Pretoria and Cape Town, the training plan may need separate sessions for supervisors and front-line agents.
We also support refresh training when a process changes, or when a branch adds a new onboarding queue. The aim is to keep the guided video session orderly, with clear steps for document checks, consent handling and escalation when a capture is unclear or incomplete.
If you are mapping a regional rollout
Regional rollouts usually work best when the business knows which office owns the process, who handles exceptions, and where the reporting sits. Some teams begin with one city and then widen the service to other branches once the training and escalation design are settled. Others need all regions aligned from the outset because the onboarding process already runs across multiple centres.
- Single-branch teams often need simpler training and fewer handover points.
- Multi-city teams usually need stronger reporting and script control.
- Compliance-led teams may want clearer record keeping and review steps.
- Operations-led teams often focus on throughput, quality and staff handling.
That is why the regional pages matter. They show where the work is commonly delivered, and how the service can be shaped for the specific structure of a business based in Johannesburg, Pretoria, Cape Town, Durban, Gqeberha or the wider Gauteng corridor.