Use case
A mascot the whole team can be
Your product's community Slack answers questions at the speed of whoever happens to be online. Put one name on those answers and staff it from a room the community can't see.
Ines 11:03 AM
@Plumelight Team does the CLI read .env files or only flags?
↳ in thread
Plumelight Team APP 11:09 AM
Both, and .env wins when they disagree. I'll link the docs section here in a minute.
Whoever answers once gets tagged forever
Community members learn fast. The staffer who answered on a Tuesday becomes the address for every question after, across timezones, weekends, and job changes. When they move on, the questions keep addressing a person who no longer answers.
@Plumelight Team is an app, so it belongs to no one. Questions mentioning it land in your private ops channel inside the same workspace, and whoever picks up the thread answers as the team: same name, same avatar, any hour.
Behind the name
The ops channel holds staff and the volunteers you trust. Each question opens as a thread anyone can claim, and a // reply coordinates the claiming without leaving the room: "// mine, I wrote that CLI flag". The member asking sees none of the shift logistics, only an answer that reads like it came from one steady person.
New moderators start at full speed
A new hire's first weeks in a community are introductions to strangers who trusted the last avatar. Under the team name there is no first week. Their first answer carries the same weight as the founder's, because the name is the one that answered yesterday.
Running it
You own the community workspace, so create the app there from the manifest, invite it to #help and wherever else questions gather, and keep the ops channel private in the same workspace.
One thing to plan for: an active community talks a lot. Your plan's message pool is shared across every bot you run, so watch the first month's count on the dashboard before you add the bot to every channel.