Data collection
Channels, instruments and how consent is recorded on each.
Who this is for
Anyone running a campaign, and anyone who has to explain the consent record.
Channels
Voice, WhatsApp, SMS, web link and app all enter through one collection pipeline. A campaign published once is reachable on every channel your organization has configured.
How consent is captured
| Channel | Consent basis | Recorded as |
|---|---|---|
| Web link | Explicit — the respondent affirms before any answer is collected | GRANTED |
| WhatsApp, SMS, voice | Notice-based — the welcome message or greeting states that participation is voluntary and how to opt out, before any question is asked | GRANTED |
| External API | Whatever the integrator reports | GRANTED, DECLINED or UNKNOWN |
| CSV import | A consent column, if the file carries one | GRANTED, DECLINED or UNKNOWN |
Silence is recorded as silenceIf an integrator or an imported file says nothing about consent, the platform records UNKNOWN. It does not record yes. An UNKNOWN row remains analysable, but it is countable and reportable in your methodology rather than indistinguishable from a documented consent.
Refusing to collect
The web-link channel refuses to accept an answer at all when consent has not been given — the request fails rather than proceeding without it.
What this does not do
Stated here rather than discovered later
- The platform performs no automatic language detection on any channel. A declared language is what the caller supplied.
- A channel is not a language capability. WhatsApp, voice and the field app carry whatever the language layer supports and add nothing of their own.
- USSD is designed and not built. It is listed as such rather than offered.