Loading…
Loading…
Support is where agents earn their keep and where a bad automated reply costs the most. FlozentAi lets the agent read the ticket, search your knowledge, and prepare the response — then stops, showing the exact text a human is approving before it goes to the customer.
| Definition | Import the Zendesk Support API specification for tickets, users and help-centre articles. |
|---|---|
| Credential | API token, or OAuth 2.0 for multi-account installs. |
| Stored as | A secret:// reference to your own vault. FlozentAi never holds the value. |
Action names are yours to choose during review — these are the shapes most teams end up with. Anything that writes is confirmation-gated unless you deliberately publish it otherwise.
| Action | Kind | What it does |
|---|---|---|
ticket.get | Read | Read a ticket with its comment history. |
ticket.search | Read | Find similar past tickets. |
ticket.comment | Write | Post a public or internal reply. |
ticket.update | Write | Change priority, assignee or status. |
There is no field in the console that accepts a token or a password. You store the secret in your vault and give FlozentAi a reference; the runtime resolves it inside the execution layer, after the policy decision.
Only if you publish the comment action without requiring confirmation. The default for any write is that it pauses, and the approval is bound to the exact proposal — editing the draft invalidates it.
Every run records the identity, the context it read, the policy decision, the provider request and the result. That trace is the record you show when someone asks why a ticket was closed.
Draft support replies from live system data and keep a human on the send button. Approval-gated AI for support teams.
Read more ProductShip an AI assistant inside your own SaaS product, scoped per customer, without building the governance layer yourself.
Read moreImport the specification, review what it found, and publish only what you want reachable.