Request Tracker (RT), worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Request Tracker (RT) account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Customer Support
- Connects with a key
- 11 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Request Tracker (RT) is
Request Tracker is a ticketing and workflow platform for managing support requests, queues, users, assets, knowledge articles, and related operations.
You paste in a key from your own Request Tracker (RT) account. It is kept encrypted, and you can withdraw it from inside Request Tracker (RT) whenever you like.
One message in, the work done in Request Tracker (RT).
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Request Tracker (RT). You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Request Tracker (RT) account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in Request Tracker (RT)
These are the ready-made tools your AI employee already has in Request Tracker (RT). It is not limited to them, but it never has to be taught these.
- Add Ticket CommentAdd a private internal comment to an RT ticket. The comment creates a durable transaction that REST2 cannot remove; RT scrips may still notify staff.
- Create TicketCreate a durable RT ticket in a queue. Creation may run RT scrips or send notifications and cannot be fully erased through REST2.
- Get QueueRetrieve one visible RT queue by id or exact name, including lifecycle and capability-sensitive links.
- Get TicketRetrieve one visible RT ticket, including its current fields and capability-sensitive links for allowed follow-up operations.
- Get Ticket HistoryReturn one page of detailed ticket history, including transaction types, field changes, comments, creators, and timestamps.
- List QueuesList queues visible to the connected RT user so an agent can select a queue for ticket search or creation. Returns one bounded page.
- List Ticket AttachmentsList attachment metadata references associated with a visible RT ticket without downloading attachment content.
- Reply to TicketSend public correspondence on an RT ticket. This can email requestors or other recipients according to RT configuration and creates a durable transaction that REST2 cannot remove.
- Search TicketsSearch visible RT tickets with an explicit TicketSQL expression and return one bounded page. Use a condition such as id 0 when listing tickets; an omitted search does not list all
- Search UsersSearch RT users with structured field conditions and return one bounded page of user references or selected fields for requester and owner lookup.
- Update TicketUpdate selected metadata on an existing RT ticket and verify every requested field by reading it back. Omitted fields are unchanged.
You stay the boss of your Request Tracker (RT) account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own Request Tracker (RT) account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in Request Tracker (RT) is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Request Tracker (RT) and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about Request Tracker (RT)
- Can an AI employee really work inside Request Tracker (RT)?
- Yes. It signs in to your own Request Tracker (RT) account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of Request Tracker (RT)?
- No. Nothing moves and nothing is replaced. Your records stay in Request Tracker (RT), your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my Request Tracker (RT) account?
- You paste in a key from your own Request Tracker (RT) account. It is kept encrypted, and you can withdraw it from inside Request Tracker (RT) whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in Request Tracker (RT)?
- It has 11 ready-made tools in Request Tracker (RT) today, among them Add Ticket Comment, Create Ticket and Get Queue. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Request Tracker (RT) and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in Request Tracker (RT) and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in Request Tracker (RT)?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Request Tracker (RT) is written down with what it did and when.