fenbs for support teams: the bugs, on one board, with names on them
Support hears about every bug first. fenbs gives support a role that files and comments, engineering a role that fixes, and an AI assistant that dedupes and updates the customer.
Last checked
The problem it solves
Support knows about a bug on Monday. Engineering hears about it on Thursday, from a different person, worded differently, and files it again. The customer asks on Friday and nobody knows which of the two tickets is theirs. One board with roles ends that: support files the bug once with a report-and-comment role, it gets a number, engineering works it in the same place, and the number is what everyone quotes.
How it is set up
- One team board. Engineering has the roles that add, edit and move; support has a role that adds Bugs and comments.
- Support files every bug as a Bug with the customer’s words in the note. It gets a reference like BU-118.
- An AI assistant connected with a read-and-comment role checks each new bug against the board and comments “looks like BU-097” where it is a duplicate, signed with its name.
- When a bug moves to Completed, support sees it in the history and tells the customer, quoting the number.
Why roles matter here
Support should be able to file and comment without being able to move engineering’s work or rewrite a bug someone is fixing. A role that says exactly that is one sentence in fenbs, and a refusal explains itself, so nobody has to ask why a button is missing.
How to try it
Paste in the real list you are working from this week using Add many, add the one person who most often tells you about problems with a small role, connect the AI assistant you already use, and work from the board for a week. At the end ask one question: is the board still true? Your own board is free, so the trial costs nothing but the week.