At our 84-unit community we logged 26 maintenance requests in 12 hours after last night’s storm, and I’m triaging within our 24–48 hour window while keeping residents in the loop. Tagging “safety-first” vs. “comfort-impacting” has helped, but if you use AppFolio or Buildium, do you see better results from a 5 p.m. batch SMS update or a same-day portal note with ETA ranges? I’m aiming to set expectations kindly and keep emergencies first without bouncing tenants between channels.
We’ve had better outcomes with a 5 p.m. batch SMS, but only when it links to a same-day portal note with ‘ETA ranges’ and a pinned banner that says when the next update drops. In AppFolio I prefix texts with ‘[S1]’ for ‘safety-first’ and put unit-specific ETAs in the work order comment so the portal stays the source of truth — like weather radar, check once, not every five minutes.
And @alex6127 +1 on the banner; adding a brief noon ‘checkpoint’ SMS with “Bldg A 60%, Bldg B triage in queue; next touch 5 p.m.” keeps the rumor mill from sprinting. In AppFolio, we add a ‘next touch’ field on each work order and use a saved blast template to merge it — SMS only for safety/no-water, everyone else gets the portal note; does Buildium let you merge fields like that?
Have you tried an SMS auto-reply that confirms receipt and returns a per-building code — residents text back “A” or “B” to get the latest ETA snapshot without staff lift? We refresh the snapshot at 4 p.m. and whenever a safety item clears, which cut callbacks by about 30%; it’s a pizza tracker for roofs. Small caveat: it only works if your SMS list is clean and opt-ins are solid.
Given your 24–48 hour window, I’d send a 5 p.m. SMS that links to a simple public “storm hub” (Google Sites/Notion) with timestamped ETAs per building, then mirror that link in AppFolio. @racevan this cut repeat tickets about 50% for us last storm and keeps residents without portal access in the loop. The only caveat: commit to a fixed update time so the link stays trusted.