Branchless Customer Proofing

A video verification flow that fits the onboarding counter

Branchless Customer Proofing is a remote identity check for organisations that open customer accounts online or by assisted digital channels. A customer joins a short guided video session, shows an identity document on camera, and the agent captures the details needed for the verification record. The process suits banks, lenders, insurers, property teams, managed service providers and other operations that need a live person in front of a trained checker before activation.

The workflow is built around practical customer due diligence steps. The agent can compare the face to the document photo, look for signs of tampering, and apply liveness checks during the session so the person on camera is present in real time. Consent capture, audit notes and record retention are handled as part of the process, with POPIA aware handling and FICA style onboarding controls where those rules apply to the client’s own process.

It works best where branch queues, travel time and paper handoffs slow the file down. A customer in Johannesburg, Pretoria, Cape Town, Durban or Gqeberha can complete the session from home, a shop floor or an office, while the business keeps a clear verification trail for internal review.

Session sizes and options for different onboarding volumes

There is no one shape for every team. Some clients only need a live agent session for higher risk accounts, while others want the same format for all new customers. The service can be set up as a light touch check, a full guided verification flow or a scaled review queue that fits a larger onboarding operation.

• Standard video session for single customer onboarding
• Higher scrutiny flow with extra document prompts and liveness checks
• Batch onboarding support for teams handling many new accounts
• Agent led review with escalation for unclear images or doubtful documents
• Internal training packs for staff who manage handover and exceptions

The practical size of the service depends on how many fields the client wants to capture, whether the session is live only or mixed with pre captured inputs, and how much escalation handling is needed. Some teams want a narrow verification step, others need a broader onboarding workflow with scripts, queue logic and reporting. We map that first, then shape the session format around it.

Where branchless proofing earns its place

This service suits operations that must prove who the customer is, but do not want the whole journey tied to a physical counter. It is common in online account opening, remote onboarding, credit applications, identity refreshes and assisted sign ups where staff need to confirm the person in front of the camera is the same person named on the document.

It also suits businesses with branches in some cities and digital onboarding elsewhere. A group with staff in Sandton and Midrand may still want a single video proofing standard for customers anywhere in South Africa. The same format can be used across Johannesburg clients, Pretoria clients, Cape Town clients, Durban clients and Gqeberha clients so the verification record looks consistent across regions.

For operations that already use a CRM, onboarding portal or internal case system, the service can sit inside the existing customer journey without changing the whole stack. That is where workflow mapping and API coordination matter, because the proofing step has to fit the business rule, not sit outside it.

• Remote onboarding for retail and business customers
• Reduced need for in person branch handling
• Consistent verification format across multiple sites
• Useful where staff need a documented audit trail

Integration work, scripts and the handoff to staff

The service is not only about the video call. Many clients need the verification step joined to their own systems, which is where integration planning and API coordination come in. We look at how the session starts, what data gets captured, where the result lands, and which team sees the outcome when a case is approved or escalated.

Agent script design matters too. A clear script keeps the session steady, limits drift between agents and gives the customer a plain sequence to follow. We also support staff training for client teams that handle onboarding, exceptions or escalations. That can include how to guide customers to place the document on camera, how to deal with glare, and how to note a mismatch without turning the call into a long argument.

For larger rollouts, pilot launch support and go live stabilising help the process settle into daily use. Change request support and operational reporting are available when a client adjusts fields, adds risk checks or changes the handoff between departments.

• Workflow Mapping
• Integration Planning
• API Coordination
• Agent Script Design
• Staff Training

What the verification session captures

A good proofing session is not vague. It needs a clear set of checks and a record that can be reviewed later by the client’s compliance or operations team. The usual capture set includes the identity document type, visible document details, live facial comparison, liveness indicators, notes on any mismatch, and the outcome of the review.

The session record may also include consent to proceed, timestamps, agent notes, and any escalation path used when the document image is faint or the customer movement is not convincing enough for the screen. Quality monitoring then checks that agents are applying the same standard across sessions, not leaving gaps when the queue gets busy.

That is where quality assurance and escalation design work together. When a case needs a second look, the process should already show who handles it, what extra information is required and where the result is stored. If the client wants refresher training later, that can be arranged around the live workflow so the people using the system do not drift into shortcuts.

Care, record keeping and the practical details to confirm

Branchless Customer Proofing needs sensible care on both the customer and client side. The customer needs a stable device camera, a clear image and enough light to show the document and face properly. The client needs a process for storing records, controlling access and keeping the session logs tied to the correct onboarding file. Where the business has retention rules or internal audit steps, those should be built into the process from the start.

Before a rollout, confirm these details with us through our contact form: the document types to accept, whether the check is live only or part of a wider onboarding journey, what fields must be captured, which staff will escalate doubtful cases, and whether the client needs reports by branch, region or queue. Also confirm whether the workflow must support both first time onboarding and later refresh checks, because the script and handoff are not always the same.

Physical fitting is usually a process setup rather than site work, but the service still needs proper planning. Client teams should know who owns the handoff, how the verification status is read, and where the record sits after the session closes. That keeps the proofing step neat and usable instead of becoming another box in a crowded file.

• Accepted ID document types
• Capture fields and session notes
• Escalation rules for unclear or doubtful cases
• Retention and access controls for records
• Reporting format by site or region