How to reduce duplicate airtime orders during busy periods
A customer is waiting, the till goes blank and the cashier is tempted to press Send again. The supplier may already have accepted the first order. Give every sale a reference, check the first request through the supplier's status route, and follow the approved retry process only once you know the result.
Make an order awaiting a result visible to other cashiers as well. Hand the check to a designated operator and tell the customer when they can expect an update. The next person at the till should be able to see that this sale is already being handled.
Counter workflow
| Moment | Staff action | Record to keep |
|---|---|---|
| Before submission | Confirm recipient, product and value | Internal sale/request ID |
| After submission | Capture the supplier reference | Original reference and time |
| Response is missing | Mark the request pending. Do not start over | Screen or status evidence, if safe |
| Follow-up | Check the original request using approved method | Status source and check time |
| Failure is confirmed | Use the authorised retry or correction path | Link the next action to the first case |
By Freepaid · Published
Make in-progress work visible
The operator needs to see whether a request is already being handled. Use a till or work queue that distinguishes a new sale from a submitted request awaiting a response. If the existing software does not offer that, define a simple internal log or handover method that does not expose sensitive values to bystanders. A separate paper record may work for a small outlet, provided it is controlled and reconciled.
Give the cashier one unique internal request ID before the supplier order is made. Store the supplier's reference against it as soon as available. That internal ID is not a replacement for the supplier reference. It helps link the customer receipt, till record and later investigation. If a request changes hands, the next operator should be able to see that it is still open.
Worked example: timeout on a R10 sale
A customer requests an illustrative R10 recharge. The till submits the order but the response does not appear. The cashier records the sale ID, original reference if available, time and value, then marks the transaction for review. The customer is told that the result is being checked and is given the receipt or support route.
The authorised operator looks up the original reference. If the provider confirms completion, the cashier updates the local record and closes the case. If the provider confirms failure, staff follow the approved retry procedure and link the new action to the original case. If the result remains unknown, it stays pending and is escalated. Staff do not submit another R10 order merely because the first screen timed out.
If two of a shift's 30 transactions are still pending at close, hand over both references, the next check time and the name of the person following up. Mark the sales as open so the incoming cashier does not ring them up again.
Reduce accidental repeat actions
If your till supports an idempotency key or other duplicate protection, ask the product owner how it works and test it in an approved environment. Use the documented behaviour when writing the retry procedure. For manual sales, have cashiers search for an open request before entering it again.
Give cashiers a plain status such as “Submitted, check result” when the supplier has yet to confirm the outcome. Reserve “Failed” for a confirmed failure. A supervisor or designated operator can check the pending queue while the cashier serves the next person.
Build and review the procedure
- Map how a counter request moves from customer instruction to supplier result and receipt.
- Choose where staff can see in-progress requests and who can check them.
- Define what evidence to capture when a response is missing.
- Train on one confirmed success, one confirmed failure and one unknown outcome using synthetic examples.
- Review duplicates and near misses by shift, cause and process step.
- Fix the underlying visibility or training gap instead of relying on staff memory.
At the end of each shift, reconcile completed, rejected, pending and unknown requests separately. Investigate any duplicates using their original references and record the outcome. Do not count unresolved transactions as completed sales or use a second order to make a report appear balanced. See the support playbook for roles and evidence handling.