Airtime or data for staff and customers?
A clerk who spends the day calling customers needs airtime. A driver uploading proof of delivery needs data that works on their phone and network. If a job involves both, try an allowance that covers both tasks and check which part people run out of first. For a customer reward, start by asking whether you’re promising airtime people can spend as they choose or a specific data bundle.
| What needs to happen? | Start here |
|---|---|
| Staff need to call customers who are reachable by phone | Test airtime against call usage |
| Drivers need a routing app and must upload proof of delivery | Test data with the real app and devices |
| Recipients choose how to use an airtime reward | Compare direct airtime with a redeemable airtime voucher |
| A single role needs calling and uploading | Run a mixed allowance and review each component |
By Freepaid · Published
Write down the task before you buy a product
Use one line per role. A field worker must receive a route, make calls when an address is unclear and upload an image at the end of a visit. An appointment clerk makes outbound calls from a mobile line and spends most of the day at a site with working Wi-Fi. A customer reward may have no work task attached at all. Putting each group on the same allocation hides which problem the purchase solves.
Capture the device and network used for the task. A personal phone may have more than one SIM. Ask which number and data connection the person uses for the work, then verify that the intended product can be delivered there. If coverage causes the problem, buying a larger allowance on the same setup may have little effect. Treat network choice and allowance size as separate checks.
Start with a small, measurable allowance
Take a team with 12 field workers and eight staff making follow-up calls. For a one-week trial, it puts aside R45 per field worker for a data product and R25 per call-back worker for airtime. That is R540 for field data and R200 for airtime, a total planned allocation of R740 before fees or exceptions. Use those amounts to set a trial budget, then check what the available bundles actually cover.
Record whether the field workers completed the upload task on schedule. Record whether call-back staff could make the planned calls. Count the people who needed an extra allocation and ask what happened in each case. An unexpected video upload, a faulty device and a larger call workload need different responses. Keep the names and mobile numbers in the operational roster, with only counts and categories in the summary.
Check the conditions that affect the result
For data, check compatibility with the mobile network, product validity, applicable time restrictions and the actual task. Test any company app with Wi-Fi off under representative conditions. If the product is a bundle for a specific service or time period, make sure those limits fit the work before purchasing for a team.
For airtime, confirm what the benefit is expected to fund. Where the goal is data access, confirm that the chosen product explicitly provides it or verify the recipient's available conversion process. If the business needs to know the upload happened, measure completion of the upload as well as successful delivery of value.
Adjust the next cycle by role
After the trial, compare each group's original budget with what they received and what they needed to finish the work. Keep an allowance when most people completed the job and the exceptions were easy to explain. Adjust it when a repeated shortfall has a consistent cause. Put unusual cases through a small reserve with approval so that one exception does not reset the policy for everybody.
For a regular staff allowance, look at SIMcloud for direct airtime or data top-ups. For a customer reward people can redeem themselves, look at AllNetAirtime’s vouchers. SIMcloud · AllNetAirtime