After years of disconnects and delayed support, this three-campus charter school switched from Raptor to Coram EMS—getting set up quickly, launching in a single meeting, and regaining confidence in day-to-day readiness.
Customer Snapshot
✅ Customer: Big Springs Charter Schools
✅ Industry: Education (Charter School)
✅ Use Case: Emergency Management System (EMS); reunification readiness
✅ Segment: Three campuses (two in Ingram, Texas; one in Leakey, Texas)
“It’s literally been night and day.” That’s how Daniel Peck, Technology Director at Big Springs Charter Schools, describes the difference after his district moved from Raptor to Coram’s Emergency Management System.
Before Coram (Challenge)
Peck’s role is simple to describe and hard to execute: “Basically, if it’s plugged into a wall, it’s pretty much my job to make sure that it’s working.” For emergency management, that standard wasn’t being met.
Big Springs had been using Raptor (selected before Peck joined) and he says the experience was dominated by instability and friction. “It was a constant hassle, headache. Everything disconnected on the regular, and nothing worked.” When issues hit, support lagged significantly. “It would usually be at least 24 to 48 hours to fix anything.”
The problems went beyond reliability. Peck recounts repeated setup loops, unclear guidance, and a high-stakes failure around reunification readiness, all while the district continued paying for the service.
The Switch to Coram
Peck first explored Coram during a previous investigation into video security. “We did a trial with it and it was pretty awesome,” he said, though funding delayed the upgrade. When it came to EMS, the contrast was immediate.
“The test was set up in maybe 15 minutes… It worked great,” Peck said. When the district was ready to launch broadly, what he expected to be a drawn-out process wasn’t. “I was expecting another round of months… It was done by the end of the meeting.”
The final push came after a breakdown with Raptor over an invoiced service the district no longer needed – an added cost Peck estimated at “four or five thousand dollars a year.” Weeks passed without resolution, then collections outreach followed, still tied to the disputed invoice. Leadership stepped in, and Peck was ready with an alternative. “Finally they aggravated our superintendent enough to where he was like, ‘what’s that other one called?’”
Coram’s responsiveness sealed the decision. “Corey had the new quote iin a couple of hours. And we had everything ready to go.”
Life With Coram (Results)
The impact was practical and immediate: faster setup, clear progress, and a team that adapted to the district’s needs.
Before: Frequent disconnects; “nothing worked”; 24–48 hour support delays; confusing setup.
After: EMS trial “set up in maybe 15 minutes”; district launch “done by the end of the meeting”; a “night and day” user experience.
Why Coram?
- Fast setup: “The test was set up in maybe 15 minutes.”
- Smooth launch: “It was done by the end of the meeting.”
- Accommodating onboarding: “They literally customized it to us.”
- Better overall experience: “It’s literally been night and day.”
- Responsive, partner-like team: “Everybody there has been phenomenal.”
Recommendation
“I can’t stand Raptor… Raptors garbage Quorum is awesome.”
.webp)