Internal tool
Multi-source orchestration agent for support triage
One orchestrator coordinating Jira, email and Salesforce cases into a single priority-ranked triage dashboard.
- Period
- Ongoing
- Role
- Built end to end
3
live sources in one view
1
priority-ranked list to work from
Context
Support work is spread across three places: tickets in Jira, requests arriving by email, and cases in Salesforce. Triage means checking all three, holding the overlap in your head, and deciding what to do first.
What I built
A single orchestrator LLM coordinating all three live sources. It tracks new and updated tickets, reads and prioritizes incoming mail, and flags whether a new case is routine or genuinely new.
The output is one priority-ranked dashboard, with a suggested reply and a short tip attached to each item.
Outcome
Triage stops being three separate sweeps and becomes one ordered list, which is where the time is saved and where items stop being missed.
This is a working internal tool rather than a product, and it is described here as one.
Stack
LLM orchestrationJira APIEmail integrationSalesforce CasesAgentic tooling
Want the parts I can't put on a public page?
Happy to walk through the data model, the trade-offs, and what I would do differently. Open to Salesforce roles, 30-day notice.