Starting the session without losing the customer
A good opening sets the pace. The agent greets the customer, explains the video identity check in plain language, confirms consent and keeps the instructions short enough for first time users. The aim is to reduce hesitation without rushing the person through an important step.
Train staff to speak clearly, pause after each instruction, and check that the customer can hear and see properly before asking for documents. If the customer is in a noisy place or the picture is poor, the agent should slow the session down and guide the person to a better position rather than guessing through the rest of the call.
- Confirm the customer understands the purpose of the session.
- Ask for consent before any document capture begins.
- Keep the camera framing simple and repeatable.
- Use short, plain instructions with one step at a time.
Document review that holds up under pressure
Agents need a checklist for reading identity documents, not a loose impression. Training should cover the visible features on the document, how to check whether it looks altered, and when to slow down because a copy is blurry, cropped or reflected badly on screen. Staff also need to know that an unreadable document is not a valid result.
Use practice sessions with different document conditions, including glare, worn edges and low light. Agents should learn to compare the document portrait with the live face, look for obvious differences, and record the reason for any concern in a clear note. That note becomes part of the audit trail and needs to be specific, not vague.
- Check document legibility before moving on.
- Compare the portrait to the live face shown on screen.
- Watch for signs of tampering or poor image capture.
- Record the reason for a failed or paused review.
Liveness checks and face matching in real sessions
Video identity work depends on a living person being present, not just a picture on a screen. Agents should be trained on simple liveness prompts that make sense in a remote setting, such as following movement, turning the head or repeating a requested action. The instruction must stay polite and consistent, so customers do not feel tested in a theatrical way.
Face matching needs discipline. A trained agent does not rely on a quick glance alone. They should compare visible features, note if the video feed is stable, and stop when the image quality makes the comparison uncertain. In those cases the right move is to escalate, not to force a decision that will be hard to defend later.
- Use a fixed sequence for the liveness step.
- Do not improvise new prompts during the call.
- Pause when the feed drops quality or freezes.
- Escalate uncertain matches instead of guessing.
Escalation paths that staff can use under stress
Escalation training should be practical, not theoretical. Agents need to know exactly when to hand over a case, what evidence to attach, and which wording to use in the record. A weak escalation path creates confusion for everyone involved and slows the account opening process.
Build separate routes for technical issues, document concerns, suspected impersonation and incomplete customer participation. Staff should be able to name the reason, the evidence and the next action without searching through notes. That kind of structure protects the operation when a session becomes messy or the customer disputes the outcome.
- Define the trigger for each escalation route.
- Keep the handover note short and factual.
- Record what was seen, not what was assumed.
- Separate technical faults from identity concerns.
Records, consent and privacy in everyday handling
Training must include careful handling of customer information. Agents should know that consent, document images, session notes and outcome records all need to be treated as controlled information. Under POPIA, the practical habit is simple: only collect what the verification process needs, store it properly and avoid casual sharing inside the team.
Staff should also understand that a neat record is part of the service, not extra admin. Notes must show what was checked, what was unclear and what happened next. If a customer asks what happens with the information, the agent should use the approved explanation and keep the answer factual, brief and consistent with the process in place.
- Collect only the information needed for verification.
- Store session records in the approved system.
- Avoid informal sharing of customer images or notes.
- Use the same explanation every time consent is discussed.
Building confidence through practice, review and refresh sessions
Agent training works best when it is repeated in short, useful blocks. New staff need guided practice with live examples, while experienced staff benefit from refresh training that keeps the process consistent after policy updates or system changes. A session review should cover tone, document handling, decision making and the quality of the written record.
Supervisors can use sample calls to spot habits that drift over time, such as unclear instructions, overlong explanations or weak escalation notes. A clean training routine gives the team a shared standard, so the customer experience does not depend on which agent happened to answer that day. It also makes integration with client systems easier to manage because the handover points stay familiar.
- Run supervised practice before live handling starts.
- Review sample sessions for tone and accuracy.
- Refresh training after workflow changes.
- Use the same standards across all client groups.
