What a live session is trying to prove
A liveness check is not a trick question. It is a short set of prompts that helps an agent judge whether the person on camera is present, responsive and able to take simple actions in real time. The goal is to reduce the chance of a spoofed video, a screen replay or a person using someone else’s document.
In a typical guided session, the customer is asked to position the camera, show the ID document, adjust the angle, then complete a movement or speech prompt. The agent watches for natural timing, eye movement, lighting changes and whether the face and document remain consistent across the session. A clean result depends on more than technology, it depends on clear instructions and steady handling by the person on the other side of the screen.
Prompts that work in the real world
Most liveness checks use ordinary actions that are easy for a genuine customer and harder to fake cleanly. The prompt should be short, direct and matched to the video quality available on a phone or laptop camera.
- Turn your head slightly to the left and then back to centre.
- Look at the screen, then look at the camera lens.
- Read a short phrase while holding the document in view.
- Move the ID closer so the edge and photo can be checked.
- Cover one side of the document, then reveal it again.
These steps are most useful when the agent keeps the pace calm. If the customer rushes, the image can blur and the review becomes harder than it needs to be. A better session usually starts with one instruction at a time and a clear pause between prompts.
How agents read the signs on screen
A trained agent is looking for a combination of small details rather than one dramatic clue. Live skin movement, small head shifts, slight focus changes and natural pauses all matter. So does the way the document behaves in the hands of the customer. A genuine interaction usually has small imperfections, while a copied feed often looks too still or too even.
The review also checks for consistency. The face in the session should match the document photo closely enough for the case file, and the document details should remain legible when the camera moves. If the lighting is poor or the camera is too far away, the agent may slow the process down and ask for a better angle before the file is used.
- Face and document photo should line up across the session.
- The customer should respond naturally to instructions.
- Lighting should show the face, edges and text clearly.
- Screen reflections should not hide the document or the eyes.
- The session record should capture what was checked and why.
POPIA records and FICA minded file handling
Video identity checks are not only about the moment on camera. The file also needs sensible handling afterwards. Personal information, screenshots, session notes and recordings should be stored with access control, retention rules and a clear internal purpose. Under POPIA, the business should treat that material as personal information, not casual admin.
For FICA style customer due diligence, the useful question is whether the record shows how the person was identified and what was observed during the review. That means the session should leave enough evidence to explain the steps taken, the document seen and the result of the liveness check. Good record keeping is usually quieter than people expect, but it is very hard to do well in a rush.
A Rosebank onboarding flow for online accounts
In Rosebank, a financial services team or credit provider may onboard a client in Cape Town or Durban without ever seeing them in person. The customer starts with a link to a guided video session, then a trained agent checks the document, face and liveness prompts while the account team watches the case status on its side. That same flow can be used for Johannesburg, Pretoria, Gqeberha, Sandton or Midrand clients without changing the core method.
Where the process usually breaks is not the check itself but the handover between systems. If the onboarding form, document capture and case notes do not line up, the file becomes slow to review. Workflow mapping, API coordination and staff training help keep the session readable from first contact to final sign-off.
- Set the liveness prompt before the call begins.
- Keep the ID capture step separate from casual chat.
- Make sure the agent knows when to pause the review.
- Record escalation points for unclear footage or mismatched details.
Training the team that runs the session
Even a good liveness design can wobble if the team handling it is uncertain. One agent may speak too quickly, another may over explain, and a third may skip the parts that matter for quality control. Training should cover how to issue prompts, how to spot a poor capture, and when to move a case into escalation rather than forcing a close call.
Refresh training helps when the team starts seeing the same mistakes again, especially on mobile cameras and low-light sessions. Quality monitoring then gives the operation a practical view of what is being missed. The best sessions feel calm to the customer and methodical to the verifier, not theatrical or overcomplicated.
At a Sandton finance counter and a Gqeberha hiring office, the needs are often similar even if the teams work differently. Clear scripts, steady pacing and a simple escalation path make the process easier to manage across regions.
What a useful liveness checklist leaves behind
A good liveness check should leave a readable trail in the case file. The notes need to show what prompt was used, how the customer responded, whether the image quality was acceptable and if any follow up step was needed. That trail is useful for internal review and for later questions about the onboarding decision.
PersonVideo ID works with South African businesses that want remote video verification handled in a structured way. The service can cover workflow mapping, integration planning, agent script design, quality monitoring and go live stabilising, with our contact form used for enquiries from across the country. When the process is designed properly, liveness checks stop feeling like a hurdle and start acting like a controlled part of the onboarding file.
