Had a 2:10 a.m. elevator fault and a brief Opera Cloud slowdown this week, and I realized our after-hours escalation could be tighter to resolve fast without waking half the building. Does anyone have a one-page checklist/contact tree you use for night-shift incidents that keeps guest impact minimal? I can share our current draft if someone’s willing to sanity-check it.
I’d keep a laminated one-pager at the night desk with a 3‑minute triage script and “roles, not names” on-call numbers — elevator = facilities, Opera Cloud = IT/network — with a clear wake-up threshold so you don’t ping the GM for a blip. Add two pre-approved guest lines (stall + comp thresholds) so the agent isn’t improvising; if your team rotates a lot, throw a QR to the live contact sheet. If you share the draft, I’m happy to sanity-check and suggest a one-call tree — like a fire drill, not a scavenger hunt.
Set up a one-tap “After Hours” macro in Teams/RingCentral that rings Facilities for 90s, then IT, then GM, and stops on the first “ACK to stop,” plus auto-creates a templated incident note in Opera Cloud with time/impact/next check — think fire drill, but on tiptoes. If you’re not on those platforms, a simple call queue with confirm-to-acknowledge works just as well. Want to DM your draft and I’ll sanity-check it?