Low Bandwidth Practices

Start with a smaller sequence, not a bigger speech

A weak signal punishes long explanations. The cleaner pattern is a short greeting, one instruction at a time, and a pause after each step so the customer can steady the phone and the document. If the script is rushed, the image drops in the middle of the important part and the agent has to start that step over.

For lower bandwidth work, script design matters as much as the camera. The agent needs plain lines that work in a noisy kitchen in Soweto, a quiet office in Sandton, or a mobile session on a lunch break in Pretoria. The goal is not drama, it is a clear record that shows who was present, what was captured, and whether the document and face matched cleanly.

• Keep the first instruction short.
• Separate document capture from face comparison.
• Pause after each frame so the client can adjust.
• Use the same wording every time the step repeats.

Retry handling keeps the session moving

Low bandwidth is rarely fixed by one lucky attempt. Good operations allow a sensible retry path when the image freezes, the audio breaks, or the camera loses focus. That path needs to be simple enough for the agent to follow under pressure, especially when the customer is in a rush and the device is shared between family members.

Retry handling should also protect the integrity of the record. If a document image is blurred, the agent should not force the session forward just to finish quickly. A second capture, with better lighting or a steadier hand, is usually worth more than a shaky image that creates work for the verification team later.

• Repeat the missed step, not the full session.
• Switch to a calmer pace after a dropped frame.
• Ask for a steadier hold before repeating the ID capture.
• Record why the retry happened in the notes.

Face checks need patience on patchy networks

Face comparison and liveness checks can suffer when video quality dips. If the picture is blocky or delayed, the agent may miss a blink, a turn of the head, or a small motion that confirms the person is live on the call. A careful operator will slow the sequence and look for a clean moment rather than guessing from a poor image.

In practice, that means the customer is asked to sit still, face the light, and hold the camera at eye level. It sounds ordinary, but on a narrow connection ordinary steps make the difference between a usable session and one that leaves gaps in the audit trail.

• Keep the face check separate from document capture.
• Ask for stillness before the liveness prompt.
• Use natural light where it is available.
• Hold the session until the image settles, if needed.

The document capture cannot carry all the load

An ID document needs enough clarity for the agent to read the details and compare the image to the person on screen. Low bandwidth can turn a front page into a blurry square, which means the process has to rely on a disciplined capture flow. The agent should guide the angle, keep the frame stable, and avoid talking over the moment when the image is being taken.

Where possible, the session should capture the document in a way that supports later review. That includes enough time for the customer to flip the card or booklet, adjust the light, and hold it flat. It also means keeping notes that explain any missing edge, shadow, or partial frame that affected the capture.

POPIA and record keeping belong in the flow

Remote identity checks involve personal information, so the session must be handled with care. Consent needs to be part of the flow, not a side note, and the record must show what was collected, why it was collected, and how it was handled. For FICA style customer due diligence, that discipline matters just as much as the actual capture.

Low bandwidth can tempt teams to skip a step to save time. That is usually the wrong move. A better approach is to keep the process ordered, note any interruption, and make sure the verification trail still makes sense after a difficult call. Good record keeping reduces confusion when a file is reviewed later by the client team or an internal quality lead.

• State consent before the capture begins.
• Keep session notes tied to the file.
• Note any retry, delay, or failed frame.
• Store the record in line with the client process.

Training the team for weaker connections

Staff training should not assume stable video every time. The team needs to know how to slow down without sounding uncertain, how to rephrase an instruction, and how to move the session forward without losing control. That is where training, quality monitoring, and escalation design work together.

PersonVideo ID supports this through workflow mapping, agent script design, pilot launch support, and refresh training. In a real rollout, a client in Cape Town may have clean fibre in one department and a less stable link in another. A client in Durban may see different device habits across the team. The operational answer is a playbook that keeps the verification steps clear even when the line is uneven.

• Train agents to pause rather than talk over the video.
• Use the same escalation route for repeated drops.
• Review recordings for pressure points in the script.
• Refresh the team when device habits change.

A practical Rosebank example with a Gauteng client

A Midrand lending team may onboard customers online from different suburbs and see a mix of newer phones and older devices. During a weak session, the agent slows the opening, checks consent, captures the ID, then separates the face check from the document step. If the image breaks, the file notes reflect the interruption and the customer is guided back to the exact point that needs another attempt.

That kind of pacing looks plain, but it is often the difference between a neat verification record and a messy one. It also gives the client a steadier handover into the rest of the onboarding workflow. For businesses working across South Africa, from Pretoria to Gqeberha, low bandwidth does not have to derail the process if the steps are planned with care.