Airtime Survey Incentives South Africa: A Research Guide

Research agencies can distribute airtime incentives in South Africa by sending an approved respondent list through a bulk recharge portal, or by connecting their research system to an airtime API. The critical record is the link between an eligible participation event and its final recharge result. A completed questionnaire and a completed reward are two different events.

This guide is for research operations managers, panel owners and organisations running repeated surveys. It explains when airtime is a suitable incentive, how to budget a wave, and how to keep a reward ledger that answers a participant’s query without exposing their survey answers.

When are airtime incentives suitable for a survey?

Airtime is worth evaluating when participants use supported South African mobile numbers, the reward is a modest phone-credit amount, and the research team needs a traceable distribution process. It may be unsuitable when participants need cash reimbursement, use ineligible services, or expect a redeemable voucher instead of a direct recharge.

There is a documented local precedent. The University of Stellenbosch’s 2020 CRAM-MATCH study, archived by UCT DataFirst, provided R10 airtime to participants. This is an example of a research payment method, not a recommended incentive value for a new study or evidence that SIMcloud supplied that project.

Commercial research providers also use mobile incentives: GeoPoll describes incentive delivery alongside its South African mobile research services. That establishes an existing use case. It does not establish that airtime will improve the response rate for your particular audience.

Separate access support from the participation reward

If respondents need connectivity to open the questionnaire, a reward delivered only after completion cannot solve their initial access problem. Decide whether you need data before participation, airtime after an eligible response, or both. Keep the two allocations separate in the budget and ledger.

Do not promise a universal improvement in response. A 2024 randomised study by Lockwood and Lieberman found that the material incentives tested did not increase survey participation among South African local councillors. That result concerns a specific political population and incentive design; it is not a test of SIMcloud or a general verdict on airtime. It is a reason to pilot the incentive with the audience you actually need.

Direct airtime, data, voucher or cash?

SIMcloud’s airtime API purchases a direct recharge, not an airtime PIN. The bulk portal supports airtime purchases across Vodacom, MTN, Cell C and Telkom. Confirm an uncertain recipient’s current network with the network lookup tool; an old number prefix is not sufficient evidence.

Write the reward rules before the survey goes live

A respondent should be able to understand the offer without knowing how your fulfilment software works. State the reward product and value, the activity required, the expected fulfilment window, the number that will receive it, and the contact route for a missing reward.

Decide how screening, partial responses, repeat submissions and follow-up waves will be handled. Apply the terms communicated to participants; do not invent exclusions after they have completed the activity. Where a research approval process applies, agree the incentive and wording through that process before recruitment.

Use a study-and-wave identifier rather than a mobile number alone as the basis of your entitlement record. One participant may legitimately earn rewards in several waves. Conversely, repeating the same completion event must not silently create a second reward.

A shared phone is a review flag, not automatic proof of fraud. Check the study’s participation rules before rejecting an allocation. Keep disputed eligibility separate from delivery failures so the fulfilment operator does not have to make research decisions.

Budget a 1,000-person research wave

Suppose a wave has 1,000 approved reward events, each carrying R25 airtime. The promised airtime face value is 1,000 × R25 = R25,000. This is illustrative arithmetic, not a quote, a recommended incentive or a predicted response rate.

The funding plan should also account for the actual supplier purchase prices and any applicable charges, participant communications, operator time and approved additional allocations. Keep an emergency provision under a separate approval rule; do not automatically turn a complaint into another recharge.

The counts reconcile to 1,000, but the wave is not fully fulfilled. These face-value totals also do not prove the wallet balance: finance must reconcile the actual purchase and billing records. Keeping those questions separate prevents a reassuring batch total from hiding unpaid participants.

Build a reward ledger without copying the questionnaire

Your research system or controlled spreadsheet should retain the following fields. This is a proposed operating record for your team, not a claim that SIMcloud automatically imports or manages your research data.

Keep questionnaire answers outside the recharge file. A short reference such as ST24-W2-P0184 can connect the records without putting a respondent’s answers or study-specific sensitive information into an order description. Limit access to the file containing phone numbers to the people who need it for fulfilment.

Use a reviewed batch or connect your panel software

A CSV batch suits scheduled reward runs. Export approved events, check them against the reward ledger, and use the official msisdn,network,value,reference template. The airtime bulk flow accepts R2–R999 per row and retains up to 30 characters of the reference. The CSV guide covers field formatting; the bulk airtime walkthrough covers submission.

An API suits rewards triggered by your software. Your backend should approve and record the reward event before requesting the recharge, preserve the returned request identifier, then query its final status. A survey-page refresh must not create another entitlement. SIMcloud does not decide whether a response is valid.

The published airtime API rejects the same number and amount within five minutes with HTTP 409. That is not permanent protection against duplicate reward events. It can also affect two legitimate same-value rewards for the same number submitted close together. Plan the queue around the documented behaviour and resolve the original outcome before retrying. The API evaluation guide explains the distinction.

What a useful fulfilment pilot should prove

Choose an authorised group representing the networks and products in the real wave. Agree the budget and support arrangements before placing paid orders. During the pilot, record:

• Whether approved events produce exactly the intended purchases.
• How long purchases take to reach a final result on each required network.
• Whether an operator can locate a complained-about reward from its study reference.
• How pending orders, confirmed failures and number corrections are resolved.
• Whether finance can explain the purchased value and outstanding entitlements.

Report reward delivery separately from survey completion and response quality. A reliable fulfilment process can honour the offer; it cannot make a sample representative or guarantee useful answers.

Discuss your research incentive programme with SIMcloud

Bring the number of reward events per wave, waves per month, proposed product and value, network mix, busiest submission period, intended turnaround and launch date. Specify whether you need reviewed CSV runs or a backend integration. Those details make it possible to evaluate purchasing value, funding and operating requirements.

Discuss research airtime fulfilment with Dave, or register to prepare a small approved pilot. Account registration is free; purchases require wallet funding.

Research incentive questions

Sources and SIMcloud product documentation checked on 29 September 2026. Research examples are attributed to their original authors and are not SIMcloud customer case studies.