How to run a small bulk airtime pilot before committing
A good airtime pilot follows a few approved orders from purchase to delivery, support and reconciliation. Agree what you need to learn, who can take part and how much you can spend before you send the first top-up. Set a stopping point, especially for an order you can’t confirm.
Pilot card
| Item | Decide before ordering |
|---|---|
| Question | What uncertainty must the pilot resolve? |
| Scope | Product, value, count, cohort and duration |
| Controls | Approver, spend cap, account access and stop owner |
| Evidence | Order reference, status, receipt confirmation and report |
| Exit | Reconciliation date and decision owner |
By Freepaid · Published
Pick one question to answer
Avoid testing everything at once. A retailer might need to know whether the till workflow gives a cashier enough evidence to close a sale. Finance may need to verify that an export can be matched to its ledger. A campaign owner may want to compare the work involved in distributing direct recharge and redeemable PINs. State the primary question and the evidence that would answer it.
Keep commercial evaluation separate from technical acceptance where possible. If you need a product, price or support answer, obtain it from the supplier in writing instead of treating a handful of test orders as proof of general service levels.
Set the budget and choose test cases
Choose a small quantity and value that can be approved and reconciled by the pilot team. Use consenting participants or test accounts you control. Define product, network requirements, recipient channel and completion date. Confirm actual cost and any applicable fees before ordering.
Create a test register with one row per case: test ID, internal reference, product and value, authorised recipient or test destination, order time, supplier reference, observed status, evidence and follow-up owner. Do not put passwords, full payment details or unnecessary personal data into a shared sheet.
Define pass, fail and stop conditions
Set pass criteria before testing. For instance, every order must have a unique internal reference, the operator must be able to find the supplier’s result, and finance must be able to match the total to the statement. Have staff show how they would handle a pending order. If you get an unclear response, check the original reference before sending anything again.
Stop if the approved spend cap is reached, the wrong product or recipient is selected, access appears unauthorised, or the team cannot establish the order outcome. The named pilot owner should pause and contact the supplier. Do not keep testing to “see if it clears” when the balance or recipient impact is uncertain.
Run and document the pilot
- Obtain written approval for product, maximum spend, cohort and test dates.
- Confirm account permissions and who may initiate or approve orders.
- Review current ordering instructions and support contact.
- Place only the planned orders, recording internal and supplier references.
- Check each result using the documented status path. Retain evidence safely.
- Ask participants only the questions needed to confirm receipt or usability.
- Reconcile the order register, supplier report and funding or invoice record.
- Record exceptions, handling time and who resolved each issue.
Five R20 test orders would use R100 of the budget before fees. Set the cap from the cases your team needs to run and the charges the supplier quotes.
Decide what happens next
Record what you set out to test, what happened, what it cost and what’s still open. Choose whether to proceed to a larger controlled phase, amend the workflow and repeat a bounded test, or stop and evaluate another option. Name the approver and date. Expansion should include a new volume forecast, access review and reconciliation capacity.
For available business purchasing channels, see Freepaid bulk airtime. Confirm current product, pricing and pilot arrangements directly.