Add modular support for triage pipeline and documentation#19
Open
Mayank2142 wants to merge 3 commits into
Open
Add modular support for triage pipeline and documentation#19Mayank2142 wants to merge 3 commits into
Mayank2142 wants to merge 3 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HackerRank Orchestrate: Multi-Domain Support Triage Agent 🤖
Welcome to the Multi-Domain Support Triage Agent, built for the HackerRank Orchestrate 24-Hour Hackathon. This agent is a highly modular, intelligent support triage system designed to process user support tickets across multiple platforms (HackerRank, Claude, Visa), classify them, retrieve context from a domain-specific corpus, and make autonomous decisions to either auto-reply or safely escalate.
✨ Key Features
📁 System Architecture
The data processing pipeline is orchestrated through the following components:
classifier.py: Categorizes incoming tickets (e.g.,bug,product_issue,invalid) and extracts targeted product areas.retrieval.py: Searches the domain-specific data corpus to fetch grounded evidence for the user query.decision.py: Determines whether a ticket can be confidently auto-replied or if it must be escalated to a human agent based on strict risk evaluation.generator.py: Crafts professional, empathetic, and evidence-grounded natural language responses.pipeline.py: Orchestrates the full lifecycle of a ticket from ingestion to the final output CSV.🚀 Setup
Ensure you have your environment variables set (e.g.,
OPENAI_API_KEYorANTHROPIC_API_KEY) using a.envfile or exported directly. Then, install the required dependencies:🛠 Run the Agent
To execute the triage agent on the full support tickets dataset, use the following command:
cd code/ python main.py \ --tickets ../support_tickets/support_tickets.csv \ --data ../data/ \ --output ../support_tickets/output.csv \ --log ../run_log.txt🧪 Validation & Testing
To run the agent on the smaller sample dataset for quick testing and validation:
cd code/ python main.py \ --tickets ../support_tickets/sample_support_tickets.csv \ --data ../data/ \ --output ../support_tickets/sample_output.csv \ --log ../run_log.txt📊 Output Format
The output is written to a CSV file containing the following strictly formatted columns:
status, product_area, response, justification, request_typerepliedorescalatedscreen,fraud,api_integration)product_issue,feature_request,bug, orinvalid