Turn a finding
into a next step.
Cases bring together what Ginsi found, what your team knows and what happened next. Each reading can build on the last.
Know what deserves a closer look.
Ginsi brings related observations into a Case: what changed, why it matters and the evidence behind it. Your team gets a question to act on, with a basis you can inspect.
Does support need
more capacity?
Shared with account members
- First reply
- Earlier: 5.1 hLater: 8.9 h
- Satisfaction
- Earlier: 4.2Later: 3.7
Slower replies. Lower satisfaction. The cause is still open.
Your context can change the picture.
The numbers are part of the story. Bring in what changed in the business, and Ginsi can consider that context alongside the evidence. The first explanation stays open to revision.
“We changed how enterprise tickets are assigned.”
More capacity, a different handover — or both?
A new explanation to examine alongside the original finding.
Ginsi learns from what happens next.
Your team records how an action worked out. Ginsi carries earlier Cases and recorded outcomes into later analysis, so the next reading builds on your company’s experience.
Support handover reviewed with the team.
Your team’s assessment Partly helpful
This outcome becomes context for the next analysis.
A team-reported outcome, carried forward as context.
Illustrative product sequence · sample data
Explore the homepage Case illustrationThe anatomy of a Case.
The finding and its supporting record have different jobs. Keeping them distinct makes it possible to reconsider an explanation without losing the basis for the original question.
Finding
The reading has a title, status and source-bundle reference. Its interpretation can be examined against the evidence that produced it.
Evidence
The source bundle establishes the permitted inputs and available coverage. Missing evidence and suppressed groups remain limits on the finding.
Added context
Company events and recorded context can change how the evidence should be read. A human explanation and an observed measurement are not interchangeable.
Status & later evidence
Case outcome records distinguish an open issue from one that has faded, been resolved, dismissed or superseded. A recurrence can matter in a later review. These records describe the Case’s development; they do not establish what caused it.
Sharing is an access decision.
| Action | Effect | What stays separate |
|---|---|---|
| Pin a Case | Editors can lift a Case into the company’s shared pinned view. | A pin changes prominence, not access. Each reader still needs permission to see the Case. |
| Share a company Case | An owner or administrator can share a company Case with all accepted account members. Sharing adds a company pin and an in-app notification; email follows each member’s preferences. | This is an explicit access change, not a side effect of ordinary pinning. Cases bound to a named Workroom keep that Workroom’s boundary. |
| Inspect a source | Resolve the evidence through the source’s permitted reader. | Case access does not grant raw-data or source access. |
| Read after a change | Current authorization and privacy state govern the response. | An old link or an earlier view is not continuing authority. |
Keep the question open.
Keep the reasoning available.
The value of a Case is continuity: the next review can begin with the evidence and context already gathered. Later improvement is another observation to examine, not proof that the earlier decision worked.
Context that survives the meeting.
Add what the measurements cannot tell you.
A team may know that a handover changed or that the reporting period included an unusual mix of support work. Record that company context so the next reading can consider it. A proposed explanation should remain distinguishable from a measured observation.
Return to what remains unresolved.
In the illustration, reviewing routing is a human choice about where to investigate. A later review can ask whether the support pattern persists, whether another explanation is stronger and whether the Case should remain open. Recording a resolved or recurring issue gives future analysis useful context.
A shared question still has an audience.
Company membership, role and the Case’s current audience govern who can see it. Source access is checked separately. Case readers recheck authorization after privileged content reads, so a previously opened link cannot stand in for current permission.
