Skip to main content

Slate CRM

Guidebook integrates with Slate, Technolutions’ CRM for higher ed admissions and enrollment. If your institution manages recruitment, events, or orientation in Slate, the integration connects that work to your Guidebook guides in both directions. Student records, events, and registrants come into Guidebook, and app engagement and attendance go back to Slate. Your team stops building the same event twice, and each student’s Slate record shows how they actually engaged.

What you can connect

Person Data (Slate to Guidebook)
Syncs Slate student records to each student’s Guidebook account, so students see their Slate information, like major, college, or orientation group, in their guide profile. You choose up to 12 Slate fields to show, and that choice applies to every guide in your organization. Students are matched by their Net ID through SSO, or by a verified email address. When a student has a Slate record, their first and last name come from Slate and can’t be edited in the app.

Event & Session Data (Slate to Guidebook)
Link a Slate event folder to a guide, and every event in that folder becomes a session in the guide’s schedule. Session names, times, descriptions, tracks, and locations stay in sync with Slate. When students register for those events in Slate, they’re added to the guide’s Users list in Audience Management automatically. If they un-register, they’re removed (or lose access on an invite-only guide). Registration sync needs Person Data connected on the same Slate instance.

Guidebook App Usage Data (Guidebook to Slate)
Sends app engagement back to Slate every hour: guide downloads, time in app, schedule adds, session, menu item, and list item views, and form responses. Each record is tied to the right Slate event and student record.

Attendance Data (Guidebook to Slate)
When a student is checked in on Guidebook, their Slate registration is marked Attended with the check-in time. Checking in to a session also marks them attended for the overall event. You choose which guides send attendance data to Slate.

Guidebook QR Code URL (Guidebook to Slate)
Sends each linked guide’s permanent QR URL to Slate, so you can use it in Slate emails or turn it into a QR code there. It’s the same URL as the QR code on your guide’s Promote page. It never changes, even if you rename the guide, change its privacy, or move it to a different Space, and scans work the same way, including for passphrase and invite-only guides. It needs Event & Session Data, and a guide’s URL is sent once the guide is published and attached to a Space.

App Usage Data and Attendance Data both need Person Data and Event & Session Data connected on the same Slate instance. They only include students who are logged in, have a Slate record, and said yes to sharing their usage information for that guide.

Set up the integration in Builder

Only organization admins can set up the Slate integration. Before you start, a Slate admin at your institution needs to import the Guidebook Suitcases and create a web service in Slate for each connection. Our Slate setup guide walks through those steps.

  1. In Builder, select Organization Account in the side navigation, then open the Integrations tab.

  2. Under Organization Integrations, find the Slate row and click Set up (or Edit if you’ve already started). This opens the Slate Integration page.

  3. Choose a data type and follow the four steps: Select Type, Set Up, Configure, and Review and Save. Each step saves as you go, so you can leave and pick up where you left off.

Your connections appear on the Slate Integration page with their status: Connected, Paused, Error, or Setup incomplete. You can pause, resume, edit, or remove any connection. Removing a connection stops the sync, but doesn’t delete anything in Slate or anything already synced into Guidebook.

If your school uses more than one Slate database (for example, Admissions and Graduate School), you can connect each one and choose which data types it shares.

Good to know

  • Slate is the source of truth for the sessions it creates. To change a session’s name, description, time, track, or location, update the event in Slate and the next sync brings it into your guide. Capacity, registration dates, waitlist, and images stay editable in Builder.

  • Synced sessions can’t be deleted in Builder. To remove one, remove the event in Slate and it comes out on the next sync.

  • Linked folders are locked to their guide. To move a Slate folder to a different guide, contact our support team.

  • New registrants appear after the next sync, not instantly. A student who’s brand new in Slate can take one extra sync cycle, because Guidebook first needs their Slate record from Person Data.

  • Guidebook doesn’t remove data it has already sent to Slate. If you untick a guide or remove a connection, Guidebook stops sending new data, but anything already in Slate, like app usage, attendance records, or a guide’s QR Code URL, stays there. If you no longer want it, remove it in Slate.

What’s coming next

Personalized schedules: using session selections from Slate registration to build each student’s personalized schedule in the app automatically.

Learn more

Step-by-step setup for each connection:

Questions about your integration? Email slate@guidebook.com.

Did this answer your question?