From the Front Lines: What 7.5 Years in EdTech Platform Support Taught Us About Virtual Learning Failures
Before ClassQuip, we spent years on the other end of the phone: teachers whose polls never loaded, students stuck in waiting rooms, parents trying to explain a frozen screen they could not see. Those calls shaped every product choice we made when we finally built our own classroom.
People assume platform support means resetting passwords. That was part of it. The rest was listening to classrooms in real time—an eighth-grade teacher whispering so she would not wake a sleeping toddler while she troubleshooted a mic, a counselor reading error messages aloud from a student’s kitchen table, a principal asking whether attendance would still sync if half the class got kicked offline. Austin handled most of those technical escalations across seven and a half years supporting large-scale virtual learning infrastructure. Savannah was in schools watching what happened after the call ended: did the kid rejoin, or did they quietly miss the lesson?
We did not set out to become edtech founders on day one. We set out to stop seeing the same failures repeat every semester. When you sit with enough districts, you notice the problems are not random. They cluster around a handful of decisions product teams made for corporate meetings, then sold into K–12.
Failure mode: class as a tab scavenger hunt
The most common pain was not exotic. Teachers opened a video call, then a poll, then a document, then something for breakout work. Students copied links from chat and opened the wrong one. Someone shared the poll link instead of the room link. The first ten minutes of block disappeared into logistics that had nothing to do with the standard on the board.
Support could walk a teacher through it, but we could not be in every room every morning. The workaround culture was exhausting: printable link cards, classroom aides whose real job became tab police, students marked disengaged when they were actually lost in another window. Savannah kept saying what teachers said to her in plainer language: “I am not running a webinar. I am running sixth period.”
ClassQuip decision: one owned room link for the term. Video, deck, board, polls, timers, and group tables live in that same tab. No separate login tour for each tool. The student who shows up late clicks one link and lands in class, not in a maze.
Failure mode: the device nobody tested on
Sales demos ran on fast laptops with wired internet. Class ran on four-gigabyte Chromebooks on Wi‑Fi that dropped when the bus lane filled up. Austin lost count of tickets that were really memory pressure: video eating the machine alive while three other tabs fought for scraps. The browser would kill something silently. The teacher saw a blank face on camera and assumed the kid checked out.
Parents called when homework “worked fine” but live class did not. Often the child was on a phone or an older machine doing their best. Telling a family to buy better hardware was never an acceptable answer for a public program.
ClassQuip decision: build for the Chromebook first, not last. Keep the live room lightweight. When connection gets rough, favor keeping students in the conversation—even if that means audio-first for a stretch—instead of freezing the whole class while one device catches up.
Failure mode: teaching stopped for IT
Teachers are not IT staff, but the stack treated them like tier-one support. Unmute buttons hidden three menus deep. Screen share prompts that scared teachers out of showing student work. Breakout flows that sent half the groups to the wrong place. Every minute spent fixing the tool was a minute not spent on feedback, relationships, or the kid who needed one clarifying example.
Savannah pushed us on language and layout: labels a substitute could read cold, controls that stay in the same place every day, participation that looks like raising your hand—not like configuring software. Austin pushed on what happens when something still breaks: clear diagnostics staff can act on instead of “try again later.”
ClassQuip decision: put teaching actions on the main screen, not buried in settings. Give districts a path for tech staff to join a room when they need to, without turning every teacher into a network engineer.
Failure mode: participation that only looks good in screenshots
Plenty of tools could launch a poll. Fewer made the answers usable in the next sixty seconds of instruction. Teachers told us about polls that exported to spreadsheets they would never open during class, or chat boxes that became a side conversation they could not moderate while teaching. Engagement features became another window to babysit.
We also heard from students who never typed in chat because their name sat next to every message. Shy kids were invisible; loud kids dominated. That is not a personality problem. It is a room design problem.
ClassQuip decision: polls, word clouds, and checks that stay tied to the live lesson—results on the board while conversation continues. Quip Tables for small group work that pulls everyone back to the main room without a separate meeting link. Tools that respect a teacher’s pacing instead of fighting it.
Why we started ClassQuip
Support taught us where the bodies were buried. Classroom work taught us what “fixed” should feel like on a Tuesday in February. We did not want to add another app to the pile. We wanted to remove steps until live class felt like class again—on the devices districts already own, with sign-in patterns districts already trust.
ClassQuip is the product those years pointed toward: one tab, built for K–12, free for individual teachers who want to try it in their own room before anyone signs a district agreement. We still read hello@classquip.com like we used to answer the phone—tell us what broke, which period, which device. That is how the roadmap stays honest.
If you lived the tab shuffle or the Chromebook freeze, you already know the failures we are describing. Come see whether one room link changes your morning at classquip.com/demo, or open a free classroom at classquip.com/signup.
— Austin & Savannah