Use case
A feedback box that answers back
Feature requests surface mid-conversation: a sales debrief, a support thread, a rant in #general. Give people a name to tag the moment it happens, and reply when it ships.
Tomás 4:47 PM
@Feedback Meridian signed 🎉 but they asked twice for SSO on the starter plan.
↳ in thread
Feedback APP 4:52 PM
Logged. Third SSO ask this quarter; it goes in front of Monday's roadmap meeting.
Feedback happens mid-conversation
Nobody leaves a deal-closing thread to fill in a form. The request gets a 👍, scrolls up, and is gone by Thursday. A @Feedback mention costs the writer three seconds and keeps the context: the message, the thread around it, the screenshot they attached.
Every mention lands in your product team's private channel as its own thread, with a link back to where it was said. Triage happens there: weigh it, mark it a duplicate, or answer on the spot.
The reply is what builds the habit
A form never says anything back. Here the requester gets an answer in their own thread, from @Feedback itself: "on the roadmap", "works today, here's how", or "no, and here's why". Their colleagues watch the exchange happen in the channel, and one person's habit becomes the team's.
BotFerry keeps each conversation's routing for the life of the bot, so a thread can sit quiet for six weeks and still receive "this shipped in 4.2 today". Closing the loop months later is the point.
Triage without an audience
The public side sees the ask and the answer. The channel where you weigh requests stays private, and replies starting with // never leave it: "// duplicate of the March ask", "// this contradicts what enterprise wants". You can be candid about a request without publishing the deliberation.
Where to put it
Invite the bot to the channels where opinions already show up: sales wins, customer-call notes, #general. Skip the channels where nobody talks about the product. When a mention arrives from somewhere you didn't expect, you've learned where feedback lives.