What's new ·
Custom closing wrap-up
Every company creates its own list of closing reasons, with a default outcome for each and scope by channel or department.
By Lucas Marchon, Founder at BrainChat
Every company talks differently: "sale completed", "quote sent", "customer ghosted". A fixed list of reasons worked for no one, and an open list made comparing dashboards impossible. Custom wrap-up solves both.
How it works
- The list belongs to the organization. Choose between standard and custom modes, and create reasons using the names your team uses.
- Each reason has a mandatory default outcome: Resolved, No response, Canceled, or Spam. This is what dashboards use for comparison.
- Optional scope: limit a reason to specific channels or departments. The Sales team won't see Support reasons.
- Who edits: anyone with support editing permissions. All members can read the list.
History remains unchanged
When closing, the conversation saves the reason, the outcome, and the name of the reason at that moment. Renaming a reason later does not rewrite past support sessions.
Where wrap-up appears
- When closing via the conversation, the list menu, or by dragging to Closed on the Kanban.
- In supervisor dashboards, grouped by default outcome.
Complements
- Conversation Kanban: dropping the card into Closed prompts for the wrap-up.
- Supervisor dashboard, satisfaction survey, and automatic distribution: where outcomes are compared.