When the first check is not enough
During a remote video identity check, the ordinary path is easy enough. The customer joins a guided session, shows an ID document, the agent compares the face with the document and the account can move forward when everything lines up. In real operations, though, there are sessions that need more than a yes or no.
Escalation design sets out what happens when an ID is damaged, the photo is unclear, the person’s appearance has changed, the consent step was missed, or the case needs extra review under your own onboarding rules. It also gives your team a clean route for follow-up when the first session ends with an open question.
- Document quality issues, including glare, crop loss and blurred text
- Face comparison concerns where the live image is not a clean match
- Liveness doubts, such as poor camera conditions or distracting movement
- Consent and record-keeping gaps that need a controlled restart
The escalation map we build around your workflow
We shape the escalation path to fit your onboarding flow, not the other way round. The route can be simple for smaller teams or split into more steps where different people handle document review, case handling, training and final decision-making.
The working version usually shows who sees the case first, what evidence they need, when a second agent gets involved, and when the matter is closed or sent for further review. That keeps the team from guessing in the middle of a live queue.
- Front-line agent action for common session problems
- Supervisory review for unusual document or identity concerns
- Follow-up handling where a fresh session is needed
- Record notes that support audit trails and internal reporting
What the service includes in practice
Escalation Design covers the practical parts that sit between policy and day-to-day work. We look at the triggers, the handovers, the messages used by the team and the notes that need to sit in the customer record. If your business works with different client types, we can split paths by risk level, document type or onboarding route.
The result is a set of steps your team can use without improvising in the middle of a verification session. It also gives your training material a firmer structure, so new staff do not learn the process from scattered notes.
- Trigger points for unusual or incomplete sessions
- Decision branches for retry, review or stop
- Message wording for customer follow-up inside the workflow
- QA checkpoints for records, notes and supporting evidence
- Internal handover steps for support or supervisor review
How we shape the process with your team
We begin by looking at the live path your customers follow, from session start to account opening. Then we mark the places where escalations actually happen, not the places that look neat on paper. In many businesses, the best route is the one agents can remember under pressure and still record correctly.
After that, we build the escalation logic in plain language, test it against sample scenarios and adjust the wording where it feels too broad or too narrow. Where needed, we also link the process to staff training so the handover steps do not sit in a file nobody uses.
- Workflow review and issue mapping
- Draft escalation paths and handover notes
- Scenario testing with real session examples
- Alignment with training, reporting and QA checks
Turnaround, scope and pricing shape
Pricing depends on the size of the workflow, the number of escalation branches and whether the work sits beside integration planning, training or quality monitoring. A single service line with a small set of review points is different from a multi-team onboarding flow that needs layered handovers and reporting notes.
We quote against the scope you send through our contact form, then size the work around the amount of mapping, writing and testing needed. If the service is part of a wider rollout across Johannesburg, Pretoria, Cape Town, Durban or Gqeberha, the scope usually includes more coordination between teams and more detailed operational notes.
- Small scope: one workflow, a few escalation paths
- Medium scope: several case types, more handover points
- Larger scope: multi-team review, reporting links and training notes
Aftercare for live cases and changing rules
Once the escalation paths are in use, questions usually come from real cases rather than theory. A customer may present a document with a damaged corner, an agent may need a clearer route for a doubtful match, or the business may change how a follow-up case is routed. We stay close to the working process so the escalation notes do not drift away from the actual job.
That support can include refresh training, change request handling and small updates when a workflow changes. If your team wants the path reviewed after a pilot or a policy update, we can adjust the sequence and tidy the language so the staff notes stay usable.
- Refreshes for new staff or revised procedures
- Change requests when the workflow shifts
- Pilot-stage fixes for unclear handovers
- Reporting updates where case trends need better tracking
Key facts
| Service | Escalation Design |
|---|---|
| Base | Rosebank, Johannesburg |
| Coverage | South Africa, including Johannesburg, Pretoria, Cape Town, Durban and Gqeberha |
| Focus | Remote video identity verification escalations |
| Typical triggers | Unclear documents, mismatch concerns, consent gaps, unusual cases |
| Related work | Workflow Mapping, Staff Training, Quality Monitoring, Go Live Stabilising |
