Exception Case Review

When a file needs a second set of eyes

Not every onboarding file lands in the standard lane. Some cases arrive with worn identity documents, unclear camera images, mismatched names, changed surnames, border document formats or a customer whose live image needs extra comparison. Exception Case Review is the controlled review path for those files, so the case can be isolated and checked before it passes into the next step.

The service is set up for remote verification teams that handle South African customer due diligence in a structured way. A trained agent can pause the normal flow, capture the ID document again if needed, compare the face to the document image, run the live check carefully, and record the outcome with the supporting notes. That makes the review easier to audit later and less messy for operations staff who need a clean file trail.

In practice, this works well for banks, lenders, insurers, legal intake teams and account opening counters that receive a small number of awkward cases every day. It also helps when a customer is signing up from another city, using a phone with a poor camera, or sending document images that need extra clarity before the file is accepted.

What the exception review pack includes

The review pack can be set up around your internal rules and the level of scrutiny your staff need. Some teams want a short manual check and sign off note. Others need a fuller review with extra image capture, clearer case notes, script prompts for the agent and a stronger escalation path. The workflow can be mapped to fit the way your onboarding team already works.

• Live video session for a guided exception review
• ID document recapture where the first image is unclear
• Face comparison against the document image and live session
• Liveness checks to reduce impersonation risk
• Agent notes, case tagging and outcome recording
• Escalation route for unusual or unresolved files
• Operational reporting for the review queue

Where a business has more than one onboarding channel, the exception path can sit beside the main journey without changing the whole process. That helps teams keep things consistent across Johannesburg, Pretoria, Cape Town, Durban and Gqeberha, while still letting local operating rules show in the scripts and review notes.

Sizes and operational options for different queues

Exception Case Review is not a one shape fits all service. Smaller teams often need a light review lane for a few unusual files a week, while larger operations need a broader queue with several agents and tighter case handling. The service can be scaled to match the number of documents you expect to isolate, the number of review steps you need, and the amount of reporting your compliance or operations team wants to see.

Some clients keep it very lean, with a single review path and one escalation level. Others want separate rules for document quality issues, face mismatch flags, missing fields, customer name changes and repeat attempts. Staff training can be aligned to those options so the team knows when to continue, when to pause and when to move a file into a higher review level.

• Single review lane for low volume exception files
• Multi level review for larger onboarding queues
• Script variants for document, face and liveness issues
• Custom notes fields for internal audit records
• Pilot launch support before full use across the team

Where a business already has an existing digital onboarding flow, exception handling can be planned as a separate branch rather than a full redesign. That keeps the main path clean and lets the unusual files receive the attention they need without slowing every other customer.

Where the service suits best

This product suits businesses that onboard customers online and still need a careful human check for edge cases. It is useful where FICA style customer due diligence is part of the intake process and the team needs a sensible way to manage unclear identity files without losing control of the record trail. The review can support account opening, profile changes, recovery cases and other moments where the document picture needs extra scrutiny.

It also fits teams that work with mixed device quality, older documents, or customers who do not complete the first capture cleanly. In those situations the issue is often not the customer, but the file quality. A focused exception review gives the operator room to check the image, compare the face, and decide whether the file can move forward or needs escalation.

Rosebank based coordination works well for national teams because the process can be run remotely, with training and operational support for staff in different provinces. That matters when you need a practical process that your team in Sandton can follow in the same way as your staff in Cape Town or Durban.

Fit out, integration and team training

There is no physical installation in the warehouse sense, but there is a proper setup step. Your team needs the review flow mapped, the integration touchpoints planned, and the staff trained to use the exception path without hesitation. Jared Jantjies handles integration planning and API coordination, while Anele Nortje can shape the training so the reviewers know the sequence and the wording to use.

For client systems, the exception review can be linked into your existing onboarding environment through a planned handover point. That may include case status updates, script prompts, outcome fields and escalation markers. If your operations team wants extra oversight, quality monitoring and refresh training can be built into the support plan too.

• Workflow mapping for your current onboarding steps
• Integration planning for case routing and status changes
• Agent script design for unusual file handling
• Staff training for review teams and supervisors
• Change request support when your process shifts
• Go live stabilising during the first live cases

Because the work is remote, your internal team can keep the review moving without needing a physical counter or paper handover. That suits offices that already handle digital sign ups and want a clear way to manage the odd file that needs more care.

Care, record keeping and the details to confirm

Exception case handling depends on clean records. Each review should keep the captured document image, the face comparison outcome, the liveness result, the reviewer note and the final case decision in a way that is easy to trace later. Consent and record keeping should sit inside your normal POPIA aware process, with only the information needed for verification stored and handled under your internal controls.

When ordering this service, confirm the review categories you want, the fields that must be completed, the escalation levels, the languages or scripts your agents need, and the documents your team expects to see. It helps to define how a case is marked if the photo is blurry, the name has changed, the document looks altered, or the live session raises a flag.

Care is mostly about process discipline. Quality monitoring can catch drift in script use, and refresher training helps the review team keep the same standard across busy weeks. Leila Petersen can support quality checks, while Megan Vermaak can track client handling and operational reporting so the exception flow stays orderly.

For ordering, it also helps to confirm whether you want separate treatment for South African ID cards, passports or other accepted identity documents, and whether your escalation route must involve a supervisor, an operations lead or a compliance contact inside your business.