How do consultants keep client requests in Slack from getting buried in threads?

What burying a request in a thread actually means

Consultants keep client requests in Slack from getting buried in threads by capturing each real ask the same day, following the thread it lives in, and keeping a list that still fires. Seeing the message on Tuesday and still owning it on Thursday are different jobs.

The ask often arrives as a thread reply with no @mention, in a Slack Connect channel or in a client workspace where you are a guest. Slack's defaults treat that as silence unless you already follow the thread. Shared channels sit on paid Slack plans on both sides. The Free plan only allows one-to-one external DMs. Pro is $7.25 per user per month billed annually, or $8.75 billed monthly, as of 23 October 2026.

Write a reply target into the engagement. Amy Sept, writing for Upwork on 13 March 2026, tells freelancers to reply within 24 hours, and to urgent requests within 4 to 6 hours or as soon as they are back online. Mursa publishes 4 business hours for standard client Slack, 1 business hour for urgent, and the next business day after hours. Its July 2026 workspace audit logged about 3,100 client-side messages across 14 client channels over 27 weeks.

A later chase until the work went out is a neighboring job, on the follow-up teammate page. Drafting the client-facing reply is another, on the approval-before-send page.

Which tool wins which job

Fund the row that matches the leak. A louder ping, a personal list, and a flagged task are neighboring jobs.

What Slack itself notifies you about in threads

Slack's default is a DM, a mention, a keyword, a channel notify, or a reply in a thread you already follow. In a multi-person channel, a thread reply notifies you if you started the thread, replied to it, or were mentioned. Opening the channel and reading only the main view still drops the reply sitting under a parent message.

To catch every reply in a client channel, turn on Follow every thread in that channel's advanced notification options, or check Get notified about all replies and show them in your Threads view. Raise that same channel to All new posts so a top-level ask without an @mention still pings.

Keyword notifications fire on exact matches in channels you have joined, and highlight the word in yellow. Slack's own note: keywords in messages sent in threads you are not following will not trigger a notification. Clients answer in threads. That setting will not save you there.

If you are signed into more than one workspace on desktop, Slack puts a numbered badge on the workspace icon when there is unread activity in another workspace. That badge is a count of unread activity. The list of open asks still has to live somewhere else, and it will not follow a thread you never opened. Activity always shows mentions, reactions, and thread replies. You can also show channels set to All new posts, and to-do reminders.

Guest accounts, Slack Connect, and who can install an app

Most consultants land in a client's Slack as a guest, or they share a channel through Slack Connect from their own workspace. Those two setups are different installs.

Guests cannot install or remove apps. They cannot authorize a Slack account to use apps. They cannot set reminders for channels or members. Single-Channel Guests cannot use shortcuts. Multi-Channel Guests can use shortcuts only if a Workspace Owner turns that on. Personal To-dos and Remind me about this still work for guests on every plan.

Slack Connect is different. Each side stays in its own workspace. Apps added by the other organization show that organization's Slack icon, and people in the channel can see messages from bots and apps. A shortcut from an app is available to you only if that app is installed to your workspace. Adding an app to a client's workspace can need that client's admin. Ask them, rather than promising a one-click install in a workspace you do not own.

Todoist connects to only one Slack workspace per Todoist account. Confirmation that a task was added is visible only to you. Chaser lets Slack Connect people and Single-Channel Guests receive assigned tasks for free. They cannot create tasks. If you are the guest, you cannot flag the incoming ask yourself.

The caveat that should decide the setup

The failure mode consultants name first is an unsupervised reply in the client's channel. One wrong send can cost the account. The quieter failure is this prompt: the request was sitting in a thread, you had seen it, and Thursday never became a task.

A second caveat is public chase. People in a Slack Connect channel can see messages from bots and apps. A reminder posted in the shared thread shows the client you are chasing the work. Keep the nudge off the thread the client can read. The recap the client sees still waits for a person to send.

A third caveat is auto-capture that you cannot install. A guest cannot add Todoist, Notion, Chaser, or Concrete to the client's workspace. Slack To-dos with an actual reminder are the native path that still works. If you work through Slack Connect from your own paid workspace, you can install on your side. Concrete is an AI employee that works in existing Slack channels: every incoming message gets a receipt mark, drafts land as Send / Edit / Skip cards, and there is no auto-send mode. After downtime it sweeps channel history, thread replies included. Follow-ups survive reboots. Each morning it nudges the owner of every open ask. Install is one button per Slack channel, and each workspace gets its own private machine. It does not give one inbox across every client Slack. It is in design-partner preview; the longer thesis is on the vision page.

Step by step: keep the ask out of the thread

This is the boring version that holds when you are a guest in several client Slacks. Pin it for yourself. Do not wait for the first 'we sent you that on Tuesday' call.

• Step 1: Acknowledge the same day. Reply, or react, so the client knows the ask landed. Name when the real work comes. "Got it, doing Thursday" is a receipt. Silence until Thursday is how the thread dies.
• Step 2: Capture the ask out of the thread that same day. Hover the message and pick Remind me about this, or Add to-do and add a reminder. Creating a to-do does not set a reminder by default. If you can install an app on your own workspace, copy the ask into Todoist or Notion the same day. Do not trust Saved with no reminder.
• Step 3: Follow the thread and set All new posts. On each client channel, set All new posts and Follow every thread, or Get notified about all replies. Keywords will not fire on an unfollowed thread. Mentions-only skips a client who never @mentions you.
• Step 4: Keep the chase off the shared thread. A bot message in Slack Connect is visible to the client. Nudge yourself in To-dos, Activity, or a private list. The reply the client sees still waits for a person to send.
• Step 5: Sweep threads in the morning. Open Threads and Activity, including workspaces that only show a badge on the icon. Channel history hides thread replies unless you open them. A catch-up that reads only top-level messages drops the actual ask.
• Step 6: Keep a person on the send button. A receipt and a to-do are not a reply. Draft if you want speed. Send stays a tap. There is no auto-send mode that is safe in a client channel.