Before your first campaign
Three things determine what you can do later, and all three are easier to set now than to change afterwards:
- Your organization's working language. This is the language your team sees the workspace in. It is separate from the language you collect in and separate again from the language you publish in.
- Your country profile. This resolves administrative terminology — whether your second administrative level is called a district, a county or a commune — and it must be a country the registry recognises.
- Who holds which role. Roles are not decoration: an enumerator cannot create a study and an analyst cannot change retention policy, and those refusals are enforced in the database predicate rather than hidden in the interface.
The shape of a project
Work is organised as programme → project → campaign → responses. A programme can span several countries without duplicating your organization. A campaign is what a respondent actually answers.
A study sits alongside this and is the research object: it carries the design, the sampling plan, the methodology and the analyses. You attach a campaign to a study to make its responses analysable.
Choosing a collection channel
Voice, WhatsApp, SMS, web link and app all enter through one pipeline, so a campaign published once is reachable on all of them. What differs is how consent is captured — see Data collection.
What to expect on day one
An empty workspace is an empty workspace. There is no seeded demonstration data in a real organization, and nothing is generated on your behalf. If you want to see the platform working before you collect anything, use Explore VoiceInsights in Action.