--- title: "WhatsApp CRM Integration for Admissions: A School Guide" description: "Connect WhatsApp to your admissions CRM: data flows in each direction, consent, advisor handoff, deduplication and scoping for HubSpot, Salesforce, Slate." url: "https://www.skolbot.ai/en/blog/whatsapp-crm-integration-admissions" language: "en" dateModified: "2026-11-12" --- # WhatsApp CRM Integration for Admissions: A School Guide Updated on November 12, 2026 Connect WhatsApp to your admissions CRM: data flows in each direction, consent, advisor handoff, deduplication and scoping for HubSpot, Salesforce, Slate. A WhatsApp conversation only helps your admissions team if it reaches the CRM. Without that link, the advisor cannot see the applicant's question, the course they want or the permission they gave to be contacted. They call back blind, or not at all. This guide shows how to connect WhatsApp to an admissions CRM, whatever the tool: HubSpot, Salesforce, OSCAR Campus, Slate, Zoho, Odoo, or another CRM through an API or webhook. It covers what flows in each direction, where to store consent, how to hand over to an advisor and how to avoid duplicate records. It ends with how Skolbot scopes the integration with your team. ## The principle: the CRM stays the source of truth Start with one rule: your CRM remains the source of truth for each record. WhatsApp is a conversation channel. The integration moves events between the two, in directions you define in advance. This split protects your team's work. Status, campaign source and contact preferences live in the CRM. The conversation lives in WhatsApp, with a summary and the useful fields copied to the record. Advisors keep working in the tool they already know. On the technical side, Meta's WhatsApp Business Platform delivers incoming messages and delivery statuses through [webhooks](https://developers.facebook.com/docs/whatsapp/cloud-api/webhooks). A webhook is an automatic notification sent to a web address when an event happens. The integration layer receives these notifications, matches them to a record and writes to the CRM through its API or connector. To compare data models across the main CRMs in the sector, see our [higher education CRM comparison](https://www.skolbot.ai/en/blog/crm-higher-education-comparison). ## Two flows, two directions A complete WhatsApp integration has two flows. The first runs from the applicant to the CRM. The second runs from the CRM to the applicant. Skolbot covers both with two separate agents. | Flow | Trigger | Skolbot agent | What reaches the CRM | |---|---|---|---| | Inbound | The applicant writes in: Instagram or Facebook click-to-WhatsApp ads, the WhatsApp icon on the website, QR codes | WhatsApp Capture | A new or updated record, depending on the integration | | Outbound | A CRM cohort defined by a status: fair contacts, incomplete applications, dormant leads, admitted international students | WhatsApp Activate | Replies and next steps, in the same record | ### Inbound: from conversation to record In the inbound flow, WhatsApp Capture answers applicants who write in. It answers from the school's knowledge base and qualifies the request. Depending on the integration, it creates a record or updates the existing one. Not every message becomes a lead. Spam is filtered out. A company looking to recruit or a student already enrolled is sent to the right department, without creating a lead in your CRM. Your database stays clean. The fields sent to the CRM are agreed with your team. A lead can carry the country, language, course, target intake, consent, a score and a call sheet for the advisor. The exact list depends on your data model. ### Outbound: from CRM to conversation In the outbound flow, everything starts in the CRM. WhatsApp Activate takes a cohort defined by a status and leads it to one action: open day, webinar, application, phone appointment with an advisor or enrollment step. Replies and next steps come back to the same record. The advisor knows where each contact stands before calling. This flow covers new leads and existing CRM contacts alike, on one condition: consent. ## Consent: a CRM field, not a forgotten checkbox Consent must be a CRM field that the sending rule can read at the moment of sending. Without it, the system cannot know whether a message is allowed. The [WhatsApp Business Messaging Policy](https://whatsappbusiness.com/policy/) requires that the person gave you their number and agreed to be contacted by you on WhatsApp. It also requires you to respect requests to stop. Meta's guidance on [getting opt-in](https://developers.facebook.com/docs/whatsapp/overview/getting-opt-in) states that businesses must obtain opt-in before sending messages. National rules apply too. Your country's data protection authority publishes the rules on marketing messages to individuals. Ask your data protection officer to review your scenarios. At Skolbot the rule is clear: the WhatsApp Business account belongs to the school, which runs it under its own contract with Meta. Before any WhatsApp Activate outreach, the school must hold the person's consent. In practice, store for each contact: - the allowed channel (WhatsApp, email, phone); - the date and source of consent (form, fair, conversation); - the scope of consent (application follow-up, course information); - any withdrawal, visible to every channel. A "STOP" received on WhatsApp must update this field in the CRM. Otherwise another campaign may contact the same person tomorrow. Our [guide to the WhatsApp Business API and GDPR](https://www.skolbot.ai/en/blog/whatsapp-business-api-school-gdpr) covers the responsibilities linked to the channel. ## Human handoff: the advisor gets a brief, not a raw thread An agent answers common questions. An advisor makes decisions and handles individual cases. The integration must make this handover smooth. With Skolbot, the advisor receives a brief in the CRM that summarises the request, instead of a raw conversation to reread. Handover rules are set with your team during scoping. Common handover reasons to discuss: 1. a question about an individual application; 2. a complex financial question; 3. a request about personal data; 4. an uncertain answer from the agent; 5. an explicit request to speak to a person. For each reason, decide who receives the task in the CRM and which status shows it. Admissions decisions stay with your team. Also plan the callback process on the admissions side: without it, a qualified lead does not become a new student. ## Deduplication: a stable key before the first message The same person may write on WhatsApp, fill in a form and leave details at a fair. Without a rule, that creates three records. The advisor sees three requests and the applicant receives three follow-ups. The phone number is the natural key of a WhatsApp conversation. Store it in a normalised format in the CRM, with the country code. A number typed as "07700…" on a form does not match "+44 7700…" from WhatsApp unless both are normalised. Set the matching order too: phone number, then email, then a manual rule. Decide which source wins when a field conflicts, such as the target course. Our guide to [student lead deduplication across channels](https://www.skolbot.ai/en/blog/student-lead-deduplication-across-channels) covers these rules in detail. ## What changes with your CRM The principle is the same everywhere. What changes is the connection method, the objects and the available fields. Skolbot connects to HubSpot, Salesforce, OSCAR Campus, Slate, Zoho and Odoo. Other CRMs connect through an API or webhook. | CRM | Questions to check during scoping | |---|---| | HubSpot | Which property holds consent? Which lifecycle stage triggers a callback? | | Salesforce | Which objects hold the contact and the application? Which API permissions are open? | | OSCAR Campus | Which prospect fields can the API read and write? | | Slate | Which fields and populations define a cohort? | | Zoho, Odoo | Which modules and custom fields hold prospects? | | Other CRM | Does it accept an API or an inbound webhook? | These questions are not promises. The connection method, objects, fields and sync direction are checked for your setup before any deployment commitment. For Slate specifically, our [Slate WhatsApp integration guide](https://www.skolbot.ai/en/blog/slate-whatsapp-integration) covers source formats, batch imports and population follow-up. ## Scoping: about two weeks, with sign-off on your side A good integration starts with short, concrete scoping. At Skolbot, setup takes about two weeks. - **Week 1, at Skolbot:** documentation, knowledge base, WhatsApp number, CRM mapping. - **Week 2, with your teams:** testing, feedback, sign-off. Go-live comes at the end of week 2. Timing depends on integrations and your approvals. On your side, prepare the school's documentation, the access needed for the CRM and the callback process. For the knowledge base, Skolbot collects and checks, and your team approves. Before the scoping meeting, prepare a simple sheet with: 1. the CRM fields your advisors actually use; 2. the consent field or property; 3. the statuses that define your follow-up cohorts; 4. handover reasons and the owner of each queue; 5. your current deduplication rule, even an informal one. If you are moving follow-up from phones or personal messaging into the CRM, our [CRM follow-up migration checklist](https://www.skolbot.ai/en/blog/crm-follow-up-whatsapp-phone-migration-checklist) helps you lose nothing on the way. ## The most common integration mistakes Most failures come from process, not technology. Here are the most frequent ones. **Creating a lead for every message.** An applicant who asks three questions must not create three records. Matching by phone number must happen before any record is created. **Storing consent outside the CRM.** If consent lives in a spreadsheet or in the WhatsApp thread, the sending rule cannot read it. It must be a field. **Copying the whole conversation into the record.** A summary and the useful fields are often enough. Decide with your data protection officer what to keep, who can access it and for how long. **Forgetting the return path.** If a reply to a follow-up does not update the record, the advisor calls without context. Test both directions. **Launching without a callback process.** A brief that lands in a queue with no owner produces no new student. For WhatsApp-specific rules on message templates and human handoff, see our guide to [WhatsApp for admissions: opt-in, templates and handoff](https://www.skolbot.ai/en/blog/whatsapp-admissions-2026-opt-in-templates-pricing-handoff). ## Frequently asked questions ### Do we need to change CRM to connect WhatsApp? No. Your CRM remains the source of truth. Skolbot connects to HubSpot, Salesforce, OSCAR Campus, Slate, Zoho and Odoo, and to other CRMs through an API or webhook. ### Does every WhatsApp conversation create a record? No. WhatsApp Capture can create or update a record depending on the integration. Spam is filtered out, and non-admissions requests are sent to the right department without creating a lead. ### Can we contact existing CRM contacts on WhatsApp? Yes, if the school holds their consent. WhatsApp Activate starts from a CRM cohort defined by a status. Consent must be recorded before any outreach. ### Who owns the WhatsApp Business account? The school. It runs its WhatsApp Business account under its own contract with Meta. ### Are WhatsApp conversations charged by Meta included? No. WhatsApp conversations charged by Meta are not included in the Skolbot subscription.