Email open rates hover around 20%. WhatsApp messages get opened, on average, within minutes, by more than 90% of recipients. For higher ed teams trying to reach students who treat their inbox like a graveyard, that gap is the whole story.
But WhatsApp isn’t email with a green tint, and it isn’t SMS either. Meta runs the platform on a tight set of rules, and the teams who get the most out of it are the ones who treat it as its own channel from the start. Here’s what to know before you send your first message.
Why WhatsApp, and why now
For most students under 25, WhatsApp is where actual conversations happen. They check it constantly, reply quickly, and treat it as the place to talk to people who matter. A message from your admissions team lands in the same thread as messages from their mum and their best mate, which is either a brilliant opportunity or a fast route to a block. There’s not much in between.
The use cases that tend to work well in higher ed:
- Nudging offer holders during the wobble between offer and enrolment
- Reaching applicants during clearing, when speed is everything
- Reminding students about open days, interviews, and document deadlines
- Following up after events with the people who actually showed up
None of these are new problems. WhatsApp just gives you a faster, more direct way to solve them.
1. Get consent right (the bit most teams underestimate)
Meta is strict about consent, and rightly so. You can’t message a student on WhatsApp just because they’re on your email list or because they once gave you their mobile number for SMS. They need to have explicitly agreed to hear from you on WhatsApp specifically.
What counts as valid consent:
- A dedicated WhatsApp checkbox on your forms, separate from email and SMS
- Clear language about what you’ll send, like “Receive application updates and event reminders via WhatsApp”
- A sense of what to expect, in terms of message type and rough frequency
What doesn’t count:
- Quietly opting in your existing SMS list
- Assuming consent because someone applied or registered
- A generic “marketing communications” tick box
If you send to people who didn’t actively opt in, the blocks will come quickly. And blocks hurt your account in ways that are hard to undo.
The practical step: add a WhatsApp consent option to your enquiry forms, event registrations, and applicant portals now, even if you’re not ready to send yet. In Gecko, this lives as a dedicated consent type, so you can start collecting permissions and build your list properly from day one.
2. Understand templates before you plan your first send
WhatsApp doesn’t let you fire off a free-form message whenever you like. When you start a conversation with a student, you have to use a pre-approved template. Meta reviews and approves each one before it goes live, which usually takes a day or two.
One thing that catches a lot of teams out: with some platforms, you build your templates inside Meta’s WhatsApp Business Manager, then plug them in elsewhere to send. That’s two tools, two sets of logins, and two places to keep in sync. In Gecko, templates live inside the platform and get submitted to Meta via API behind the scenes. You build them where you build the rest of your campaigns.
The practical step: draft your three or four most important templates now (offer holder reminder, interview confirmation, open day follow-up, application deadline nudge) so they’re ready to go when you need them.
3. Start small, segment hard
When your WhatsApp account is new, Meta caps how many people you can message in any 24-hour period. You’ll usually start with 250 and scale up as you prove you’re a good sender. The temptation will be to push that limit straight away. Resist it.
Start with the contacts most likely to welcome a message: recent offer holders, students who came to an open day in the last fortnight, applicants actively engaging with your comms. Good engagement on your first sends earns you the room to do more later.
This is also where segmentation earns its keep. The fastest way to wear out your welcome on WhatsApp is to send everyone the same thing. The channel rewards relevance more than any other, partly because students notice when a message clearly isn’t for them.
A useful test before you hit send: can you explain in one sentence why this specific group needs this specific message? If you can’t, the segment needs more work.
If you’re already running this kind of segmentation for email in Gecko, the same labels and audiences carry across. You’re not starting from scratch.
4. Treat frequency as a feature
Because students see WhatsApp messages almost immediately, over-sending is felt more sharply than over-sending email. A sensible rule of thumb for higher ed:
- Transactional: as often as needed. Interview reminders, deadline confirmations, results notifications, these are useful and welcome.
- Promotional: one or two a month is plenty for most audiences. Clearing week is an obvious exception.
- Timing: stick to reasonable hours in the student’s timezone. A WhatsApp at 7am on a Saturday is a fast route to a block.
Build a frequency cap into your plans early, so you don’t have to retrofit one when things start going wrong.
5. Make every message worth opening
WhatsApp is a privilege, not a quota to fill. Before any send, run the message past a simple question: would I want to receive this?
Here’s what that looks like in practice.
Don’t:
Hi James, just a quick reminder about our upcoming events at the University of [X]. We’ve got loads going on this autumn including open days, taster sessions, and webinars. Visit our website for more info and to register your interest. We hope to see you soon.
Do:
Hi James, your offer holder day is Saturday 15 November, 10am. Here’s everything you need: [link]. Need to swap to a different date? Reply DATE.
Same channel, very different message. The second one tells the student what’s happening, when, what to do, and how to change it. The first one tells them nothing they couldn’t get from your homepage.
Good WhatsApp messages tend to be specific, useful, and short. If a message doesn’t pass the test, it isn’t worth sending.
What good looks like
If you’re following the basics, you should see:
- Quality rating consistently high (Meta colour-codes this green)
- Block rate under 0.5%
- Delivery rate above 95%
- Reply rates that genuinely surprise you
That last one matters. Teams new to WhatsApp are often caught off guard by how much students actually reply. Make sure you’ve got someone ready to handle the conversations that come back, because they will.
Where to start this week
You don’t need a launch date to start preparing. Three things you can do now, regardless of when you plan to send your first message:
- Add a WhatsApp consent option to your three most-used forms. Even if you collect ten opt-ins a week, in three months you’ve got a meaningful list.
- Draft your most important templates. Start with the four moments where speed matters most: offer follow-up, interview confirmation, event reminder, application deadline.
- Decide who owns the replies. The team that handles inbound WhatsApp shouldn’t be a question you answer the day after launch. If you have Gecko Chat, you can connect up your bots to handle replies automatically.
If you’re using Gecko, WhatsApp Broadcasting will sit alongside the channels you’re already running, with consent capture, segmentation, and templated messaging built into the same place you work today. Worth getting your house in order now, so you’re ready when you’re ready.
