Explanation
Agents on tickets
On this page
When a channel has a Conclude app, the agents deployed to that channel also answer on the app’s tickets. No additional setup is needed in the app.
Supported ticket events
Agents in the app’s channel receive these ticket events:
- A new ticket. The agent reads the title and the description as the first message
- A comment or a file. For a file, the agent reads the comment’s text, not the file
- An email that arrives on a ticket through the app’s email integration
Each agent then answers according to its mode in the channel. An agent in Mention mode answers a new ticket only when the title or description @mentions it. An autonomous agent reads every new ticket and decides for itself.
Agents do not receive:
- a change to a field, the owner or the severity
- concluding or reopening a ticket
- a button click
- a comment on a closed ticket
- a comment from another app’s bot
- events caused by triggers, scripts or agents
Creating a ticket from a channel message does not notify agents again. They already received the original message, but they receive subsequent ticket comments.
In an app that gives every ticket its own channel, the agents of the app’s channel still answer on the ticket. A linked agent whose account is invited to the ticket’s channel answers its comments too.
What the agent reads
Before it comments, the agent gets:
- the app’s description, or the context text when the app has one
- its own instructions
- the ticket’s title, description, status, severity, owner, people, deadline and conclusion, and every custom field with a value
- the ticket’s history, with its comments, emails and changes such as a new owner
- data from your own systems, when the app has a lookup endpoint
- access to its knowledge collections and the channel’s approved learning summaries
What the agent sees in the Technical reference has the details.
What the agent does
The agent posts a comment on the ticket, under its own name. It can @mention the people on the ticket.
An agent can’t change a ticket. It doesn’t set fields, assign an owner or conclude the ticket. Use triggers and scripts for that.
Limits
- No loops. An agent never answers its own comment, another agent’s comment or a comment that a script posted
- Max comments. An agent stops replying when a ticket reaches this number of agent comments. The default is 20. Comments from all agents on the ticket count toward the limit. You set it on the agent’s Advanced tab
- Five answers a minute. Agents answer at most five times a minute on one ticket. Conclude discards responses above this limit
- Failures. When an agent that was addressed can’t answer, it posts “I could not respond to this ticket”, at most once an hour
Loop protection and rate limits in the Technical reference lists the rules.
Connected and private tickets
Agents also answer on tickets that Connected Apps shares with another channel. On a connected ticket and on a private ticket, they don’t search the channel’s learning summaries.