Instant Join Flow

A straight-through join path for live onboarding

Instant Join Flow is the live verification option for teams that want the customer moved from application into a guided video session with as little friction as possible. The customer opens the session from a secure link, follows on-screen steps, shows an ID document clearly, and the trained agent carries out the checks while the account opening record is updated in the background.

It suits businesses that already have an online form, a customer portal, or a call-centre assisted sign-up process. The flow can be mapped so the join screen, consent step, document capture and final verification outcome sit in one clean sequence instead of being spread across different tools and messages.

Session formats and operating sizes

The service can be set up as a single-verification flow for lower volumes, or as a multi-agent workflow for larger queues and branch-linked teams. Some clients want a simple browser join route for benchtop and mobile users, while others need a stricter path with scripted prompts, staged document capture, and a more detailed outcome record for audit use.

• Single-session join flow for straightforward account openings
• Multi-agent queue design for higher daily volume
• Mobile-friendly join screen for customers on a handset
• Benchtop route for staff-assisted onboarding at a branch or call centre
• Branch-tied routing for Johannesburg, Pretoria, Cape Town, Durban and Gqeberha teams

Where a business works across more than one region, the setup can separate client queues, verification rules and internal handover notes without forcing every branch into the same pattern. That helps when Rosebank, Sandton or Midrand teams handle different account types from the coastal branches.

What happens inside the verification session

The live session normally follows a clear sequence. The agent confirms the customer, asks for the ID document to be shown in frame, checks the face against the document image, and applies liveness checks to reduce the risk of replayed footage or a still image being used. Consent capture and record keeping can be built into the flow so the business keeps an internal trail of what was shown and when the session was completed.

For FICA-style customer due diligence, the join path needs to support practical controls rather than a rushed screen grab. That usually means visible document edges, clear lighting, steady camera framing and a session script that tells the customer what to hold up and when to move. The workflow should also allow escalation when the image is poor, the document details do not line up, or the user needs to restart the capture step.

Integration planning for online account opening

Instant Join Flow fits best when the onboarding stack is planned before the first customer enters the queue. We map where the join link lives, which fields are passed into the verification screen, what status moves back into the client system, and how the outcome is shown to staff who open the account later in the chain.

• API coordination for customer records and outcome updates
• Workflow mapping for the join screen and verification steps
• Agent script design for consistent document requests
• Escalation design for poor image quality or mismatched details
• Go live stabilising when the process is first switched on

Some clients only need the join flow sitting beside an existing application form. Others need tighter links with internal onboarding tools, branch queues or case notes. That is where integration planning becomes important, because the customer should not need to repeat the same information three times before the session begins.

Care, quality checks and staff handling

Because the service depends on human review, care is really about process discipline. The verification team needs a clear script, a stable handover from the application step, and a quality monitoring routine that checks how documents are captured, how liveness prompts are handled, and whether the outcome records remain readable for internal teams.

Refresh training helps when staff change, the document mix shifts, or a client updates its internal rules. Change request support matters too, especially when a business adds a new product line, wants a different escalation path, or needs the pilot flow adjusted for branch staff in a city office. A quality lead can review session handling, while the training coordinator keeps the instructions practical and consistent for new users.

Details to confirm before the join flow is set up

The details that matter are usually the ones that affect the join path, not the marketing wording around it. Check what document types the customer must show, whether the session is meant for mobile or benchtop first, which staff should receive the outcome, and whether the business wants one common script or different scripts per product line.

• Customer journey entry point and join link placement
• Accepted document types and image capture rules
• Queue structure by branch, team or product line
• Consent wording and record keeping requirements
• Internal escalation route for unclear images or mismatched data
• Reporting fields needed by operations and compliance teams

Where a client works across Johannesburg, Pretoria or the coastal branches, the join flow may also need local routing so the right agent pool sees the right session. That keeps the onboarding process orderly when volumes shift through the week and staff need a clear place to pick up the next case.

Care notes for a busy verification line

The flow stays at its best when the customer is told what to prepare before the session starts, the camera prompt is easy to follow, and the agent is not forced to rescue the process from weak instructions. Keep the document images legible, check the face match carefully, and store the session record in a way that suits your internal policy.

When the process is used heavily, quality monitoring should watch for repeated capture failures, rushed handovers and script drift. If the join path is clean, the customer feels less friction and the business gets a neater record of who was verified, what was shown and how the account opening moved forward.