How does a design studio stop client feedback rounds from dying in Slack threads?

What dying in a Slack thread actually means

A design studio stops client feedback rounds from dying in Slack threads by putting each round on the file, naming one owner, giving the round a close date, and capturing any Slack dump the same day so it still fires. Seeing 15 comments in a thread is not the same job as owning the round, and owning the round is not the same job as closing it.

Studios run this job in a Slack Connect channel shared with the client. Slack has no native owner on a thread, so the account lead and the designer can both see the dump and each assume the other copied it onto the file. 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 28 October 2026.

Write two clocks into the retainer. 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. Milk Moon Studio asks clients to compile a round within 2 days, 48 hours, of receiving the draft, and treats each feedback message as a round unless it arrives as one batch. Filestage's async-feedback guide uses the same 48-hour example as a review deadline.

A round is a batch. Confetti Design writes that most branding agencies include two to three structured rounds in a standard project fee, and that a round should be one compiled checkpoint rather than every casual Slack note. Slack's own figures for agency partners claim a 50% cut in review and approval turnaround and 80% fewer emails with the agency. Missing pings are a neighboring job, on how agencies stop missing client messages in Slack Connect. A spoken "I'll send v2 Thursday" is another, on the commitments-from-threads page.

Which tool wins which job

Fund the row that matches the leak. A pin on the file, a due date on the round, and a Slack dump that still fires are neighboring jobs.

What Figma and Slack actually do with comments

Figma comments live on the canvas. Can view means the client can view and comment without editing. Resolve hides the pin from the sidebar and the canvas. Unresolve exists if someone closes a thread too early. Milk Moon Studio tells clients to comment in Figma so the studio knows the element, can resolve the thread, and keeps the round in one place. Slack is the ping that the round is ready.

Figma for Slack is a notification pipe. Default notifications are comments you were mentioned in, plus invites, and they land in the Figma app channel. Channel subscriptions need can-edit access on the file, folder, or team. Comments made within 10 minutes of each other batch into one Slack message. File previews in Slack require edit access. A client with can view can still comment in Figma. That comment will not fan out to a subscribed channel unless someone with edit access set the subscription, or someone was @mentioned.

Slack's default is a DM, a mention, a keyword, or a reply in a thread you already follow. Clients answer in threads. Opening the channel and reading only the main view still drops the reply sitting under the Figma link. Follow every thread, or Get notified about all replies, on the client channel. Keyword notifications skip an unfollowed thread. Conversation summaries on Pro catch you up on a thread you open. They do not resolve a comment, and they do not close a round.

Filestage's own async-feedback guide says Slack was not built as a dedicated review tool: design feedback fragments across channels, and approval decisions get buried in conversation history. A cropped screenshot with a circle drawn on it is the live-prototype version of the same leak.

When a proofing tool is the round

Figma comments win when the work lives in Figma and the client will open the file. A proofing tool wins when the round needs a due date, a decision state, and a reviewer who will not make a Figma account. That is the Filestage and Ziflow row. Priced options for the Slack side of the same studio live on the AI tools roundup.

Filestage Starter is $199 per month as of 28 October 2026. It adds due dates and reminders on top of the Free plan, compares two versions side by side, and lists Slack under basic integrations. Reviewers do not need an account. Mark comments as resolved is on Business at $329 per month. Filestage's async guide tells teams to name who must review, who is optional, a deadline such as 48 hours, and what good feedback looks like, then close the loop with a decision owner.

Ziflow Standard is $199 per month billed annually, with unlimited proofs and reviewers, proof deadlines, and manual reminders. Slack notifications for new proofs, comments, and decisions, plus mark comments as resolved, ship on Pro at $329 per month billed annually. People in a Slack Connect channel can see messages from bots and apps. A Ziflow or Filestage ping in the shared channel is visible to the client.

Chaser wins the thinner job: the client already dumped the round in Slack, and you need an owner and a due date on that message. Reminders post in the thread. Keep that in mind if you do not want the client to watch you chase your own designer. A morning list of still-open asks is on the daily summary page.

The caveat that should decide the setup

The failure mode studios name first is an unsupervised reply in the client channel. One wrong send can cost the account. The quieter failure is this prompt: the client pasted 15 comments under the Figma link, three people had seen the thread, and nobody pinned them on the file before Thursday.

Clients dump in Slack even when the onboarding note asks for Figma comments. A Reddit project-management thread from March 2026 described one web-design client who left three Figma comments, a voice note, a 9pm Slack message, and a follow-up email the next morning that contradicted two of the earlier notes. The working fix in that thread was one consolidator, and a written rule that the compiled batch is the round. Milk Moon Studio already runs that rule: comment in Figma, then ping Slack or email when the page is done.

A second caveat is Figma for Slack. It notifies Slack about comments that already live on the file. It does not turn a Slack thread into a round. Subscribe the client channel if you want Figma mentions in Slack. Still copy a Slack dump onto the canvas the same day.

A third 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 round. Keep the nudge off the thread the client can read. Safety of putting an agent in that channel is on the shared-channel page. 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. It is in design-partner preview; the longer thesis is on the vision page. Drafting the client-facing reply is a neighboring job, on the approval-before-send page.

Step by step: keep the feedback round alive

This is the boring version that holds for a 3-to-30 person studio when the owner is still the account lead. Pin it during onboarding, not after the first "we sent notes on Tuesday" call.

• Step 1: Name the round in the channel. State the version, the kind of feedback you want, and the close date. Milk Moon asks for compiled feedback within 48 hours of the draft. Filestage's async guide uses the same 48-hour example. Confetti Design counts a round as one structured checkpoint, not every casual Slack note.
• Step 2: Put comments on the file. Share the Figma file as can view so the client can comment without editing. Ask for pins on the element, not a paragraph in Slack. A proofing tool is the path when the reviewer will not open Figma. Slack is the ping that the round is ready.
• Step 3: Name one studio owner and one client consolidator. A group in the channel recreates the bystander effect. Milk Moon asks one client-side person to collect stakeholder notes before the studio sees them. Conflicting color preferences from three stakeholders are one round only after someone compiles them.
• Step 4: Write the Slack reply target. Acknowledge standard messages within 4 business hours, high-touch within 1 hour, and after-hours the next business day, in the client's timezone. "Got it, compiling by Thursday" is a receipt. Silence until Thursday is how the thread dies.
• Step 5: Capture Slack dumps onto the file the same day. When the client pastes 15 comments under the Figma link, copy each item onto the canvas or the proof as a pinned comment that day. Add a Slack To-do with a reminder, or a Chaser task, if you need the dump tracked before you pin it. Follow every thread on that channel. A catch-up that reads only top-level messages drops the actual notes.
• Step 6: Close the round and keep a person on the send button. Resolve the Figma comments. Send the next version. The "round is closed, v2 is up" message waits for a tap. There is no auto-send mode that is safe in a client channel. Follow-up on an unanswered request is a neighboring job, on the AI teammate page.