New Slack Protocol

📢 Submitting Deliverables to Danny in Slack

Hi team!

Whenever @Danny requests a deliverable (document, spreadsheet, design, etc.) in Slack, please follow this process to keep things organized and easy to track:

1️⃣ Reply in a thread with the file

📎 When you're submitting the deliverable, always reply directly in the thread of Danny's original message in Slack. 🔍 This keeps the context clear and avoids scattered follow-ups.

2️⃣ Forward that message to #docs-for-dk

📂 After posting your reply with the file, forward that exact message (not just the file) to the #docs-for-dk channel. 📌 This channel acts as a centralized archive so Danny can quickly find what he needs—no digging through DMs or chat history.

🔖 For Easy Access:

For Danny, please ⭐ star the #docs-for-dk channel to keep it pinned and easy to access in your sidebar.

Stay Organized 🙌

This simple protocol helps prevent important files from slipping through the cracks and ensures smoother collaboration.

📢 Proper Handover/Escalation for SS Team

• If an SS team member reacts with a 🔵 on a support request, it means you are taking ownership of the task and are expected to handle and close it.

• If you’re unable to close it before your EOD or will be off the next day, make sure to do a proper handover to another SS team member. This ensures there’s clear accountability and continuity until the task is fully resolved.

• When doing Slack backreads, if you come across a tagging you can’t attend to immediately, mark it as “Save for Later.”

 → This helps make sure we don’t miss any requests, especially when juggling multiple tasks.

• After handing over a task in the Slack thread, send a quick DM or drop a note in the SS group chat to confirm it’s been passed on.

 → This adds another layer of assurance so nothing gets buried under other messages.

These steps help ensure no support requests are left hanging and that every tagged task is properly followed through until resolved.

Updated by Anna ( October 28, 2025)