Department · Service & Support · schema_pack: 6 types
The customer shouldn't have to repeat themselves. The agent should remember.
Exceptions, cases, and escalations with source and inherited permission: the customer doesn't repeat the case and the agent answers by the current version.
Scenario
How context circulates when ValorBrain is in the flow.
- 01
The support agent asks about the case and receives the decisions and exceptions already granted to that account, like the extended refund deadline on ticket #8812, with source, who approved it, and how long it holds.
- 02
Permissions are inherited from whoever uses the agent: it sees only what that person can see.
- 03
The answer cites the source of the precedent instead of reconstructing the case from memory.
- 04
A new ticket retrieves the resolutions of similar cases, with the outcome of each.
- 05
What the team learned stays on record as a learning, with the originating case cited.
- 06
The agent makes a proposal with precedent in hand, not a guess.
- 07
The case escalates to the supervisor with context ready: history, exceptions in force, and sources.
- 08
The customer doesn't repeat the story to the second person.
- 09
Whatever the supervisor corrects becomes a recorded lesson for the team's and the agents' next sessions.
Schema pack
Unit types that give structure to what's worth remembering in this area. Every record carries source, owner, version and validity.
schema_pack:types: - customer - case - escalation - policy_exception - resolution - learningNext step
Less starting over. More continuity
Bring a real project. In one conversation we map where context gets lost between the people and agents on your team, and where to start.