When the video session is not enough
A standard guided video session works well when the customer is calm, the camera is clear, and the ID document is readable. Trouble starts when the image is blurred, the document is damaged, the name does not match the application, or the customer cannot complete the liveness prompts without help.
Exception routing gives each of those cases a defined path. The agent does not guess, and the customer does not get bounced between teams. The record shows what was seen, what was missing, and which reviewer must take the next step.
- Unreadable ID image goes to document review.
- Face match concern goes to verification review.
- Application mismatch goes to client operations.
- Consent concern goes to compliance review.
How the first review sorts the case
The first reviewer should only decide what is visible in the session. They check the ID document capture, the face comparison, the liveness check, and whether the customer gave consent for the process and record keeping. If one part is weak, the case moves, it does not stall in the same queue.
A practical routing table keeps the work tidy. It also makes the handover to another reviewer easier, because the notes already explain the issue in plain language.
- Document damage, clipped edges or glare go to image quality review.
- Mismatch between the selfie and the live session goes to identity review.
- Missing consent wording goes to process control.
- Suspicious session behaviour goes to escalation handling.
What a clean escalation path looks like
Escalation should not mean panic. It should mean that the case needs a different set of eyes, a different script, or a stronger evidence trail before the account can move forward. In practice, that means the team knows who can reopen the file, who can request a fresh capture, and who can mark the case as paused.
Clear routing rules are especially useful when branches and central teams work together. A Johannesburg client may send a case for a Cape Town onboarding team to review, while the operational notes stay in one format. That keeps the record easy to audit and easier to explain during internal checks.
- Pause the file when the document is expired or unclear.
- Send the file for secondary review when the face match is uncertain.
- Request a new session when lighting or camera quality fails.
- Move the case to compliance review when consent is incomplete.
The notes that help later reviewers
Good exception routing depends on good notes. The reviewer should record what happened in the session, what was checked, and why the case could not move straight through. Short notes are fine if they are specific. Vague notes waste time, while a clear line about glare, mismatch, or missing consent gives the next reviewer something real to work with.
For South African businesses handling customer onboarding, the record also helps with internal FICA-style due diligence and POPIA-aligned record keeping. The point is not legal theatre. The point is that the business can show how it treated the case, and why the route changed.
- Record the exact issue seen in the session.
- Note which evidence was readable and which was not.
- Capture the reason for the escalation path.
- Log the staff member who picked up the case.
A Rosebank example with moving parts
A client in Sandton opens accounts for trade customers across Gauteng. Most sessions move through the normal flow, but a few arrive with damaged IDs, poor lighting, or a customer who struggles to hold the document steady on camera. Without routing rules, those files would sit in the wrong place and the onboarding team would have to rework them by hand.
With a defined process, the case moves from the live agent to the right reviewer, then to the team member who can request a better capture or reopen the file for a second look. That is the difference between a noisy pile of exceptions and a controlled queue.
- Rosebank operations can flag the case for second review.
- Integration support can tag the file in the client system.
- Training notes can show the agent which script to use.
- Quality checks can confirm whether the route was used correctly.
Training staff to spot the right route
Routing rules only work when the team knows the signals. Staff training should cover the common failure points, the handover labels, and the words used in escalation notes. That way, a verification team in Johannesburg and an onboarding team in Pretoria can read the same file and understand the next move.
The strongest teams rehearse unusual cases, not just the easy ones. They practise what to do with a faded document, a partial face match, a distracted customer, or a session that needs a fresh consent capture. That practice keeps the process steady when the work is busy.
- Use one script for document issues.
- Use one route for face comparison concerns.
- Use one handover note for consent gaps.
- Use one review line for unclear liveness checks.
Keeping the route useful after go live
Exception routing is not a once-off exercise. After pilot launch support and go live stabilising, the team should review which cases are being rerouted most often and whether the labels still make sense. If one route fills up too fast, the process may need a better decision point or a different reviewer.
That is where operational reporting and change request support matter. The routing map should stay close to the work, so the client team, verification team, and integration lead can adjust without losing the audit trail. A good routing rule is the one people can use under pressure, not the one that looks tidy on paper.
In Durban, Cape Town, Gqeberha, Midrand and Sandton, the customer may never see the route itself. They only feel whether the process is orderly. That is usually the right sign, because the best exception handling is calm, specific and easy to trace.
