At some point in almost every procurement conversation, someone asks a version of the same question: "But can it do X?"

It's a good question. You should ask it. And here's what our product team believes: the most trustworthy answer a vendor can give you is an honest no.

So here it is. Three things Guidebook doesn't do. Why we've made that choice deliberately. And what it means for your yield numbers, your orientation outcomes, and the students showing up on your campus already feeling like they belong.

Built for moments. Not for records.

Guidebook doesn't replace your CRM. It handles what your CRM can't.

If you're running admissions at a private or regional university, you almost certainly live in Slate, EAB Navigate, or a similar enrollment platform. Those tools are excellent at what they do. They track applications, manage communications pipelines, segment your prospect pool, and store every interaction a student has ever had with your institution.

What they can't do is tell a prospective student which building their welcome session moved to at 7:45am on Admitted Student Day.

That's the gap Guidebook fills.

When a student walks onto your campus, Slate goes quiet. The record exists. The relationship doesn't. What the student experiences in the next eight hours is what decides whether they deposit: whether they can find the room, whether the schedule makes sense, whether your institution feels like it has its act together or not.

Many admissions teams tell us they assumed Guidebook and their existing enrollment platform would overlap. They were surprised to find they weren't competing for the same moment at all.

What does Guidebook do that a CRM doesn't?

Guidebook manages the on-campus experience: the real-time schedule, the campus map, the push notification when a session moves, the personal agenda a student builds before they arrive. It's the layer between your database and your student's phone on the day it matters most. Your CRM owns the record. Guidebook owns the moment.

75% of top 50 U.S. colleges trust Guidebook for exactly this reason: they have enrollment platforms, and they still need this.

Guidebook doesn't send mass communications. It delivers the right information at exactly the right moment.

Your enrollment platform sends the emails. Guidebook is what a student opens when they're standing at the campus entrance wondering where to go first.

These are different jobs. One is pre-arrival. The other is present-tense.

A common frustration many admissions teams describe is this: they send every admitted student multiple emails in the weeks before an Open House or Admitted Student Day, and by the time the day arrives, students still wander into the wrong building, miss the session they wanted, or can't find the dining hall. The information was sent. It wasn't received, not in a way that was useful when it was needed.

That's not a student attention problem. It's a delivery-channel mismatch. Email is for before. The app is for during.

Guidebook gives your team a channel that's live, real-time, and in the student's pocket. Push a schedule change at 8am and every student with the app sees it before the session starts. No reprinting. No shouting across a lobby. No staff stationed at every hallway junction.

Learn how the admissions and enrollment teams we work with run their events, including how they use Guidebook alongside, not instead of, their existing communication stacks.

Guidebook doesn't manage event registration. It makes the experience after registration worth showing up for.

Registration is the before. Guidebook is the during.

When a student signs up for your Admitted Student Day through your institutional system, through Eventbrite, or through Slate's event module, that registration is yours to manage. Guidebook doesn't need to touch it.

What Guidebook does is pick up the moment a student arrives. The schedule is in the app. The map is in the app. The personal agenda they built ahead of time is in the app. The session feedback form they fill out before they leave is in the app.

It's worth noting: Guidebook does offer a Registration and Check-In product for teams who want to consolidate. But it's a choice, not a requirement. Many of our university partners keep their existing registration systems and simply connect the experience layer on top. Your stack, your call.

The point is, we're not here to replace what's working. We're here to make the part that follows it better.

What Guidebook is built for (and what that means for your yield numbers)

Every deliberate limitation above points to the same thing: Guidebook is built for one job. The in-person experience of your student-facing events, from the first Open House to the final Welcome Week session, on the device your students actually use.

That focus is a product philosophy, not a gap in the roadmap.

And it produces results you can measure.

Andrea Crilly, Assistant Director of Admissions for Campus Experience at Indiana Tech, watched her institution's yield on Admitted Students Day go from 40% to 82% after moving to a Guidebook-powered experience for their admitted student events. Her team went from five people spending 400 hours on event materials to two people spending 25 hours. Printing costs fell by 29%, a four-figure saving per event.

Those aren't software outcomes. They're enrollment outcomes. The difference between a student who attends an Admitted Student Day and feels looked after, and one who wanders a campus that doesn't seem to know they're coming.

Read the full Indiana Tech case study to see what that shift looked like in practice.

Your yielded class is made in the moments between deposit and move-in. Guidebook doesn't manage your records, send your emails, or run your registration. It makes the moments themselves worth having. That's the idea behind one app for every moment that matters.

If that's the gap you're trying to close, let's talk.

[faq]
Q: Does Guidebook integrate with Slate or other CRM platforms?
A: Guidebook works alongside your CRM rather than replacing it. Many university admissions teams use Slate, EAB Navigate, or similar enrollment platforms for their communications pipelines and application management, then use Guidebook to power the on-campus experience of their events. The two tools serve different moments in the student journey and don't need to compete. For specific integration questions, your Guidebook account team can walk you through what's possible for your setup.
Q: Can Guidebook replace our existing event registration system?
A: It doesn't have to. Most of our university partners keep their existing registration systems and use Guidebook as the experience layer on top. Students register where they always have, then use Guidebook on the day itself for the schedule, campus map, push notifications, and personal agenda. That said, Guidebook does offer its own Registration and Check-In product for teams who want to consolidate, but that's a choice, not a requirement.
Q: How long does it take to build a Guidebook app for an Admitted Student Day?
A: Most teams are building and launching in days, not weeks. Guidebook's drag-and-drop builder requires no technical training, and many admissions coordinators build their first guide in a single afternoon. Indiana Tech's team, for example, reduced their total event preparation time from 400 hours across five staff members to 25 hours with a team of two after switching to Guidebook.
Q: Does Guidebook send push notifications to students?
A: Yes. Push notifications are one of the most-used features on event day. Your team can send real-time updates to all attendees or specific segments, whether that's a room change, a schedule update, or a reminder about the next session. Notifications go directly to the student's phone, which is where they're already looking.
Q: What data does Guidebook give us after an event?
A: Guidebook's analytics dashboard shows you which sessions were most attended, which content pieces got the most views, how many students downloaded and actively used the app, and engagement patterns across the day. That data is useful both for reporting internally and for refining your event experience year over year.
Q: Is Guidebook only useful for large institutions?
A: No. Guidebook is used by institutions ranging from small private colleges to large research universities. The no-code builder is designed so that a one- or two-person admissions team can own and run it without IT involvement. The value of a well-organised, real-time mobile experience doesn't scale with institution size. It scales with how much the student experience matters to your yield numbers.
Q: What's the difference between Guidebook and a university portal or website?
A: A university portal or website is designed for broad, persistent access to institutional information. Guidebook is designed for a specific moment: when a student is on campus, at your event, and needs to know what's happening right now. It's a native mobile app, not a website formatted for a phone, which means it works faster, sends push notifications, and delivers a student experience that feels like your institution has its act together.
[/faq]