Is a Slack feedback channel an FDE to product loop?

THE SHORT ANSWER

No. It is an inbox, and a good one. Jayesh Govindarajan, who runs the roughly 700-person org behind Agentforce, told Aakash Gupta that forward-deployed engineers post field feedback into one Slack channel tagged paper cut or feature request, and PMs match posts to the roadmap and ask whether a customer-specific fix should become general. The same day Salesforce reported that 50% of Slack messages now come from apps and agents, so the channel fills from both sides. What a channel does not carry is a count of other customers with the same problem, a date product owes an answer, and a written decision back. The loop is the handback packet: the delta in configuration terms, the customer's eval rows, the reversals, and the count, delivered two weeks in, at go-live, and at day 60, with product owing a written decision within two weeks, generalize, keep as configuration, or kill, from a named person, plus the eval the general version has to pass. The metric that tells the two apart is generalization rate: packets with a decision in two weeks, and three-customer patterns that shipped. A channel cannot produce it.

No. A channel with two tags is an inbox, and the agents will post into it too now that half of Slack's messages come from apps and agents. The loop is a packet with a count, three dates, and a decision back with a name on it, measured by generalization rate.

The six steps, the Slack numbers, and the packet are in Salesforce's AI Org Routes Field Feedback Through One Slack Channel. Kill the Channel as the Loop.. The packet itself is from Absorb Pain, Excrete Product: The FDE Handback, and the metric from The FDE Scorecard: Count What Stayed, Not Who Was Sent.

SOURCES

THE LONG VERSION

RELATED ANSWERS

Last reviewed 2026-11-04 · 1 min read