When to automate WhatsApp, SMS and reminders — and when not to

Walk into a lot of Kenyan clinics, schools, SACCOs or shops, and you'll find they already run on WhatsApp and SMS. Somebody sends the reminders by hand. A clerk copies the due list into a phone, one number at a time. A missed call becomes a note on a pad by the reception desk. Of course automation looks tempting. It's the same work, every single day.

It's also easy to get wrong. A message goes out that should really have been a conversation. Someone gets a reminder they never agreed to. Personal data ends up spilled into a group chat.

We're a small software studio in Nairobi, and this is the kind of job we do. We set up one repetitive task at a time, replies, reminders or follow-ups, on tools you already use: WhatsApp, SMS, email, web chat, voice, a CRM or Google Sheets, and M-Pesa. Here's how we think about when that's a good idea and when a person needs to stay in the loop. We won't promise you hours saved. The workflow examples on our homepage are labelled illustrative, and they aren't client results.

Which messages are safe to automate?

The ones that come out the same every time. If you know what the message says, when it goes and what happens next, a machine can usually send it.

Think of a clinic's appointment reminder. One goes out the afternoon before, another closer to the slot, and the front desk handles whatever replies come back. Or a fee or repayment reminder that names the amount, the date and a pay link, and stops by itself once the balance is paid. Even a quick "we've got your message" before a person sits down to write a proper answer.

In all of those, the machine is just doing something a person already does the same way each time. The person still owns the exceptions, like a complaint, a sensitive balance, a patient who needs a different time or a member who says the amount is wrong.

Anything that shifts with the relationship, though, stays human. A negotiation, a first sales call, a condolence, a dispute. Nobody wants those from a bot.

What you want is for automation to take the repetitive work off your team while the responsibility stays with them.

Do we need to change our whole system?

No, and we'd advise against it. A useful first audit is small. We take one path, from the moment a reminder ought to go out to the moment someone has to reply, and look at just that. How automations work on our site lays out that sequence. In the first month you don't need to swap out tools your team already knows.

If you send SMS or run a short code, the Communications Authority of Kenya is the public regulator for telecommunications and related consumer issues. Your licence and sender-ID duties are yours, and we're not going to invent some shortcut around them.

To book, go to beaconcreek.co.ke/book.

Sometimes one of our live products already does the job. Rent records live in ConfiRent, collection templates in CadenceApp, and a salon can approve booking reminders in LookFinesse. When that's the case, we'll send you there instead of building a custom flow for the same thing. We'll also be honest about where those products are today. LookFinesse message delivery through the Hub isn't live yet, so approved messages are held, and ConfiRent payments are paused until launch. We won't describe either as already sending or collecting.

So bring one workflow, not a wish list, and book a free 20-minute audit. There's no deposit until we agree.

What about consent and the law?

This is the part people tend to skip. A reminder is very often personal data, whether that's a name, a phone number, a balance, an appointment or a child's class. Kenya's Data Protection Act, 2019 (Cap. 411C) says processing has to be lawful, fair and transparent, for a specified purpose and limited to what's necessary (section 25). Section 37 restricts direct marketing. Section 33 sets the conditions for processing a child's data, which schools need to pay attention to, and section 43 covers breach notification.

The Office of the Data Protection Commissioner is the public authority that registers data handlers and takes complaints. Whether your organisation has to register, and how you take consent or handle an opt-out, is your own compliance work. We're not lawyers, and this isn't legal advice.

When we design a flow, there are a few rules we stick to. We only send to people who have a genuine relationship with the message, a booked visit, a membership, a tenancy or a school place, and never to a bought list. It has to be obvious who's messaging and how to make it stop. When someone opts out, on WhatsApp, SMS or anywhere else, that's respected, even when it makes the diary harder to manage. Other people's balances, marks or medical details never go into a group thread "to save time". And a named person stays responsible for any reply that isn't routine.

When should we hold off?

Sometimes the honest answer is to leave it with a person for now, or wait.

If your contact list is a mess, and you can't tell a current customer from an old number, clean that up first. If your team would send a payment or collections message in a tone you wouldn't put your name to, fix the wording before you automate it. For collections in particular, licensed digital credit providers are bound by the CBK Digital Credit Providers Regulations, 2022, including regulation 20 on threats, shaming and unsolicited contact with a borrower's phone book, and other licences come with their own rules.

Hold off too if the "reminder" is really marketing, and you have no way of getting consent. And never hand a tool a serious decision, like a diagnosis, a loan write-off or an expulsion, without a person making the call.

What you want is for automation to take the repetitive work off your team while the responsibility stays with them.

And after the audit?

If we agree on a workflow, we quote it and agree the success criteria, and only then does a deposit come up. Ready-made automations and care plans are listed on the site. Check the current figure on the pricing pages before you budget, or ask us to quote after the call.

If you'd rather try a product first, every commercial app with a sign-up is free for 30 days without a card. For a quick introduction to who we are, see What Beacon Creek builds in Nairobi.