Scripts that keep the session moving
Our agent script design service turns a busy verification call into a steady sequence of prompts. The aim is not theatre, it is clarity. Each line gives the agent a clean cue for greeting, consent, ID capture, face comparison and closing checks, without making the customer feel rushed or boxed in.
We write for real operating conditions in Johannesburg, Pretoria, Cape Town, Durban and Gqeberha, where teams may handle different accents, device types and customer confidence levels on the same day. The script must hold its shape when a customer is nervous, on a small phone screen, or unsure where to position the camera.
- Opening lines for identity confirmation and consent
- Prompts for ID document capture and image clarity
- Face comparison wording for the live check
- Liveness prompts that stay calm and direct
- Closing lines for outcome, notes and escalation
What we shape into the script
We build the wording around your workflow, not the other way round. If your team verifies South African ID documents, captures a proof of address, or needs an extra step for second-factor confirmation, we map those actions into a script that sounds natural on a live session. The same goes for handover points, retries and escalation wording.
For many clients, the hardest part is not the technology. It is keeping agents consistent when a session moves off script. A good script gives them enough structure to stay accurate, while still letting them speak like a person. That balance matters when the customer is trying to finish onboarding and the agent has three screens open.
- Greeting and identity confirmation lines
- Consent wording for the video session and recording
- Document positioning and image quality prompts
- Liveness check instructions and retry phrasing
- Escalation wording for unclear images or mismatches
How the script gets built with your team
We start with your current onboarding flow, then work through each decision point with the people who use it. That may include operations, compliance, training and the agents who carry the calls. We note where a script needs firmness, where it needs softer wording, and where a single phrase can save time later in the session.
Once the first draft is in place, we test it against common cases: glare on an ID document, a customer with a cracked screen, poor camera angle, or a name that does not match the application exactly. Those details matter because they show where the script needs a backup line or a clearer instruction.
- Workflow mapping and decision point review
- Draft script written for live video use
- Internal review with your nominated team
- Revisions for tone, order and escalation wording
- Final handover with version control notes
Numbers, phrasing and field notes
Script design is more useful when the team has clear specs to work with. We note the number of prompts per stage, the order of checks, the names of optional branches and the points where an agent must pause. If your process needs a shorter call path for low-risk checks, we can trim the wording without losing the control points.
We also pay attention to the small things that affect adoption. A script that is too formal can sound cold, while a loose script can make the session drift. We write for the middle ground, with enough structure for QA and enough plain language for a customer who is not used to digital onboarding.
- Prompt count per stage
- Required and optional verification branches
- Escalation triggers and decision notes
- Tone guidance for customer-facing lines
- Version naming for controlled rollouts
Pricing shape and project scope
Our pricing approach follows the scope of the script set, the number of customer journeys and the amount of review needed. A single onboarding flow is a different task from a multi-step process with several fallbacks, so we quote according to the real drafting and consultation work involved.
Where clients need related work, we can fold in training notes, QA wording and escalation design so the script does not sit alone. That often reduces rework later, because the same language can carry through to staff training and call review. It also keeps the handover cleaner for internal teams that need to keep the process moving across branches or remote staff.
- Scoped per workflow, not per generic template
- Pricing reflects script depth and review cycles
- Optional alignment with training and QA material
- Useful for single-team or multi-site operations
Aftercare for live use and changes
After go live, our support stays focused on the script itself. If your onboarding flow changes, your risk wording shifts, or an edge case shows up during live sessions, we help revise the wording so the team does not keep working around a stale prompt. Small edits matter when agents are repeating the same lines all week.
We also support refresh training when a script has been in use for a while and the team needs a reset. That can include updated talk tracks, replacement lines for awkward moments and clearer escalation wording for supervisors. The point is to keep the script usable, not simply filed away. POPIA record keeping, consent wording and internal decision notes can be reflected in the script where your process calls for them.
- Script updates after workflow changes
- Refresh notes for new or casual staff
- Rewording for exception handling
- Alignment with reporting and QA checks
Key facts
| Service area | Rosebank, Johannesburg with remote support across South Africa |
|---|---|
| Core output | Agent call scripts for guided video identity verification sessions |
| Included focus | Consent prompts, ID capture, liveness wording and escalation lines |
| Related work | Training notes, QA phrasing and change request support |
| Pricing approach | Scoped to workflow depth, review cycles and training needs |
| Typical use case | Businesses onboarding customers online through video KYC |
| Client contact | our contact form on our contact page |
