Where a video session can drift off script
A remote verification process looks tidy on paper until a real customer joins with a sun-glared ID card, a cracked screen, or a background that makes the image hard to read. Quality assurance watches those moments closely, not to slow the work down, but to keep the same standard from the first session to the last.
In practice, the review covers whether the customer was guided clearly, whether the ID document was captured cleanly, and whether the face comparison matched the document holder. A good review also checks that the agent handled liveness prompts properly, so a still photo, replayed video, or other misuse does not slip through unnoticed.
What the reviewer should listen and look for
Quality checking is not only about the final pass or fail. It also looks at the agent’s tone, pacing, and whether the customer was given enough direction to complete the session without confusion. If the script is too loose, one agent may ask for extra steps while another skips them. That kind of drift shows up fast in customer experience and in the audit trail.
- Clear opening consent and identity notice
- Correct document type and legibility checks
- Face comparison against the presented ID
- Liveness prompts used at the right point
- Proper escalation when the image or behaviour looks doubtful
For teams handling FICA-style customer due diligence, the review also checks whether the record is complete enough for internal process and future review. Under POPIA, consent handling and record keeping need disciplined treatment, not casual notes on a call log.
A Johannesburg pilot that shows the point
Picture a Midrand onboarding team handling applications for an account that opens online. Customers arrive from Johannesburg, Sandton and Pretoria, some on a strong connection, others on a weak one. One agent keeps the video brief and clean, another spends too long talking around the check, and a third forgets to note a failed liveness attempt. On paper, all three may look productive. In QA review, only one process is really repeatable.
That is where structured review helps. It lets the operations lead see which step is causing friction, whether the script needs a smaller change, or whether the team needs refresh training. In a city office setting, the issue is often not the technology alone, but how the team uses it under pressure and time constraints.
Records that help when a file gets questioned
Good verification work leaves a clear trail without turning the session into a paperwork exercise. The review file should show what was seen, what was confirmed, and what was escalated. It should also show when a customer could not complete the session cleanly and had to be reworked under the proper process.
- Session outcome and reason for the outcome
- Document type used during the check
- Any mismatch between document and face
- Escalation notes for uncertain cases
- Quality scoring against the agreed script
When those notes are neat, the client team can trace patterns instead of guessing. That matters in South African operations where one branch may be handling corporate sign-ups, another retail accounts, and another a mix of both. The record should support the business process, not create another problem to solve.
Training keeps the script from going stale
A script that worked well in the first month can start slipping once staff change or customer behaviour shifts. Training is part of quality assurance, not a separate decoration. The team needs reminders on how to explain the session, how to handle awkward lighting, and when to pause and reset instead of pushing ahead with a weak image.
Refresh training also helps when the workflow changes. Maybe the client has altered their onboarding fields, or the escalation path now needs a second review for certain cases. The people doing the sessions should know the change before it starts affecting customers.
At PersonVideo ID, this is where the operations side, training side and quality side need to sit close together. Naledi Adonis can keep the process practical, Jared Jantjies can shape the integration steps, and Anele Nortje can keep the staff guidance readable for the people actually on session duty.
Local service teams need tighter handovers
Across South Africa, the handover between client systems and verification staff can get messy if it is not mapped properly. A business in Cape Town may want a different approval path from one in Gqeberha, while Durban teams may need a different escalation pattern for customer connectivity issues. Quality assurance helps spot those differences before they become daily habits.
That is also where Escalation Design and Go Live Stabilising matter. The review process should show whether the client knows what to do with a borderline case, whether the agent knows where to send it, and whether the reporting line is clean enough for management to act on it. Sibusiso Gamieldien and Megan Vermaak can use those findings to keep the process calm and visible, rather than patching problems one by one.
