Moving CRM Follow-Up to WhatsApp and Phone: Checklist

The CRM stays the record; WhatsApp and the phone are channels

Moving follow-up to WhatsApp and calls does not mean leaving the CRM. The CRM is still the record for each applicant, and every exchange on a new channel has to write back to it. If a WhatsApp thread sits on one officer's phone and a call sits in their memory, the office has not migrated; it has scattered its follow-up.

The question often arises around CAO offer rounds and the Leaving Cert results period, when admissions staff see email go unanswered while a short message or a call gets a reaction. Before habits change, check that nothing essential is lost: 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, deduplicating leads across channels and the missed-call callback process, and sits within our guide to recruiting more students.

Nine checks at a glance

1. Inventory current follow-up first

List each moment where your office follows up: application received, missing documents, open day invitation, offer-stage contact, registration reminder. For each, note the tool, the channel, the owner and what happens when the applicant does not answer.

Informal follow-up always turns up: a personal spreadsheet, a broadcast list on a phone, a duty number known to three people. Bring those into the CRM first, because they vanish when an officer leaves.

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

2. Record consent per channel, not globally

Consent for email is not consent for WhatsApp, and a number given to book a visit is not agreement to marketing messages. Under the GDPR, which applies directly in Ireland and is supplemented by the Data Protection Act 2018, the European Data Protection Board states that where consent is the legal basis, it must be freely given, informed, specific and unambiguous. Electronic and telephone marketing also falls under the ePrivacy Regulations; the Data Protection Commission publishes guidance on both, and your data protection officer should confirm how it applies to admissions outreach.

In the CRM, store at least the following per channel:

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

WhatsApp adds its own layer. 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 trusting a rule remembered from last year.

3. Wire up one suppression list

An applicant who says stop on WhatsApp should stop getting email chasers for the same purpose, and the reverse. With separate lists, two tools contradict each other and the refusal is ignored.

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 follow-ups read that status before sending.
3. The refusal survives a merge or accidental deletion: keep the fact of the refusal, not the content.

For calls, ask your data protection officer where a callback the applicant requested ends and unsolicited outreach begins.

4. Settle the identity rule before the first message

A phone number is not an identity. It may 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" rather than auto-merge when in doubt. For an applicant under 18, note who the contact is: the applicant, a parent or both.

5. Require a complete, dated, readable trail

Every WhatsApp message in or out, every call placed or missed and every note should appear on the record with date, channel, author and content or summary. If staff must copy and paste by hand, the trail will be incomplete within a week of an offer round.

Verify that:

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

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

6. Write the human handover rule

Automation or a template must never hold on to an applicant who asks for a person. The rule lists triggers: a question on fees or the SUSI grant, 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 offers an escalation model.

7. Name an owner and a target time per queue

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

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

8. Test on dummy records before real applicants

Create a few fictional records: one with WhatsApp consent, one without, one opted out, two duplicates, one minor with a parent. 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 old follow-up read-only 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 you cannot undo is one nobody dares to fix.

Set in advance the date the old process closes and what gets archived. The CRM should be able to answer an access or erasure request across every channel.

What should not travel on WhatsApp

A rule of thumb helps staff: messaging is for pointing and scheduling, not for exchanging sensitive documents. Leaving Certificate results, passports and financial or health information go through a secure portal, with a link or an appointment. Put it in the staff handbook.

That applies to universities, technological universities and private colleges alike, whether applicants come through the CAO, a direct application or a QQI-validated programme.

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 visit or event slots, then hands 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 your institution's decisions, validated by your data protection officer. A well-configured tool applies those rules; it does not replace them.