Importing supporter lists
Prepare a file, record its source and consent, and follow it from upload to completion.
Supporter lists enter Sauti through a controlled intake so that every record has a known source and a lawful basis, as the Data Protection Act, 2019 requires. Raw files never pass through the campaign workspace.
Ways people come into Sauti#
| Route | How it works |
|---|---|
| List import | The Sauti data team loads your file securely after you agree its source and lawful basis |
| Field app sign-up | Volunteers sign supporters up in person, if your organisation has this turned on |
| Join link or QR | Supporters enter their own details on a personal join page shared by a volunteer |
| Donations | Donors are recorded with masked details when they give |
Preparing a list for import#
- Know where it came from. Note the source (for example "Ward 4 sign-up sheets, March 2026") and the collection date.
- Know the lawful basis. Usually consent or legitimate interest. Any other basis needs your legal adviser's written approval reference.
- Keep the evidence. Sign-up sheets, consent forms or screenshots of an online form. The data team may ask for it.
- Use a clean file: UTF-8 CSV or XLSX, one person per row, one heading row. Typical columns are name, phone, email, county, constituency, ward, polling station, gender, year of birth, language and any custom fields.
- Send it securely using the method the Sauti data team gives you, never by ordinary email or chat.
What happens during import#
The data team declares the source and lawful basis, maps your column headings, and reviews the first 50 rows before starting. During the import Sauti:
- normalises Kenyan phone numbers and rejects invalid ones;
- encrypts every phone number and email with your organisation's key;
- merges people who are already in your campaign instead of duplicating them;
- skips anyone on a suppression list (people who opted out or objected);
- places each person in the geography using the codes or names in your file, and flags rows that need a decision.
Rows that need review (for example an unclear ward) are resolved one by one: exclude the row, create a new person after confirming the location, or merge with an existing person.
Following an import#
Open People › Import status. Each batch shows rows read, valid, new or merged, issues, invalid, duplicates and opted-out rows. A batch can be rolled back by the data team for seven days after it finishes; after that, corrections are made record by record.
Note: Uploaded source files are deleted 30 days after import. Keep your own original copy in a secure place if you need it.
Optional number-status check#
Before a big campaign you can check whether consented SMS numbers appear active. In People › Import status, choose an audience or import batch under Number status. The cost is shown from your plan price before you start, and only totals are shown afterwards. Audiences can then exclude inactive numbers.