SupportAgent. Resolves tickets with the whole company in context.
Every task it ships with, by app.
These are real entries from the OwnAgents task catalog — each one a verified, replayable operation against the app’s API, with permissions scoped by OwnCentral and every execution written to the audit log.
Where it works across the stack.
Because every app shares one control plane and one event bus, SupportAgent composes multi-app workflows no siloed tool could attempt:
What it takes on beyond the registry.
The registry is the floor, not the ceiling. Working through OwnIQ with the full context of the connected stack, SupportAgent also handles:
- ▸Triage and prioritise every inbound ticket by SLA and severity
- ▸Draft context-aware replies with the account history attached
- ▸Detect at-risk accounts from ticket sentiment and frequency
- ▸Escalate to the right owner with a complete context bundle
- ▸Keep CSAT and SLA dashboards honest — no manual tagging
- ▸Turn resolved tickets into knowledge-base drafts
Scoped permissions
SupportAgent runs under the same RBAC model as human users — field-level permissions and scope boundaries enforced by OwnCentral at runtime.
Reasoning via OwnIQ
Every model call routes through the sovereign gateway: metered, redacted, and attributable. Prompts never leave your perimeter.
Audited & reversible
Every action lands in the tamper-evident log with full attribution. Hard business rules cannot be overridden by the model.
See SupportAgent on your data.
More agents: DealAgent · SpendAgent · HireAgent