Knowing when a case can actually be closed
Identify business objects (interventions, cases) whose planned lines all lie in the past, without closing a case that still has an expected follow-up.
Learn more →Use cases
Kohentra isn't defined by the list of its agents, but by the business situations it helps handle. Each case below describes a real problem, the observed context, and how Kohentra submits a proposal to a human decision.
Catching an inconsistency in the business graph
Notice when two business objects that should be linked (or should no longer be) fall out of a coherent relationship, without turning every discrepancy into an incident.
Learn more →What should have happened and didn't
Identify the absence of a normally expected business event (a follow-up, a renewal) rather than only ever looking at what actually happened.
Learn more →Billing that matches what actually happened
Spot delivered activity that hasn't been consistently billed yet, without flooding the queue with false positives on recurring or already-covered cases.
Learn more →Understanding business relations specific to your organization
Recognize business relations that don't exist in a standard schema - equipment attached to a thirdparty through a specific fleet-management module, for instance - without requiring custom development every time.
Learn more →Orchestration that knows which agent to call, and when
Decide which specialized capability to mobilize for a given situation, without re-triggering an already-resolved analysis or piling up redundant processing.
Learn more →