Political Campaign CRM Explained: Managing Supporters in Kenya

A campaign CRM is your campaign’s memory: who you met, what they care about and what you promised to do next. Used well, it turns a pile of phone numbers into votes. Used badly, it can break the law.

What a campaign CRM is, and what it isn’t

A CRM is more than a contact list. It records who a supporter is, where they are (ward and polling station), what they care about (water, school fees, roads, jobs), who in the campaign knows them and what follow-up is due.

It is not the IEBC voter register. Your CRM cannot tell you for certain that someone is registered or where they vote. Encourage supporters to check their own details with IEBC. During past verification periods, voters could check by sending their ID number by SMS to 70000.

A useful supporter record has

Collect data the right way

The Data Protection Act 2019 applies to campaigns. Collect only what you need, tell people why you are collecting it, and get their agreement before you send them SMS or WhatsApp messages. The Office of the Data Protection Commissioner (ODPC) enforces the Act, and campaigns that process personal data to win political support may need to register with it. Check the current rules.

Don’t buy lists of phone numbers or share your supporter list with other campaigns. Bulk SMS to people who never gave you their number annoys voters and can lead to complaints to the ODPC.

Be careful with sensitive details such as ethnicity, religion or health. The Act gives them extra protection. Don’t record them unless you have a clear, lawful reason.

Turn contacts into follow-up

A CRM is only useful if you follow up. If a supporter at a baraza asks about a borehole, the record should create a task saying who will reply and by when.

Send each follow-up to the right person. Local issues go to the ward coordinator, manifesto questions to the policy team and invitations to the events team. Don’t send everything to the candidate.

Close the loop. Record the outcome: done, couldn’t reach them, or not interested. A long list of open follow-ups is not engagement.

Control who sees what

Supporter data is valuable and easy to misuse. A ward coordinator needs their own ward’s supporters, not the whole county. The communications team needs approved contact lists, not field notes.

Limit downloads. Most leaks happen when someone exports a spreadsheet and shares it on WhatsApp. Remove access on the day someone leaves the campaign.

Decide what happens after the election: what you keep, what you delete and when. Don’t keep data forever “just in case”.

Agree these access rules

Keep your data clean

Supporter lists get messy fast: duplicates, wrong numbers and people who have moved. Set aside time every month to clean yours.

Sense-check your numbers. If your CRM shows 20,000 supporters in a ward with 15,000 registered voters, something is wrong.

Use the CRM to guide the ground: which wards have few contacts, and which coordinators are not following up? UshindiOS SRS connects supporter records, field capture, follow-up and messaging, with each team seeing only its own area. Your campaign stays responsible for how it collects and uses personal data.

Your monthly CRM check