Opening the session without rushing the customer
A good consent step starts before the document is lifted to camera. The agent should explain the purpose of the session, what identity details will be captured, and that the check is being used to support customer due diligence. That explanation should be plain enough for a first-time user in Johannesburg or a small business owner in Gqeberha who has never been through a video KYC flow before.
The customer should know what is being asked of them and why. A short pause at the start gives space for questions, for confirming consent to record the session if recording is part of the process, and for checking that the person on screen is comfortable proceeding. If the customer sounds uncertain, the agent should slow down rather than pushing ahead.
- State the purpose of the session in plain language.
- Explain what will be captured during the call.
- Cover whether the session is recorded and kept for audit purposes.
- Give the customer a moment to say yes or ask for clarity.
What the customer should understand before ID capture
Consent is stronger when the customer can see the steps ahead of them. In a well-run verification flow, the agent describes the order of events before the ID document is shown to camera. That usually includes the document capture, the face match, a liveness check and any final review that the team completes before the account moves forward.
This matters for businesses onboarding clients in Pretoria, Midrand and Sandton. Some customers are happy to verify remotely, but they still want to know whether the session will include a live face check, whether the image will be stored, and whether a trained agent will review the file. Clear wording avoids confusion later when a customer asks what exactly was collected.
- Say what will happen during the session, in order.
- Explain that an ID document will be viewed and compared to the live face.
- Note that the customer may need to follow a guided prompt for liveness checks.
- Make the handling of captured records part of the explanation, not an afterthought.
Consent and record keeping under POPIA
For many South African businesses, the consent discussion is tied to record handling. That means the customer should understand that some information may be retained for audit, verification and internal control purposes. The conversation is not legal advice, and it should not pretend to solve every compliance question, but it should give the customer a fair picture of what the business is doing with their records.
POPIA-minded handling is practical, not theatrical. Keep the wording direct, limit the capture to what is needed, and avoid collecting extra material that has no place in the verification file. In a Rosebank office servicing clients across Cape Town, Durban and Gqeberha, that discipline helps staff stay consistent even when the daily volume changes.
- Tell customers that records may be kept for verification and audit purposes.
- Do not collect extra material that is not part of the check.
- Store the session in line with internal access controls.
- Keep consent language consistent across teams and locations.
What agents should say, and what they should not leave out
Agent script design makes a real difference. A script should not sound stiff, but it should cover the essentials every time. The customer needs to hear the purpose, the steps, the recording point if there is one, and the fact that the agent is there to guide the process rather than to pressure them through it.
Training should also cover the awkward moments. A customer may hold the ID too close to the camera, miss a prompt, or ask whether the document copy will be used elsewhere. The answer should be simple and consistent. If the session needs to pause, the agent should explain the pause and continue only when the customer is still comfortable. That sort of discipline protects the workflow and keeps the tone professional.
- Use the same consent wording across the team.
- Say what is being checked and why it matters.
- Avoid vague lines that leave the customer guessing.
- Explain pauses or repeats when the image is unclear.
A local onboarding example from a busy South African team
Picture a finance team in Sandton opening accounts for clients from Durban and Cape Town. The customer logs in from a phone, joins a short guided video session, and is told upfront that the call will be used for identity verification. The agent explains that the ID will be checked against the face on screen, and that a live presence check may be used to reduce obvious impersonation risk.
That small exchange changes the whole tone of the session. Instead of feeling pushed through a mystery process, the customer can see what is happening and can stop to ask questions if the flow is unclear. For the business, that usually means fewer disputes over what was collected and better discipline in the verification file. It also gives the operations team a cleaner base for review when they look at sessions from different branches or client groups.
Consent works best when it is spoken, not hidden in a long block of text. The customer should hear it, understand it, and then move into the check without feeling blindsided.
Keeping consent steady across integrations and training
When a video verification service connects into a client workflow, consent cannot be left to chance. Integration planning should show where the consent prompt sits, what the customer sees before the session starts, and how the record is tagged after the session ends. If the flow changes, the script and the staff training need to change with it.
For South African businesses that use our contact form to start a project, the most useful work is often the practical work. That includes workflow mapping, API coordination, escalation design, pilot launch support and refresh training. The aim is to keep the consent step visible, repeatable and easy for staff to follow without turning the session into a long lecture.
- Map the consent step into the wider onboarding flow.
- Align the agent script with the system prompts.
- Train staff on how to explain recordings and stored files.
- Review the process after changes to the client workflow.
Small checks that make the consent step hold together
The best consent process is not loud, it is clear. Staff should listen for hesitation, explain the next step before it happens, and keep the customer informed when a document image needs to be retaken. That makes the session feel ordered and gives the customer a fair view of what the business is doing with their details.
For teams in Johannesburg, Pretoria and Rosebank, the practical test is simple. Can a customer say afterwards that they understood the purpose of the session, the capture of their ID, the face comparison, and the handling of the record? If the answer is yes, the consent step has done its job. If not, the script needs a tighter line or a better handover between the system prompt and the agent's voice.
