Slate + WhatsApp: A Slate WhatsApp Integration for Admissions

A Slate WhatsApp integration connects prospective students' WhatsApp conversations to Slate, the admissions CRM by Technolutions. Slate does not document a native WhatsApp feature. Skolbot fills that gap with two AI agents: WhatsApp Capture turns inbound conversations into Slate records, and WhatsApp Activate follows up with a population or query exported from Slate.

The integration runs on Slate's public mechanisms: source formats, Upload Dataset, SFTP and web services. Objects, fields, triggers and sync direction are confirmed for each institution's Slate configuration during scoping.

Slate + WhatsApp: what Slate already does

Slate already sends text messages natively. Technolutions documentation states that real-time, bidirectional SMS text messaging is a native component of Slate, with no third-party integration required. Replies appear on the record linked to the phone number and in Inbox.

WhatsApp is a different story. We found no native WhatsApp feature in Technolutions' public documentation. If your team wants to answer applicants on WhatsApp and see those exchanges in Slate, you need a layer that runs WhatsApp and feeds Slate.

Slate texting vs a WhatsApp AI agent: two different tools

The two can coexist. SMS works well for reminders and one-to-one counselor exchanges. The WhatsApp agent serves applicants who prefer WhatsApp and ask many questions before they apply, international applicants in particular.

What Skolbot is not

Skolbot is not a connector certified by Technolutions. We claim no partnership with Technolutions and no listing in any Slate marketplace. The integration uses the import and export tools Slate documents for every institution. Your Slate team keeps control of mapping, matching and the activation of each feed.

WhatsApp Capture: from inbound conversations to Slate records

WhatsApp Capture answers applicants who message you on WhatsApp, for example from a QR code at a college fair or a button on a program page. The agent answers questions, qualifies the inquiry and records consent. The lead is then sent to Slate.

The source format: the way into Slate

Slate organizes imports around Upload Dataset, the import tool in Slate. A source format describes a dataset that always comes from the same source and maps each column to a Slate field. The Source Format Library offers formats for known vendors; for Skolbot, a custom source format is created and reviewed by your team.

Typical data includes name, WhatsApp number, email if given, program of interest, intended entry term, lead source, consent and a conversation summary.

SFTP or web service

Slate documents two ways in:

• files dropped on the Technolutions SFTP server, usually in an /incoming/ directory, as described in the Slate SFTP overview;
• a web service push to the endpoint unique to the source format, as described in Importing Data with Web Services.

The same page notes that Upload Dataset works best with batches rather than row-by-row updates. Skolbot therefore sends leads in batches. A callback request travels with the lead in the batch, with its call brief, so your team finds it on the Slate record.

WhatsApp Activate: following up with a Slate population

WhatsApp Activate starts in Slate. In Slate, a population is a group of records with like attributes, defined by rules. Your team builds a query on that population, for example applicants to one program with an incomplete file.

Slate lets you schedule the export of a query's results to an SFTP server or make them available through a web service. Skolbot reads that export, messages only the people who opted in to WhatsApp, then sends the outcome back to Slate through the source format.

Skolbot only reads what your query exposes. Your team chooses the contacts, the criteria and the fields.

WhatsApp opt-in

Consent is a requirement, not a detail. Meta documentation states that businesses are required to obtain opt-in before messaging people on WhatsApp, and your own policies may go further. A phone number in Slate does not, on its own, mean the person agreed to WhatsApp messages.

In practice, scoping adds a Slate field that holds WhatsApp consent and its date. WhatsApp Activate filters on that field. WhatsApp Capture fills it when an applicant agrees to be contacted. Our guide to WhatsApp applicant outreach and opt-in covers frequency rules.

Human handoff to counselors

The AI agent makes no admissions decision. It hands off when the question involves a personal case, an exception, financial aid or a complaint, or when the applicant asks for a person.

Scoping settles three points: who receives the conversation, in which tool, and what is written to Slate. Usually the Slate record gets a status, the handoff reason and the assigned counselor. The counselor picks up with the full context.

How a Slate WhatsApp integration is scoped

Scoping follows a simple order:

1. The pilot. One moment in the journey, for example WhatsApp inquiries from college fairs.
2. Objects and fields. Your Slate team says where the lead lands: person record, custom fields, an interaction or another structure specific to your instance.
3. Matching. The phone number is often the key, with email as backup. Slate applies its own matching rules at import.
4. Sync direction. Capture flows from Skolbot to Slate. Activate starts from a Slate export, then the outcome comes back.
5. Timing. A batch frequency that works for the admissions team.
6. Data. Summary or full transcript in Slate, with input from your privacy office. For US institutions, check how this fits FERPA and your policies once the applicant enrolls. For European institutions using Slate, scoping also covers GDPR: lawful basis, notice, retention and transfers.
7. Errors. Who gets alerted when an import is rejected. Skolbot logs every batch it sends.

To compare with other setups, read our WhatsApp CRM integration guide for admissions, AI admissions agent vs CRM automation and the higher education CRM comparison. The integrations page lists supported CRMs.