Repeat Customer Refresh

A refreshed check for an already-open customer file

Repeat Customer Refresh is a remote video identity session used when a business needs to update an identity record for an existing customer. The person joins a guided video call, presents an identity document, and a trained verifier checks the document details against the live face on screen before the refreshed record is closed off.

This service suits teams that already know the customer but need a newer verification record for internal controls, FICA customer due diligence processes in general terms, or a file review before account activity continues. It is designed for online onboarding teams in Johannesburg, Pretoria, Cape Town, Durban and Gqeberha, with workflow planning that suits different approval routes and customer volumes.

The session is not a heavy setup. It is a controlled identity refresh with clear steps, consistent agent prompts and secure capture of the verification outcome. If a client wants the process tied into their own onboarding stack, our team maps the handover, the data fields and the approval notes before launch.

Session flow and the pieces that make it work

Each refresh session follows a practical sequence. The customer enters the video session, confirms consent for the check, shows the ID document to camera and may be asked to adjust lighting or angle so the document can be read properly. The verifier then compares the document photo with the live face, checks for obvious mismatch signs and records the session outcome.

• Guided video session with scripted identity prompts
• ID document capture for local and cross-border identity files where applicable
• Face comparison against the document image
• Liveness checks through natural movement and prompt response
• Consent capture and record keeping aligned to internal policy
• Escalation notes where a manual review is needed

For higher-risk client groups, the flow can include an extra question set or a second review step before the refreshed file is marked complete. Where the business wants tighter control, the script can ask the customer to show both sides of the document or to repeat a movement prompt for clearer verification evidence.

Sizes, session options and operating fit

Repeat Customer Refresh is offered as a single session type, but the operating setup can be adjusted to suit the client’s workload. Some teams need a light refresh for low-risk repeat customers, while others need a fuller scripted session with extra checkpoint notes and a stricter escalation path. The session can be run in English and can be adapted for operational wording that matches the client’s own onboarding language.

For larger onboarding teams, the work can be grouped into pilot volumes, steady-state volumes or scheduled refresh queues. The support package may include workflow mapping, API coordination, agent script design, quality monitoring and staff training so the business can run the refresh process with fewer handovers. Where the client’s internal team handles the first-line queue, we set out the decision points that matter most, so agents know when to continue and when to escalate.

• Standard refresh session for routine rechecks
• Enhanced refresh session for higher-risk customer files
• Scripted refresh for regulated onboarding teams
• Training pack for internal call centre or verification staff
• Integration support for online forms, CRM fields and case notes

Where the refresh session suits the working week

This product fits businesses that keep customer files open over time and need a fresh identity record before changing access rights, limits or account status. It is useful for finance teams, service platforms, insurance onboarding counters and any operation that keeps customer identity controls under review. The format also suits groups that need a repeat check after a change request, a file review or an internal audit cycle.

Because the session is remote, it can serve customers in Rosebank, Sandton, Midrand, Pretoria, Cape Town, Durban and Gqeberha without a branch visit. That helps businesses with national customer bases keep the process consistent while still handling local operating requirements. For teams that work with agents in more than one city, the same refresh script can be trained across sites so the checks stay aligned.

Where a business has seasonal spikes or a batch of customers needing updated records, the queue can be handled through a scheduled rollout. The client-side team may prefer live reporting, while another may only need daily operational notes and exception counts. Both structures can be supported.

Fitting it into your system without trouble later

The refresh service can be built into existing onboarding flows through API coordination, screen prompts and internal status updates. If the business already has account opening steps in place, the verification point can sit before final approval or before a status change is released. Our integration planning looks at field names, document storage, audit notes and the point where a verifier should hand a case to an internal reviewer.

Staff training covers the agent script, identity prompts, escalation wording and the handling of failed sessions. Quality monitoring can review sample sessions for document clarity, face match handling and consistent note taking. Where a client needs a refined approval route, escalation design can separate low-risk refreshes from cases that need manual attention.

• Workflow Mapping for the refresh journey
• Integration Planning for customer systems and case notes
• API Coordination for data handover
• Staff Training for internal or outsourced teams
• Escalation Design for exceptions and manual review
• Operational Reporting for refresh activity and outcomes

Care, records and the details to confirm

The service depends on clear images, steady camera framing and correct customer consent. Clients should confirm which identity documents are acceptable, whether the refresh applies to all customers or only selected risk groups, and how long the record must be kept under their internal policy. The handling of consent, retention and access to recordings should sit inside the client’s own controls and POPIA-aware records process.

Before a rollout, it helps to confirm the document types, the face match tolerance, whether liveness checks are required on every session and who signs off on an exception. If a business wants additional reporting, the update fields should be listed early so the live file and the stored record carry the same reference details.

• Accepted ID document list
• Retained record format and storage location
• Consent wording and audit note fields
• Escalation route for unclear images or mismatch findings
• Reporting fields for refresh status, reviewer notes and final outcome

Care is mostly about control. Keep the document list current, keep the script short, and make sure every refreshed session lands in the same record format so the next review does not start from scratch.