Open with purpose, not a lecture
The first lines set the tone for the whole session. A customer should hear what is happening, why the call is taking place, and what will be asked next, without a long speech that sounds rehearsed. Short sentences help the agent stay calm and keep the customer focused on the task.
A practical opening names the process in plain words. It tells the customer that the session is for identity verification, that an ID document will be checked, and that the face match matters. In South Africa, where many people join from a phone on a noisy commute or from an office lobby in Sandton, a clean opening saves time and cuts confusion.
- Say what the session is for.
- Explain that the ID document must be visible.
- Tell the customer to stay in a quiet place if possible.
- Ask for steady lighting before the first capture.
Build the script around the real screen flow
The best scripts follow the order that the customer sees on screen. Agents should not jump ahead or speak in abstract terms. If the system asks for an ID document first, the script should support that moment, then move to the face check and the final confirmation. That rhythm keeps the conversation natural and reduces repeated instructions.
For a Rosebank team serving customers across Johannesburg, Pretoria and Cape Town, the wording must work for different devices and different digital comfort levels. A good line does not assume the customer knows the steps already. It gives one instruction at a time, then pauses long enough for the customer to act.
- Match the script to each screen prompt.
- Keep instructions short and sequential.
- Avoid two tasks in one sentence.
- Use the same wording each time the step appears.
Use clear language for ID checks and face comparison
Agents need wording that explains document capture and face comparison without overloading the customer. A plain line about holding the ID flat, removing glare, and keeping all corners visible is easier to follow than a technical explanation. The same applies when asking the customer to look at the camera for a live face check.
Scripts should also cover the small pauses that matter. If the image is blurry or the light is poor, the agent needs a calm correction. The customer should understand that a second attempt is normal, not a sign that something is wrong. That is especially helpful for clients in Durban or Gqeberha where people may join from mixed indoor and outdoor light.
- Ask for the full document, not a cropped edge.
- Tell the customer to remove any cover or sleeve first.
- Use plain words for lighting and focus.
- Keep face comparison instructions short and direct.
Leave room for consent and record keeping
Good scripts must handle consent in a way that feels clear, not heavy. A customer should know that the session is being recorded or stored where that applies, and that the business keeps records for its own verification process. The wording should stay general and practical, without turning into legal advice or a lecture on policy.
In a South African setting, script wording also needs to respect privacy expectations under POPIA and the due diligence steps common in FICA workflows. That means agents should speak plainly about data use, storage and verification records. They should not improvise. When the script is fixed and well tested, customers hear the same careful wording every time.
- State that consent is part of the process.
- Explain record keeping in straightforward language.
- Keep privacy wording consistent across sessions.
- Avoid legal jargon unless the business has approved it.
Train for edge cases before they reach the call
A script gets tested hardest when the session does not go smoothly. The customer may have a damaged ID, a reflected screen, a shaky camera or a crowded room. Agents need wording for those moments so they can guide the customer without sounding impatient. Good training turns those awkward spots into routine steps.
PersonVideo ID works with businesses that want staff training, escalation design and quality monitoring around their verification flow. In practice, that means the script should give agents a safe path when they need to pause, repeat or move a customer to another step. A rushed line can create more confusion than the original problem.
- Prepare wording for blurry images and glare.
- Allow a script line for failed face match attempts.
- Use a calm tone when asking for a retake.
- Give the agent a clear escalation cue.
A Johannesburg script that sounds local without trying too hard
A useful local example is a mid-morning verification for a small finance team in Rosebank onboarding customers from Pretoria and Midrand. The customer joins from a phone, the agent opens with one clear sentence, and the process moves from consent to ID capture to face comparison without extra chatter. That flow feels respectful and efficient.
What matters most is not fancy wording. It is the ability to help the customer finish each step with confidence. A solid script keeps the agent on track, protects the customer from confusion, and gives the business a repeatable way to handle online onboarding across South Africa.
For businesses planning new scripts or updating old ones, our contact form is the place to send the brief. The team can then map the workflow, shape the agent wording and align the script with the rest of the verification process.
