Home/Mindbreeze/Use cases/Support Case
Use cases · Customer supportSupport Case: every ticket prepared before the agent opens it
A new ticket says little more than “it does not work”. Support Case prepares and enriches it: a summary, similar earlier cases with their solution, the relevant documentation and the customer context, each with its source.
Discuss this use case All use cases
Illustrative example
In short
Support Case is a Mindbreeze agent that prepares and enriches incoming support cases. For each new case it adds a short summary, similar earlier cases and how they were solved, the relevant product documentation and the customer context, each linked to its source. The support agent checks the suggestions, solves the case and records the solution as usual. SoftAdvice connects Support Case to your ticket system, documentation and CRM and sets it up with your support team.
Most time goes into understanding the case, not solving it
Before a support agent can help, they search the ticket history, the knowledge base, product documentation and the CRM. Often the same problem was solved before by someone else, but nobody finds that case in time.
- Ticket history and solutions
- Knowledge base and product documentation
- Release notes and known issues
- Customer and contract data in the CRM
From new ticket to solved case
The agent prepares; the support agent solves and decides what to tell the customer.
Ticket arrives
A customer reports a problem through the usual channel.
Prepare and enrich
Support Case adds a summary, similar cases, documentation and customer context, with sources.
Solve
The support agent checks the suggestions, solves the case and answers the customer.
Record
The solution is recorded in the ticket system, so the next similar case finds it.
A person decides, the sources stay visible
The agent prepares; a person checks and decides. Every answer links to the documents it used, so anyone can see later what it was based on.
Mindbreeze applies the permissions of each source system: what someone cannot open in the source, they do not see in the answer. If access in a source is too broad today, that is fixed in the source; we check it before the start.
- Answers support, people decide
- Permissions of each source respected
- Sources linked in every answer
- Access checked before the start
What we measure on a first use case
We agree the baseline with your team before the start, so the result is measured on your own questions.
Handling time
Time per case for an agreed type of ticket, before and after.
Useful suggestions
Agents rate whether the similar cases and documents helped.
Escalations
How often cases still go to second line for known problems.
Permission tests
Test users confirm that nobody sees what they may not open.
What this use case needs, and what it does not do
Suggestions are only as good as the ticket history and documentation. Before the start we agree which ticket types are in scope, which systems are connected and how solutions are recorded. Support Case prepares the case; it does not answer customers by itself.
These pages describe how a Mindbreeze agent can be set up for this task. They are not customer references: we describe them without names or figures, and the example answers are illustrative.
- Ticket types in scope agreed
- Connectors confirmed per system
- No automatic replies to customers
- Solutions recorded as usual
Questions about this use case
What is Support Case?
Support Case is one of the pre-built agentic use cases (Insight Touchpoints) in Mindbreeze Insight Workplace. SoftAdvice connects it to your sources, sets it up for your rules and team, and measures the result with you.
Does it replace our ticket system?
No. The ticket system stays the place where cases are handled. Support Case adds the preparation; which ticket systems can be connected is confirmed before the start.
Do we need to move our documents?
No. The documents stay in the systems where they are today. Mindbreeze connects to them; which systems can be connected is confirmed per system before the start.
How do we start?
With a conversation about one use case: the team, the typical questions and the systems involved. From there we propose a scoped first step.
Would this help your team?
Tell us about the team, the questions and the systems involved. We come back with a proposal for a scoped first step.