Early Wins with Mongoose: What Real Customers Say About Getting Started

Getting started with a new student engagement platform is usually the part nobody talks about, but it’s often where teams learn the most. This post pulls real, named moments from Mongoose customers in their first weeks and months: A SUNY admissions office that fixed a years-long deliverability problem overnight, a community college coordinator who sent an early campaign to the wrong-sized audience and turned the fallout into a lesson, and a private college marketer who sent her first text “terrified” and got 230 replies back.

These are early-stage stories, not year-end results. If you’re evaluating Mongoose and wondering what the first few months actually look like, this is a good place to start.

---

SUNY Alfred State College of Technology: A Deliverability Fix Overnight

Tony Rudolph had a specific, nagging problem before he brought Mongoose to SUNY Alfred State College of Technology: his texts weren’t landing. As part of the SUNY system, Alfred State shared one EIN number with every other SUNY campus, and carriers were treating the whole system as a single sender. His deliverability rate was stuck at 16 percent.

Rudolph, now Associate Director of Admissions at Alfred State, had worked with Mongoose at a previous institution and brought the team in to fix it. The change didn’t take a semester to show up.

“Our deliverability rate went from 16% to above 90% by working with Mongoose. That completely changed our entire strategy and certainly our success.”

— Tony Rudolph, Associate Director of Admissions at Alfred State College

Not every early win is that fast. Some come with a stumble first.

Century College: The Mistake That Became a Lesson

Aniell Ducat, Communications Coordinator at Century College — a community and technical college in White Bear Lake, Minnesota — was still new to segmentation when he sent one of his first big campaigns. Ahead of fall semester, he wanted a quick read on how students were feeling, so he sent a simple prompt asking students to reply with an emoji. He sent it to 4,000 to 5,000 students.

“We have tons of text messages coming in. Just a flooding of GIFs and emojis,” his director told him — and it took nearly two days to work through the responses. Aniell’s takeaway wasn’t to stop experimenting. It was to understand his audience size and his team’s capacity before a send, and to treat texting as the two-way conversation it’s built to be, not another form of email.

Knox College: First Campaign, First Surprise

When Natasha Caudill joined Knox College as its Digital Communications Specialist, texting was still mostly one-off messages and a default welcome note. She saw room to do more, but the first send didn’t feel confident.

“The first few texts I sent, I was terrified. But I quickly realized we could do so much more — and students were actually paying attention.”

— Nathasha Caudill, Digital Communications Specialist, Knox College

One of her early campaigns, a holiday-themed quiz text, pulled in more than 230 responses. That early signal is part of why texting at Knox went from a utility to a strategy, one built around campus moments like admit-day mascot messages and live coverage of campus traditions.

Gwinnett Technical College: Testing It Before Trusting It

Carolyn Duven had been burned by a chatbot before. Her previous vendor’s bot ran on rigid, pre-loaded scripts, and it showed: students would type “English classes” and get back a reminder to complete their FAFSA. So when Gwinnett Technical College sat down for its Mongoose Chat demo, Duven’s team didn’t ease in.

They built a page called “Break the Bot” and fired off the kinds of fragmented, half-sentence questions real students actually ask. As Duven, Executive Director of Student Support Services, put it:

“That really sold us on the quality of the Mongoose Chat product and how easy it is to train it.”

— Carolyn Duven, Executive Director of Student Support Services, Gwinnett Technical College

That first test became the reason Gwinnett Tech moved forward — and the bot, now nicknamed “Griff,” handles routine questions for a call center staffed by just four people.

What These Stories Have in Common

None of these are year-end wins. They’re the moments that came before the wins — a compliance problem solved in a day, a mistake that taught a team how to size a campaign, a first send that landed better than expected, a demo that earned trust before a contract did.

That’s usually what getting started with Mongoose actually looks like: a few weeks of testing, and a team that starts trusting the platform enough to build on it.

Same team. More capacity. Better outcomes. (It just tends to start smaller — and messier — than people expect.)

See what getting started could look like for your team. Book a demo or browse more Mongoose case studies from institutions like yours.

---

Author: