High Risk Escalation

When a case needs a second set of eyes

Some onboarding files are clean from the first step, while others need closer handling because the image is unclear, the ID document is worn, the session is interrupted, or the recorded answers do not line up with the applicant’s details. High Risk Escalation gives your team a controlled route for those files, so the matter does not sit in the middle of the queue with no owner.

In practice, the case is flagged inside the video verification workflow, then passed to a senior reviewer or an assigned risk team member under your onboarding rules. The reviewer can check the live session record, the document images, the face match notes, the consent trail and any agent comments before the final decision is made. That keeps the process tidy when the case is not straightforward.

• Useful for blurred IDs, cropped images and poor lighting
• Useful when a face comparison needs a second review
• Useful where the answers given in session need follow-up
• Useful when your internal rules call for extra sign-off

Routing that matches the file, not the noise

This service is built around client-defined thresholds. A bank, insurer, credit provider or other regulated business may treat the same file differently, depending on product risk, customer profile and channel. The escalation path can be set so that one type of exception goes straight to senior review while another is held for a training-led recheck or a document resubmission request.

The routing can also separate operational issues from true risk issues. If the internet connection drops in the middle of a session, that may need a restart. If the identity document is valid but the face match is weak, that may need a higher review tier. If the applicant refuses consent or will not complete the live checks, the flow can stop at the point your rules require.

• Queue labels for document risk, identity mismatch and consent issues
• Different handling paths for low, medium and high concern files
• Notes fields for reviewer comments and next steps
• Optional hold status while evidence is checked

Where the escalation layer fits in the workflow

High Risk Escalation usually sits between the first verification pass and the final onboarding outcome. It works well for remote customer journeys where a guided video session is already in place and the business wants a controlled pause before approval, rejection or request for more information. That makes it a strong fit for teams with more than one sign-off level.

It is also practical for operations that run across Johannesburg, Pretoria, Cape Town, Durban and Gqeberha, where different branch teams may need the same rule set but with local oversight. The escalation path can be linked to workflow mapping, escalation design and operational reporting, so managers can see what was flagged, what was cleared and what stayed open for follow-up.

For client teams in Rosebank, Sandton and Midrand, the service fits onboarding counters, risk units and customer success teams that want one process across the full intake chain. It also helps when staff training has to match the live process, not a loose written note that gets interpreted differently by each agent.

Setup, integration and staff handling

The product is usually fitted into your current onboarding stack through workflow mapping, API coordination and script design. That means the escalation trigger can sit inside the session rules rather than being managed by hand at the end of the day. Your team can see which fields must be completed before a senior review opens, and which ones should be locked until the file is resolved.

Integration planning matters because the escalation path needs to talk to the rest of the journey. If your onboarding platform stores documents, logs session actions and tracks reviewer decisions, the handover should be clean. Staff training then covers the practical side: when to flag, what to note, who can review, and which customer updates are allowed under your internal process.

• API coordination for case status changes
• Agent script design for high risk situations
• Escalation design with named reviewer roles
• Go live stabilising for the first live files

Controls, records and the paper trail

Video KYC flows normally need clear records of consent, identity evidence, session notes and final outcomes. High Risk Escalation supports that by keeping the review trail visible and linked to the file, so the reason for the hold or the decision can be traced later if needed. That matters for internal audit work, customer queries and general due diligence under the client’s own onboarding rules.

The process can include liveness checks, face comparison notes, document capture quality markers and reviewer sign-off fields. Where a case is sensitive, the record can show exactly when it moved into senior review and who handled the next step. The goal is orderly handling, not guesswork, and certainly not a loose inbox full of half-checked files.

• Consent log attached to the session record
• Reviewer name, time stamp and outcome note
• Document image quality flag and follow-up reason
• Audit-ready status history for each escalated case

Case sizes, options and practical specs

High Risk Escalation can be configured as a light triage layer or a full multi-step review path. Smaller teams may only need one senior reviewer and a short hold state, while larger operations often want separate queues for document issues, identity mismatch, consent problems and exception approvals. The shape of the setup depends on your onboarding volume, your sign-off rules and the number of staff members who must touch the file.

Typical options include reviewer queues, priority tags, hold reasons, comment fields, escalation counters and reporting by branch or team. For businesses with more complex controls, the path can be built to support pilot launch support, refresh training and change request support, so updates do not disturb the live workflow. In busy environments, that keeps the process practical and easier to manage from Rosebank or from a distributed national team.