CRM Follow-Up to WhatsApp and Phone: A Migration Checklist

Migrating follow-up moves the channel, not the record

Moving follow-up to WhatsApp and the phone does not mean leaving the CRM. The CRM stays the record of each applicant, and every exchange on a new channel has to write something back to it. If a WhatsApp thread lives on one adviser's handset and a call lives in their memory, the team has not migrated; it has scattered its follow-up.

The question usually arrives in a busy cycle. Teams notice that emails go unanswered while a short message or a call gets a reaction. Before habits change, check that nothing essential is lost on the way: consent, opt-outs, identity, history and the handover to a person.

This checklist follows the order in which problems appear. It builds on our pieces on WhatsApp opt-in without blocking applicants, lead deduplication across channels and the missed-call callback process, and sits within our guide to recruiting more students.

The nine checks at a glance

1. Inventory what exists before changing anything

List every moment where your office follows up an applicant: acknowledging an application, chasing missing documents, inviting people to open days, post-offer contact, confirming an interview. For each one, note the tool, the channel, the owner and what happens when the person does not reply.

The inventory nearly always turns up informal follow-up: a personal spreadsheet, a broadcast list on a phone, a duty number known to three people. Bring these under the CRM first, because they vanish when an adviser leaves.

Then decide, journey by journey, what goes on WhatsApp, what goes by phone and what stays on email. Identity documents and supporting evidence do not belong on a consumer messaging app.

2. Record consent per channel, not globally

Consent given for email does not cover WhatsApp, and a number left to book a visit is not agreement to marketing follow-ups. Where consent is your basis, the ICO's guidance on electronic and telephone marketing says organisations will often need specific consent to send unsolicited direct marketing by calls, texts or emails under PECR alongside UK GDPR.

In the CRM, store at least the following for each channel:

• Proof of consent: date, source (form, chat, UCAS fair) and the wording shown.
• Purpose: course information, application progress, event invitation.
• Current status: agreed, refused, never asked.

WhatsApp adds its own rules. Meta's WhatsApp Business Messaging Policy, in the version last updated on 23 September 2026, allows a business to contact someone only if that person has given opt-in permission to receive messages or calls. Read it again at launch rather than relying on a rule remembered from last year; it changes. Our article on the WhatsApp Business API and GDPR covers the wider framework.

3. Connect one suppression list

An applicant who tells you to stop on WhatsApp should stop receiving chasers by email for the same purpose, and the reverse. Without a shared list, two tools contradict each other and the refusal is lost.

Meta's same policy requires businesses to respect any request to block, discontinue or opt out of communications. Check three things:

1. The stop keyword or button updates the CRM promptly.
2. Campaigns, sequences and manual chasers read that status before sending.
3. The refusal survives a merge or an accidental deletion: keep the fact of the refusal, not the content.

For calls, the Telephone Preference Service is the register for marketing calls to individuals. Ask your data protection officer where a callback the applicant asked for ends and cold outreach begins.

4. Fix the identity rule before the first message

A phone number is not an identity. It can belong to a parent, be shared in a household or have changed hands. Before writing to a record, decide how the CRM ties an incoming conversation to an applicant.

A simple rule has three lines: store numbers in international format (the ITU's E.164 recommendation describes the structure), confirm with a second data point before merging, and flag a record "to verify" instead of merging automatically when in doubt. Where an applicant is under 18, note who the contact is: the applicant, a parent or both.

5. Demand a complete, dated, readable trail

Every WhatsApp message sent or received, every call made or missed and every note should appear on the record, with date, channel, author and content or summary. If advisers must copy and paste by hand, the trail will be incomplete within a week of Clearing.

Verify that:

• Inbound messages reach the CRM with no manual step.
• Calls are logged, including attempts with no answer.
• Call recording exists only if your institution decided on it, callers are told and a retention period is set.
• The log shows whether a message came from a person or from automation.

That last line matters: transparency duties apply when someone is talking to an AI system, so take advice on the text that applies to you.

6. Write the human handover rule

Automation or a message template must never hold on to an applicant who asks for a person. The rule lists the triggers: a funding question, a complaint, a personal circumstance, an explicit request for a call.

For each trigger, name the recipient, the expected delay and the channel of the first reply. An applicant who writes on WhatsApp and gets an unexpected call is not always pleased; offer the callback instead of imposing it. Our after-hours enquiry process gives an escalation model.

7. Name an owner and a target time per queue

Three queues appear: inbound WhatsApp messages, calls to return and outbound chasers. Each needs a named owner, a target time set by your institution (no universal public benchmark dictates it) and a deputy for absences.

Add a supervision view in the CRM: unanswered conversations, overdue callbacks, applicants with no valid consent for the channel in use. That view, more than the messaging tool, makes the migration manageable.

8. Test on dummy records first

Create a few fictional records: one with WhatsApp consent, one without, one opted out, two duplicates, one under-18 with a parent. Then run the scenarios: inbound message, stop request, missed call, request for a person, record merge.

Log every gap and go live only when the critical cases (opt-out, missing consent, duplicate) behave as intended. A pass on the happy path proves nothing.

9. Plan the way back

Keep the previous follow-up in read-only mode during the transition and write down how to return to it: who decides, how live conversations are picked up, how affected applicants are told. A migration that cannot be undone is one nobody dares to correct.

Fix in advance the date the old process closes and what gets archived. The CRM must be able to answer a subject access or erasure request across every channel.

What should never go on WhatsApp

A rule of thumb helps advisers: messaging is for pointing and booking, not for exchanging sensitive documents. Detailed grades, passports, financial or health information go through a secure portal, with a link or an appointment. Put it in writing in the adviser handbook.

That holds whether the applicant came through UCAS, direct application, Clearing or a foundation-year route.

Where Skolbot fits, and what stays with you

Skolbot Chat is an agent on the school website. It answers from the institution's published content, qualifies the enquiry, offers appointments or open-day slots, then passes the conversation to the team and the CRM. WhatsApp and voice channels are scoped project by project: their scope, timing and price are to be confirmed before any commitment.

Consent, suppression, human handover and retention rules remain decisions for your institution, validated by your data protection officer. A well-configured tool applies those rules; it does not replace them.