Two small features, shipped together, both do the same thing in different corners of the platform: they take data that already exists somewhere in Bloomz and put it in front of a family without anyone retyping it.
Attendance Conversations: a text reply that actually lands somewhere
Auto Notices already sends the automated absence text. The gap was the reply. A guardian could text back “he’s sick today,” and until now that reply either went nowhere useful or attached itself to whatever conversation thread happened to be most recent, which is not the same thing as the outreach it was actually answering.
Attendance Conversations closes that gap with a fix that sounds small and isn’t: the reply now correlates to the specific absence outreach it’s responding to, using the guardian’s phone number and a recent-outreach time window, not a generic “most recent thread” guess. A quick-reply reason, sick, appointment, transportation, family emergency, or something else, auto-applies to that day’s attendance record. Apptegy Attendance Pro and SchoolStatus Attend both do two-way attendance texting too. What neither can do is write the reply into an underlying student record that also drives a risk score and a notice ladder, because neither has one. Bloomz does, so the reply doesn’t just get logged, it actually excuses the day.
There’s a second layer here that matters more than the convenience. If a reply discloses something sensitive, a family losing housing, a safety concern, a health crisis, the message still delivers normally. Nothing gets blocked or held back from the office. But a Thrive case opens automatically, and a counselor gets paged. A follow-up question can go out, but only on a staff member’s explicit approval, never fired automatically by an algorithm. That’s the same AI posture running through every Bloomz feature: AI proposes, a human decides.
Weekly Learning Summary: the Friday email a teacher stopped hand-building
The second module solves a different, more mundane problem. Plenty of platforms sell a “weekly digest” email. Most of them are a template a teacher fills in by hand, which means the digest is only as current, and only as honest, as whoever last had ten minutes to write it.
Weekly Learning Summary composes itself from what actually happened. Assignments due and missing come from Bloomz’s own native assignment records. When a district connects Google Classroom, grade movement and newly-missing work ride along too. Portfolio highlights and the week’s attendance round out the picture. Every family gets it translated into their own language, once per distinct language across the school, not once per recipient, and delivered through the exact same notification pipeline as every other Bloomz alert.
A district picks how much human oversight it wants. Some schools want a teacher to glance at the queue before a hundred family digests go out; that’s teacherReview mode. Others want it fully automatic every Friday at 1pm local; that’s a one-switch config change. Either way, nobody is retyping a recap from memory on a Friday afternoon.
Where to find them
Attendance Conversations is a sub-feature of Bloomz Thrive, available behind a district flag. Weekly Learning Summary has its own product page and ships on Bloomz Complete and 360. Both are part of this fall’s release; talk to your success manager about turning them on for your district.