The fortieth ask of the week
Slack is where product questions actually arrive. Pins, FAQs, and search lose to a channel’s design — it forgets on purpose.
Somewhere in your workspace there is a channel — #ask-product, #sales-help, or just the team channel that absorbed the role — where product questions actually arrive, in volumes the wiki and the ticket queue never see. It’s where a seller asks whether the integration works behind a proxy, where marketing double-checks a claim the night before it ships to the website, where the new account manager asks the question that was answered, thoroughly, eleven scrolls up.
Ask the people who answer there how it feels, and you’ll hear the same thing: every individual reply is easy, and the aggregate eats the week. The fortieth ask isn’t harder than the first. It is exactly as easy, which is what makes it so hard to stop doing.
Channels forget by design
Chat is built for flow. A message earns attention for a day, gets resolved, and sinks — the design assumption is that whatever mattered was extracted in the moment. Knowledge needs the opposite: a stable home that accumulates. Teams routinely ask a chat channel to be both, and the channel always picks flow.
The usual patches fight the design and lose. Search fails not because the answer isn’t there but because it was phrased for one asker — your beautiful proxy explanation lives under whatever words that seller happened to use in March, and the next asker uses different ones. Pinned posts and channel FAQs are documents, so they inherit the documentation problemwith less structure and no owner at all. And the social fix — a culture of “search before asking” — taxes the asker to protect the expert, which is backwards for the team as a whole: you want questions surfaced, just not re-answered by hand.
An answerer that camps there
The shape we bet on: keep the channel exactly as it is, and change who answers first. A Deputy camps in the channel. When the fortieth ask lands, it answers in the thread the way it answered the first — from the briefing, quoting the line the answer came from, so the asker can see the source instead of taking a bot’s word for it.
Slack · WaterPro
The economics only work because of what happens on a miss. A question past the briefing gets a plain “this one needs the owner” and an escalation to you, marked pending — the loop we wrote up separately — and your one reply becomes the briefing line that answers every future phrasing of it. In a channel, that compounding is visible week over week: the asks keep arriving at the same rate, and the share that reaches you keeps shrinking.
/save, for the answer you just typed
You will still answer things yourself — sometimes faster than deciding whether to, and often precisely because the question was new. Those hand-typed answers are the most valuable text in the channel and historically the most doomed, sinking with everything else. So the reverse direction gets its own verb: hit /saveon an answer that’s gold, and Deputy drafts it into the briefing — reconciled against what’s already there, landing as a diff you approve.
Slack · WaterPro
Between the two directions, the channel’s role quietly inverts. It stays the place questions arrive, because nothing was ever going to change that. It stops being the place answers go to dissolve.
Why async is the point
A note on emphasis. Live surfaces get the demos — an AI that talks in a meeting is easy to be impressed by, and we build one. But the tonnage of the expertise tax is asynchronous: it arrives as text, between other tasks, and wants text back. It is also, overwhelmingly, the go-to-market side of the house doing the asking — salespeople, marketers, sales engineers trying to hold the product’s current story: what it’s for, what just shipped, what we say about it. You want those people asking. You just shouldn’t be the only place the answer lives. Answering it well preserves everyone’s flow at once — the asker gets an immediate, sourced reply; you get interrupted only by questions that are genuinely new; and the record improves under both of you as you work. The channel was already the front door of your product knowledge. This just staffs it.
The fortieth ask of the week, answered like the first — with the source attached.
Join the waitlistWe'll let you know the moment Deputy's open to you.
Or ask the live Deputy on the landing page