Keep the applicant record in your CRM or student system, keep the conversation in your messaging platform, and move a small number of events between the two. That's the whole job. You don't need every field synced in both directions, and you don't need an integration on day one: several institutions start with a contact list and connect their CRM once WhatsApp is working.
This guide is for the CIO, IT lead or CRM owner who's been asked "can WhatsApp talk to our system?" It covers what should live where, which events are worth connecting, three ways to connect, a worked Salesforce example, and the questions your DPO in the UK or Information Officer in South Africa will ask.
What lives where
An admissions team runs on two kinds of information, and they belong in different places.

Lives in your CRM or student system | Lives in your messaging platform |
|---|---|
The applicant record: name, course, status, documents, decision | The conversation: every WhatsApp, web chat, email and Messenger message |
Pipeline stages and reporting on applications | Templates, broadcasts and journeys |
Offer and enrolment decisions | Routing to the right adviser or team |
The system of record for audit | The inbox your admissions staff work in |
The integration's job is to keep the two in step at the moments that matter, not to copy one into the other.
In Cue, each contact has one record with their full conversation history across WhatsApp, web chat, email and Messenger. Phone calls sit on the same record too, with recordings and transcripts. Your CRM keeps the pipeline; Cue keeps the conversation.
The events worth connecting
Start with the handful of events that save someone a manual step. We'd start with three.
Event | Direction | What happens | Why it matters |
|---|---|---|---|
New enquiry arrives on WhatsApp | Messaging → CRM | Look up the contact in the CRM; create a lead if there isn't one | No retyping, and no duplicate records |
Applicant answers entry questions in the chat | Messaging → CRM | Course, qualifications and start date written to the record | Advisers see qualification before they call |
Conversation finishes | Messaging → CRM | Conversation history, or a summary, saved against the record | One place to see what was said |
All three run from the conversation into the CRM, which Cue's Flows do today.
Messages that start from a change in your CRM, such as an offer being made, can go out as a scheduled broadcast to a list exported from the CRM while you scope anything more direct. Record opt-outs in both systems as part of the same routine.
Three ways to connect
There's no single right answer. The route depends on what your CRM or student system allows and who's going to build it.

Route | How it works | Effort | Who builds it | When it fits |
|---|---|---|---|---|
1. No integration (CSV) | Export a list from your CRM, upload it to the messaging platform, and send | Lowest | Admissions or marketing | Phase one, or while IT is busy |
2. Middleware | A tool such as Zapier or n8n passes data between the two | Low to medium | A technically confident admin | Common CRMs, simple events |
3. Direct API | The messaging platform calls your CRM's API, and your CRM calls back | Medium | IT or a partner | Custom CRMs, student systems, anything with an API |
Cue integrations are built through Flows, Cue's journey builder. A Flow can send HTTP requests to another system's API, so it can create, find and update records as part of a conversation. Zapier and n8n cover systems where a direct connection isn't practical. Cue lists the systems customers connect most often, including HubSpot and Salesforce, on its integrations page, but the list isn't a limit: if your system has an API, it can be connected.
For a HubSpot CRM, Cue's HubSpot integration guide shows how Flows create, find and update contacts and tickets and save conversations to a contact.
Student record systems vary more. In UK universities, Tribal SITS is the system reported most often: in UCISA's 2023 survey, 45 of 75 responding institutions used it, followed by Ellucian Banner with 12 and in-house systems with seven (UCISA, Trends in Corporate Information Systems 2013 to 2023). There's no equivalent published picture for UK FE colleges or South African private providers.

What matters is whether your system exposes an API you can use. Ellucian publishes an API reference for Banner. Tribal publishes samples for its Admissions Integration API. For anything else, including in-house systems, ask the vendor or your own developers for the API documentation and what access your licence includes (see the questions below).
Example: connecting to Salesforce
Salesforce is the CRM that comes up most in our conversations with UK universities, and Cue documents the setup in its Salesforce integration guide.

Create a Connected App in Salesforce to represent Cue, with OAuth enabled. You'll need System Administrator access, and a Salesforce org on Enterprise, Unlimited, Performance or Developer Edition.
Build a Flow in Cue that requests an access token from Salesforce.
Add HTTP request steps to the Flow that create a Lead, a Case or a Task in Salesforce from the conversation.
A typical admissions setup creates a Lead when an enquiry finishes qualification, with the applicant's answers attached, and a Task for the adviser who needs to follow up.
This is a configured integration built with Flows, not a managed package from AppExchange. If you're weighing Salesforce's own WhatsApp products against a dedicated platform, our comparison of WhatsApp in Salesforce for admissions covers licences, costs and when each route fits.
What your DPO or Information Officer will check
Data protection sign-off is easier when you've answered these before you're asked. In the UK, the questions come from UK GDPR. In South Africa, from POPIA, with sign-off from your Information Officer.
Lawful basis for each message type. Service messages about an application are different from marketing.
Minimum data. Pass only the fields each event needs. A message trigger rarely needs more than a name, a phone number and a status.
Access by role. Who in admissions can see which conversations, and who can export them.
Sign-in. Cue supports single sign-on with Google and Microsoft Entra ID.
Credentials. API keys and tokens are stored in the integration, not in someone's inbox, and scoped to the permissions the integration needs.
Where data is processed. Ask every vendor in the chain, including your CRM, your messaging platform and any middleware.
One record for every touchpoint
Admissions teams regularly ask us some version of "can we see every touchpoint in one place?" The answer is yes, in two layers.

The messaging platform holds every conversation against one contact: WhatsApp, web chat, email, Messenger and phone calls. The CRM holds the application and its status. Connect the two at the three events above, and an adviser can open either system and see what they need.
Questions to ask your CRM or student system vendor
Ask these before anyone writes a line of configuration:
Do you publish an API, and is access included in our licence or extra?
Is there a sandbox we can test against?
Can your system send a webhook when an application status changes?
How do we match an incoming message to an existing record? Phone number, email, applicant ID?
Are there rate limits we need to plan around in peak season?
Where is the data processed and stored?
Then ask your messaging platform the mirror questions: how it calls an API, how it receives a webhook, and who maintains the connection when either side changes.
To see how Cue connects to the systems institutions already run, read about Cue for education or book a demo and bring your IT lead.







