Hand product bugs to engineering
Connect
SPIRITT
Request TrackerRequest Tracker
Every queue, worked
SPIRITT works your Request Tracker queues end to end: finds tickets with TicketSQL, replies to requestors, adds internal comments, reassigns, reprioritizes and resolves, reading full history before it acts.
What you can do with Request Tracker.
Precise ticket search
TicketSQL across queues, plus user lookup for requestors and owners.
Replies and notes that land
Public correspondence and internal comments, with attachments and time logged.
Queues kept moving
Owner, priority, queue and status updated and verified by reading them back.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for your Request Tracker queues.
02
Connect Request Tracker
Add your RT API key, plus the tracker, inbox and chat tools your team uses.
03
Hand over the queue
Describe routing, priorities and replies. SPIRITT works tickets to resolution.
Hand over a mission.
Choose a mission. Make it yours.
Put Request Tracker to work.
Keep every queue moving
Questions
Request Tracker, with SPIRITT.
01Can SPIRITT reply to requestors?+
Yes. It sends public correspondence on a ticket, which RT delivers by email according to your configuration.
02Can it leave internal notes?+
Yes. It adds private comments with attachments and time spent, visible to staff only.
03How does it find tickets?+
With TicketSQL, the same query language your team uses, across every queue the account can see.
04Can it reassign and reprioritize?+
Yes. It updates owner, priority, queue, status and subject, then reads the ticket back to confirm.
05Does it read context before acting?+
Yes. It pulls ticket history, field changes, comments and attachment lists first.
06What does the connection need?+
A Request Tracker API key for a user with access to your queues. Other apps connect separately.