For our March 14 conference at Harbor Center, I’m piloting a shared Slack Connect channel to centralize client questions, vendor ETAs, and last-minute floorplan tweaks during the 6–10 a.m… load-in. Has this streamlined your concierge desk ops, or did it just shift radio chatter to another place?
concierge desk ops, or did it just shift radio chatter to another — It streamlined for us once we forced all non-safety updates into one Load-in thread with // reactions and had a dispatcher post 10-min rollups; radios stayed for emergencies only. Would you mandate threads for vendors in Slack Connect?
My take: I’d lean toward the simplest next step and see if it changes anything this week — if not, you’ve got a clear case to escalate. What would block you from trying that?
Building on @amelia_hugh92: we use a tiny Workflow form (“Update | Location | ETA”) that drops every submission into one ‘Load‑in’ thread and auto-mentions the vendor; only “safety/egress” goes to radio. It streamlined things, but only after we named a thread lead to post 15‑min recaps — want the workflow JSON?
Quick win: set the Connect channel to announcement-only 6–7 a.m. and have @concierge post a 10‑min rolling update; everyone else uses emoji for status, and ETAs land in a pinned sheet. It cut repeats because the latest floorplan, dock map, and ‘who’s on site’ lived in bookmarks — rule of thumb: ‘if it takes longer than a tweet, call it in.’ Small caveat: keep radios for true safety and a wired Slack fallback if Harbor Wi‑Fi wobbles.
/
/
reactions and had a dispatcher post 10-min rollups; radios stayed for emergencies only. Would you mandate threads for vendors in Slack Connect?