School Answers already does the hard part: it answers a parent’s question from your school’s own documents, connected drives, and website, with citations, and routes anything it can’t confidently answer to a human with a department, a priority, and an SLA timer. What happened after that routing was the gap, and Community Desk closes it.
Apptegy routes. Community Desk finishes the job.
Apptegy’s Community Experience module routes an unanswered question to staff. That’s real, and useful, but routing isn’t the same as resolving. A question that lands in a shared inbox with no owner and no deadline is one document-management step removed from the phone-tag it was supposed to replace.
Community Desk adds the parts that make an escalation an actual task instead of a notification: an assignee, pulled from the same People list a school already manages, not a new staff directory to maintain. An SLA countdown that’s visible, not just tracked silently in a database somewhere. And a close-out, with a resolution note, that the original asker actually sees, on whatever channel we have contact information for, email, SMS if the question came in by text, or an in-app push if the asker is a signed-in Bloomz parent. Closing a ticket without telling the person who asked isn’t closing it, it’s just changing a status field. Community Desk treats the notification as part of the job, not an optional extra.
What families keep asking, and where the gaps actually are
The second half of Community Desk looks backward instead of forward: a weekly digest of recurring questions, grouped by category, with sample questions and counts, cross-referenced against your existing coverage scorecard. If a category has real volume, two or more questions in the window, but isn’t marked covered in your knowledge base, it gets flagged as a content gap. That’s the difference between knowing your AI answered 200 questions last week and knowing which 15 of them it’s about to get asked again because nobody’s written the actual policy page yet.
School Answers already draws on your school’s Bloomz posts and documents as well as your website, so this “what are people asking” signal spans both, not just whatever happens to be indexed from the public site. A website-only competitor can’t see the questions that never made it past the front page.
Built into the existing admin console
There’s no separate app to open. The escalations tab in the School Answers admin console now shows an assignee column, an SLA badge, and a Close action alongside the existing Respond button. A new Recurring Questions tab gives you the 7, 30, or 90-day window switch and a one-click “send this week’s digest now” button, for the week you don’t want to wait on the schedule.
Community Desk ships as part of Bloomz 360, behind a flag, on the same School Answers page. Talk to your success manager about turning it on this fall.