Use case
One support name for every customer channel
You gave each customer a Slack channel because deals move faster there. Now every engineer in those channels is support staff. Put one name in front of the team instead.
Priya 9:12 AM
@Acme Support the CSV export times out past 50k rows. Same on your side?
↳ in thread
Acme Support APP 9:15 AM
Reproduced, thanks for the row count. The fix is in review; I'll post here when it ships.
Customers ask the person they met
A customer channel starts tidy. Then the customer learns names. They mention the engineer who ran the demo, the founder who closed them, the designer who answered at midnight once. Those people become the support team without agreeing to be, and the answer arrives whenever their calendar allows.
A BotFerry bot gives the channel one name that means "the company". Customers mention @Acme Support, the mention lands in a private channel your team owns, and whoever is on shift replies from there. The answer posts back into the customer's thread as Acme Support, under the app's avatar.
What the customer sees
Their own channel, their own thread, an answer from your product's name. There is no individual to bookmark, so the next question goes to the same place instead of the same person. To follow up, they mention the app again inside the thread, and the follow-up joins the conversation your team already has open.
What your team sees
One private channel, say #support-desk, collects every customer channel you invite the bot into. Each conversation opens as its own thread, with the requester's name, the source channel, and a link to the original message. Replies typed in the thread go out. Anything at the top level of the channel stays put, so the same channel doubles as your coordination space.
- Start a reply with
//and it stays internal. "//checking with billing" reads as a note to your shift, never a message to the customer. - Screenshots travel both ways. The customer's stack trace arrives in your thread, and the annotated fix you attach lands back in theirs.
- A reply that fails to deliver, say the customer archived their channel, posts a warning in your thread with the reason instead of vanishing.
Onboarding a customer takes one invite
Create the Slack app from the manifest BotFerry generates and name it what customers should read: Acme Support. Invite it to each customer channel and pick the private channel where your team works. From then on, a new customer costs one /invite. Mention the bot in a channel it hasn't joined and Slack offers to invite it on the spot.
Customer channels never see each other. A mention in one is invisible in the rest; only your desk sees them side by side.