[Day 14 of 30] Stop Drowning in Slack, Get What Matters in One Read
A simple twice-a-day workflow to triage, draft, and respond without context-switch overload.
The situation
You start the morning with a plan to move work forward.
Then Slack starts. About five messages per hour: questions, clarifications, small FYIs, “quick check” requests.
You switch context, look up context, remember where the answer lives, decide what to do with each item, then write the reply in the right tone.
By lunch you are already behind. After lunch it repeats. In the evening you are tired and behind again.
If you set a “not available” mode and reserve two batch hours (lunch and evening), you still pay the same hidden cost:
for each message you must rebuild context
you must decide what counts as “answer now” vs “defer”
you must choose a reply format and wording
The 1% upgrade
Run one batch prompt over your Slack inbox slice.
Instead of answering in real time, you ask for one output:
a triage list (FYI vs question vs request)
recommended action per item (ignore, acknowledge, reply, create task, defer)
draft replies in your voice
tasks to create when the work is bigger than one reply
a quick sanity check for missing context and duplicates
Connect Slack to your PMS inbox (two modes)
This is where the Slack inbox workflow becomes real. You choose the mode based on what your Slack admin allows.
Mode A: Slack integration is available (plugin/connector mode)
Goal: let your PMS tool read chats, mentions, and channel history through built-in Slack integrations.
Connect Slack via plugin/connector
Cursor path: Plugin -> Browse Marketplace -> search Slack -> select Slack -> Add to Cursor
Claude Code path: Connectors -> Browse Connectors -> search Slack -> select Slack -> Connect
Complete Slack authorization in browser
Approve access to your Slack workspace when prompted.
In both apps, choose the correct workspace during OAuth and confirm permissions.
Ask the agent to run a quick health check
Example request:
“Check Slack access, list chats, and read one channel/thread.”
Use the workflow in Mode A
Run the Slack inbox workflow with your preferred time window (for example “last 4 hours”).
In this mode, the workflow can work with actual Slack items and produce reply drafts.
Mode B: Slack integration is blocked, external Slack apps are forbidden
Goal: still batch-triage Slack, without Slack API access.
Core idea: treat Slack emails as your inbox input.
Turn on Slack email notifications
Notification settings are managed on this page:
https://yourspace.slack.com/account/notifications
Replace yourspace with your actual Slack workspace name.
Make sure the emails go to the same email account where your PMS tool has Gmail MCP access (your Work inbox).
Recommended settings for fast and detailed email capture
In Email notifications:
choose: Send me new notifications: at most every 15 minutes
keep notifications for: direct messages, mentions, and thread replies
In Send me an email digest summarizing activity that relates to me:
choose: once a day
enable: summary of activity that may be relevant to me, if there is no direct activity related to me
In News and updates:
turn off non-essential marketing emails, keep only operational/security emails
Ensure the emails are reachable by your PMS tool
Emails should stay in INBOX (or at least not be archived before the workflow runs).
If you filter aggressively in Gmail, add an exception for Slack notification emails.
(Optional) Keep Gmail clean
Create a Gmail label like Slack for these notifications.
Do not delete these emails or move them to a folder your PMS flow does not check.
Use the workflow in Mode B
Run the Slack inbox workflow with your time window.
In this mode, the workflow processes Slack email notifications, classifies them, and produces:
triage recommendations (ignore / acknowledge_only / needs_reply / create_task / defer)
draft replies you can review and send manually
tasks in your PMS when the work is bigger than a single message
How the fallback workflow is actually run
What powers the workflow:
Input source: Slack email notifications from your mailbox.
Processing layer: your AI chat agent with the Slack inbox prompt (below in this post).
Output: one markdown digest with triage, reply drafts, and task candidates.
Where Time Window is set:
You set it in the agent request each time you run it.
Supported examples:
last_4h
today_morning
since_09_00
Exact run flow in chat (Mode B):
Step 1: ask the agent to collect Slack notification emails for a specific window.
Step 2: ask the agent to run the Slack inbox prompt on that batch and prepare proposed replies for each unread question or request.
Step 3: copy, paste, and send those proposed replies in Slack; edit only where needed.
Step 4: review only low-confidence items, then create tasks for work that should not be answered in one message.
Example request to the agent:
Run Slack inbox workflow in Mode B for last_4h.
Source: Slack email notifications from my inbox.
Output: triage + draft replies + tasks.
Note:
The quality of proposed replies depends on how much context your system can access.
In this fallback mode, context can be incomplete.
The next article will cover how to build the missing context layer so proposed replies are closer to your real voice.
What you lose in Mode B (and why it still works)
You cannot reliably read the whole Slack thread.
Grouping is best effort based on what is present in the notification email.
You still win because you batch triage and draft replies in one pass.
Copy-paste prompt
You are my Slack inbox assistant for a personal management system.
Goal:
Turn a batch of Slack message notifications into a single actionable digest.
I want to batch this work, not react in real time.
Inputs:
1) My PMS context (auto-load first, optional paste only for missing pieces):
- First, use available PMS context automatically (week priorities, project notes, people context, recent tasks).
- If context is missing or stale, I will paste only the delta.
2) Slack batch (I will paste it):
Each item is either:
- an email notification from Slack about a message OR
- a copied message text with any permalink/link I have.
Output:
Create one markdown report with these sections:
1) Summary
- Total items
- Count by category: FYI | question | request | clarification | noise
- Top urgent item (single most urgent question/request)
2) Top urgent item (required)
Include:
- Urgency reason
- Original question/request
- Channel or DM
- Known context used
- Proposed reply (ready to copy/paste)
3) Grouped by chat (required)
Group items by channel/DM/thread.
For each chat group include:
- Chat name
- Category mix (FYI/question/request/clarification/noise)
- List of open questions in this chat
- What context is already known
- What context is missing
- Recommended next action for this chat
4) Triage list (one bullet per item)
For each item include:
- Who: author name (or “unknown”)
- Where: channel/DM/thread (or “unknown”)
- What: 1 sentence summary
- Action: ignore | acknowledge_only | needs_reply | create_task | defer
- Confidence: high | medium | low
- Link: include the link if present
5) Draft replies
Only for Action = needs_reply.
Write short and direct, in my voice:
- no fluff
- if I need time, say when I will return
- if you need clarification, ask one precise question
6) Tasks to create
Only for Action = create_task.
For each task include:
- Title
- Why now (1 sentence)
- Next step (one concrete action)
- Suggested owner: me
- Related person(s) if obvious
7) Sanity check
- Missing context I likely need
- Possible duplicates
- Items that should be answered by a single combined message
Rules:
- If something is unclear, still choose a best guess and set Confidence = low.
- Prefer one reply that answers multiple items when it is reasonable.
Now wait for my input in this format:
Slack batch:
“”“[paste here]”“”
Optional extra context (only if needed):
“”“[paste missing context here]”“”
Example output
Summary:
Total items: 12
Categories: 4 FYI, 5 question, 2 request, 1 clarification, 0 noise
Top urgent item: scope clarification requested “by today” in #product
Top urgent item:
Urgency reason: explicit same-day deadline and blocks two follow-up decisions.
Original question/request: “Can you confirm final scope today so we can proceed?”
Channel or DM: #product
Known context used: this week priority includes scope lock for release prep.
Proposed reply: “Got it. I will confirm final scope today and send a clear update before 17:00.”
Grouped by chat:
#product
Category mix: 1 FYI, 3 question, 1 request
Open questions:
final scope confirmation for today
owner for edge-case validation
Known context: scope lock is a top priority this week.
Missing context: latest decision link for edge-case handling.
Recommended next action: send one combined reply for scope and owner clarification.
#compliance
Category mix: 2 question, 1 request
Open questions:
which data fields are mandatory for this phase
Known context: compliance checklist exists in project notes.
Missing context: legal confirmation on one field.
Recommended next action: create one task and reply with ETA.
Triage list (one bullet per item):
Who: Alex | Where: #product | What: asks for a quick check on an open question about scope | Action: needs_reply | Confidence: high | Link:
Who: Maria | Where: #compliance | What: clarification on which data fields must be included | Action: create_task | Confidence: medium | Link:
Draft replies:
Alex: “Got it. I will confirm the scope today and send a clear answer before 17:00.”
Tasks to create:
Confirm compliance fields for the new workflow | Why now: message asks for a decision path and it impacts the build plan | Next step: open the existing spec, list required fields, ask legal for confirmation | Suggested owner: me
Sanity check:
Missing context: one thread references a doc name that is not in my notes
Duplicates: two items look like the same question posted twice
10-minute action
Do this in one batch cycle:
set a clear Time Window first (for example last_4h or since_09_00)
collect 10 to 20 Slack items for that window (plugin mode: unread chats/threads, fallback mode: Slack email notifications)
let the assistant auto-load PMS context first; paste only missing context if needed
run the prompt and review in this order: Top urgent item -> Grouped by chat -> Triage list
copy, paste, and send proposed replies for high-confidence needs_reply items, then edit only low-confidence replies
convert create_task items into real tasks in your PMS, with links back to the source chat or email
What to do next
If you can answer fewer messages per hour but answer the right ones, you get your day back.
This is the workflow:
batch your Slack slice
use vault context to reduce “context rebuilding”
decide action in one pass
draft replies, then send or defer
Paid artifact
An auto-run workflow that processes Slack in the background on a fixed schedule (for example at lunch and end of day), so you get a ready digest without asking Cursor or Claude Code to run it manually each time
Keep reading with a 7-day free trial
Subscribe to Your Daily 1% Better at AI to keep reading this post and get 7 days of free access to the full post archives.