feat: Add intelligent auto-router and enhanced integrations
- Add intelligent-router.sh hook for automatic agent routing - Add AUTO-TRIGGER-SUMMARY.md documentation - Add FINAL-INTEGRATION-SUMMARY.md documentation - Complete Prometheus integration (6 commands + 4 tools) - Complete Dexto integration (12 commands + 5 tools) - Enhanced Ralph with access to all agents - Fix /clawd command (removed disable-model-invocation) - Update hooks.json to v5 with intelligent routing - 291 total skills now available - All 21 commands with automatic routing 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
admin
337
dexto/agents/triage-demo/README.md
Normal file
337
dexto/agents/triage-demo/README.md
Normal file
@@ -0,0 +1,337 @@
|
||||
# TeamFlow Customer Support Triage Agent System
|
||||
|
||||
This demonstration showcases an intelligent **Customer Support Triage System** built with Dexto agents for **TeamFlow**, a cloud-based project management and team collaboration platform. The system automatically analyzes customer inquiries, routes them to specialized support agents, and provides complete customer support responses.
|
||||
|
||||
## 🏢 About TeamFlow (Demo Business Context)
|
||||
|
||||
TeamFlow is a fictional cloud-based project management platform used for this demonstration. It offers three service tiers:
|
||||
|
||||
- **Basic Plan ($9/user/month)**: Up to 10 team members, 5GB storage, basic features
|
||||
- **Pro Plan ($19/user/month)**: Up to 100 team members, 100GB storage, advanced integrations (Slack, GitHub, Salesforce)
|
||||
- **Enterprise Plan ($39/user/month)**: Unlimited users, 1TB storage, SSO, dedicated support
|
||||
|
||||
Key features include project management, team collaboration, time tracking, mobile apps, and a comprehensive API. The platform integrates with popular tools like Slack, GitHub, Salesforce, and Google Workspace.
|
||||
|
||||
This realistic business context allows the agents to provide specific, accurate responses about pricing, features, technical specifications, and policies using the FileContributor system to access comprehensive documentation.
|
||||
|
||||
## 🏗️ Architecture Overview
|
||||
|
||||
```
|
||||
Customer Request
|
||||
↓
|
||||
Triage Agent (Main Coordinator)
|
||||
↓
|
||||
[Analyzes, Routes & Executes via MCP]
|
||||
↓
|
||||
┌─────────────────────────────────────────┐
|
||||
│ Technical Support │ Billing Agent │
|
||||
│ Agent │ │
|
||||
├─────────────────────┼──────────────────┤
|
||||
│ Product Info │ Escalation │
|
||||
│ Agent │ Agent │
|
||||
└─────────────────────────────────────────┘
|
||||
↓
|
||||
Complete Customer Response
|
||||
```
|
||||
|
||||
The triage agent doesn't just route requests - it **executes the specialized agents as MCP servers** and provides complete, integrated customer support responses that combine routing intelligence with expert answers.
|
||||
|
||||
## 🤖 Agent Roles
|
||||
|
||||
### 1. **Triage Agent** (`triage-agent.yml`)
|
||||
- **Primary Role**: Intelligent routing coordinator AND customer response provider
|
||||
- **Capabilities**:
|
||||
- Analyzes requests and categorizes issues
|
||||
- Routes to specialists via `chat_with_agent` tool calls
|
||||
- **Executes specialist agents directly through MCP connections**
|
||||
- **Provides complete customer responses** combining routing + specialist answers
|
||||
- **Tools**: Filesystem, web research, **chat_with_agent** (connects to all specialists)
|
||||
- **Tool Confirmation**: Auto-approve mode for seamless delegation
|
||||
|
||||
### 2. **Technical Support Agent** (`technical-support-agent.yml`)
|
||||
- **Specialization**: Bug fixes, troubleshooting, system issues
|
||||
- **Tools**: Filesystem, terminal, browser automation
|
||||
- **Model**: GPT-5 (higher capability for complex technical issues)
|
||||
- **Connection**: Available as MCP server via stdio
|
||||
|
||||
### 3. **Billing Agent** (`billing-agent.yml`)
|
||||
- **Specialization**: Payments, subscriptions, financial inquiries
|
||||
- **Tools**: Browser automation, filesystem for policy docs
|
||||
- **Model**: GPT-5 Mini (efficient for structured billing processes)
|
||||
- **Connection**: Available as MCP server via stdio
|
||||
|
||||
### 4. **Product Info Agent** (`product-info-agent.yml`)
|
||||
- **Specialization**: Features, comparisons, documentation
|
||||
- **Tools**: Web research (Tavily), filesystem, browser automation
|
||||
- **Model**: GPT-5 Mini (efficient for information retrieval)
|
||||
- **Connection**: Available as MCP server via stdio
|
||||
|
||||
### 5. **Escalation Agent** (`escalation-agent.yml`)
|
||||
- **Specialization**: Complex issues, Enterprise customers, management approval
|
||||
- **Tools**: Filesystem, web research for compliance/legal info
|
||||
- **Model**: GPT-5 (higher capability for sensitive issues)
|
||||
- **Connection**: Available as MCP server via stdio
|
||||
|
||||
## 📚 Business Context Documentation
|
||||
|
||||
Each agent has access to relevant TeamFlow documentation via the FileContributor system:
|
||||
|
||||
### Documentation Files (`docs/` folder)
|
||||
- **`company-overview.md`**: General company information, plans, SLAs, contact info
|
||||
- **`technical-documentation.md`**: API docs, system requirements, troubleshooting guides
|
||||
- **`billing-policies.md`**: Pricing, refund policies, billing procedures, payment methods
|
||||
- **`product-features.md`**: Feature descriptions, plan comparisons, integrations
|
||||
- **`escalation-policies.md`**: Escalation procedures, contact information, incident templates
|
||||
|
||||
### Agent-Specific Context
|
||||
- **Technical Support**: Company overview + technical documentation
|
||||
- **Billing Agent**: Company overview + billing policies
|
||||
- **Product Info**: Company overview + product features
|
||||
- **Escalation**: Company overview + escalation policies
|
||||
- **Triage Agent**: Company overview for routing context
|
||||
|
||||
## 🚀 Getting Started
|
||||
|
||||
### Quick Start - Integrated Triage System
|
||||
|
||||
The **recommended way** to run the triage system is using the main triage agent, which automatically connects to all specialists:
|
||||
|
||||
```bash
|
||||
# Run the complete triage system (connects to all specialist agents automatically)
|
||||
npx dexto --agent agents/triage-demo/triage-agent.yml
|
||||
|
||||
# Test with a customer inquiry
|
||||
npx dexto --agent agents/triage-demo/triage-agent.yml "I want to upgrade from Basic to Pro but confused about pricing"
|
||||
```
|
||||
|
||||
This will:
|
||||
1. **Auto-connect** to all 4 specialist agents as MCP servers
|
||||
2. **Analyze** your request and route to the appropriate specialist
|
||||
3. **Execute** the specialist agent to get the expert answer
|
||||
4. **Respond** with a complete customer support response
|
||||
|
||||
### Running Individual Agents (Advanced)
|
||||
|
||||
For testing individual specialist agents:
|
||||
|
||||
```bash
|
||||
# Run specialized agents individually
|
||||
npx dexto --agent agents/triage-demo/technical-support-agent.yml
|
||||
npx dexto --agent agents/triage-demo/billing-agent.yml
|
||||
npx dexto --agent agents/triage-demo/product-info-agent.yml
|
||||
npx dexto --agent agents/triage-demo/escalation-agent.yml
|
||||
```
|
||||
|
||||
### Environment Setup
|
||||
|
||||
Ensure you have the required API keys in your `.env` file:
|
||||
|
||||
```env
|
||||
OPENAI_API_KEY=your_openai_api_key
|
||||
TAVILY_API_KEY=your_tavily_api_key # For web research
|
||||
```
|
||||
|
||||
## 📋 Example Scenarios
|
||||
|
||||
### Scenario 1: Technical Issue
|
||||
**Customer Input**: *"My app keeps crashing when I try to upload files. Getting error code 500."*
|
||||
|
||||
**Triage Agent Response**:
|
||||
- **Analysis**: Technical Issue → Route to Technical Support Agent
|
||||
- **Execution**: Calls `chat_with_agent` → Technical Support provides debugging steps
|
||||
- **Customer Response**: *"I've routed your issue to our Technical Support team. Here's how to resolve the 500 error when uploading files: [detailed technical troubleshooting steps from specialist]"*
|
||||
|
||||
### Scenario 2: Billing Question
|
||||
**Customer Input**: *"I want to upgrade from Basic to Pro but confused about pricing. Will I be charged the full amount?"*
|
||||
|
||||
**Triage Agent Response**:
|
||||
- **Analysis**: Billing Question → Route to Billing Agent
|
||||
- **Execution**: Calls `chat_with_agent` → Billing Agent explains prorated pricing
|
||||
- **Customer Response**: *"I've routed your inquiry to our Billing team. When upgrading from Basic to Pro, you'll only be charged a prorated amount for the remaining billing period - just the difference between plans for the time left in your cycle. The upgrade takes effect immediately."*
|
||||
|
||||
### Scenario 3: Product Information
|
||||
**Customer Input**: *"What's the difference between your Pro and Enterprise plans? I need API access."*
|
||||
|
||||
**Triage Agent Response**:
|
||||
- **Analysis**: Product Inquiry → Route to Product Info Agent
|
||||
- **Execution**: Calls `chat_with_agent` → Product Info Agent provides detailed comparison
|
||||
- **Customer Response**: *"I've connected you with our Product team. Both Pro and Enterprise plans include full API access. The main differences are: Pro supports up to 100 users with 100GB storage, while Enterprise offers unlimited users, 1TB storage, SSO, and dedicated support. [detailed feature comparison]"*
|
||||
|
||||
### Scenario 4: Escalation Required
|
||||
**Customer Input**: *"This is my third time contacting support about data privacy concerns. I'm considering legal action."*
|
||||
|
||||
**Triage Agent Response**:
|
||||
- **Analysis**: Legal/Compliance Issue → Route to Escalation Agent
|
||||
- **Execution**: Calls `chat_with_agent` → Escalation Agent provides management contact
|
||||
- **Customer Response**: *"I've escalated your data privacy concerns to our senior support team. Given the legal implications, I'm connecting you directly with our compliance manager Sarah Johnson (sarah.johnson@teamflow.com). She'll address your concerns within 2 hours."*
|
||||
|
||||
## 🔧 Advanced Configuration
|
||||
|
||||
### Current MCP Server Configuration (Automatic)
|
||||
|
||||
The triage agent automatically connects to specialists via stdio MCP servers:
|
||||
|
||||
```yaml
|
||||
# Current configuration in triage-agent.yml
|
||||
mcpServers:
|
||||
technical_support:
|
||||
type: stdio
|
||||
command: npx
|
||||
args: [dexto, --mode, mcp, --agent, agents/triage-demo/technical-support-agent.yml]
|
||||
|
||||
billing_support:
|
||||
type: stdio
|
||||
command: npx
|
||||
args: [dexto, --mode, mcp, --agent, agents/triage-demo/billing-agent.yml]
|
||||
|
||||
# Similar configuration for product_info and escalation agents...
|
||||
```
|
||||
|
||||
### Production Configuration (Distributed Servers)
|
||||
|
||||
For production deployment, you would run each specialist as a separate server:
|
||||
|
||||
```yaml
|
||||
# triage-agent.yml - Production Configuration
|
||||
mcpServers:
|
||||
technical_support:
|
||||
type: sse
|
||||
url: "http://localhost:3001/mcp"
|
||||
headers:
|
||||
Authorization: "Bearer your-auth-token"
|
||||
|
||||
billing_support:
|
||||
type: sse
|
||||
url: "http://localhost:3002/mcp"
|
||||
headers:
|
||||
Authorization: "Bearer your-auth-token"
|
||||
|
||||
product_info:
|
||||
type: sse
|
||||
url: "http://localhost:3003/mcp"
|
||||
headers:
|
||||
Authorization: "Bearer your-auth-token"
|
||||
|
||||
escalation:
|
||||
type: sse
|
||||
url: "http://localhost:3004/mcp"
|
||||
headers:
|
||||
Authorization: "Bearer your-auth-token"
|
||||
```
|
||||
|
||||
### Running Distributed Servers
|
||||
|
||||
```bash
|
||||
# Terminal 1: Technical Support Server
|
||||
npx dexto --agent agents/triage-demo/technical-support-agent.yml --mode server --port 3001
|
||||
|
||||
# Terminal 2: Billing Support Server
|
||||
npx dexto --agent agents/triage-demo/billing-agent.yml --mode server --port 3002
|
||||
|
||||
# Terminal 3: Product Info Server
|
||||
npx dexto --agent agents/triage-demo/product-info-agent.yml --mode server --port 3003
|
||||
|
||||
# Terminal 4: Escalation Server
|
||||
npx dexto --agent agents/triage-demo/escalation-agent.yml --mode server --port 3004
|
||||
|
||||
# Terminal 5: Main Triage Coordinator
|
||||
npx dexto --agent agents/triage-demo/triage-agent.yml --mode server --port 3000
|
||||
```
|
||||
|
||||
## 🎯 Key Features Demonstrated
|
||||
|
||||
### 1. **Intelligent Routing with Execution**
|
||||
- Natural language analysis to determine issue category
|
||||
- **Automatic execution** of specialist agents via MCP
|
||||
- **Complete customer responses** combining routing + expert answers
|
||||
- Seamless tool confirmation with auto-approve mode
|
||||
|
||||
### 2. **Specialized Expertise Integration**
|
||||
- Each agent has domain-specific knowledge and tools
|
||||
- **Real-time coordination** between triage and specialists
|
||||
- **Unified customer experience** despite multi-agent backend
|
||||
|
||||
### 3. **Scalable MCP Architecture**
|
||||
- **Stdio connections** for local development and testing
|
||||
- **SSE connections** for distributed production deployment
|
||||
- **Tool-based delegation** using `chat_with_agent`
|
||||
|
||||
### 4. **Comprehensive Tool Access**
|
||||
- Filesystem access for documentation and logging
|
||||
- Web research capabilities for up-to-date information
|
||||
- Browser automation for testing and demonstrations
|
||||
- **Agent-to-agent communication** via MCP tools
|
||||
|
||||
## 🔍 Testing the System
|
||||
|
||||
### Interactive Testing
|
||||
|
||||
1. **Start the complete triage system**:
|
||||
```bash
|
||||
npx dexto --agent agents/triage-demo/triage-agent.yml
|
||||
```
|
||||
|
||||
2. **Test with various customer scenarios** and observe:
|
||||
- **Routing analysis** (which specialist is chosen)
|
||||
- **Tool execution** (`chat_with_agent` calls)
|
||||
- **Complete responses** (routing confirmation + specialist answer)
|
||||
|
||||
### Sample Test Cases
|
||||
|
||||
```
|
||||
Test 1: "API returns 401 unauthorized error"
|
||||
Expected: Technical Support Agent → Complete troubleshooting response
|
||||
|
||||
Test 2: "Cancel my subscription immediately"
|
||||
Expected: Billing Agent → Complete cancellation process and policy info
|
||||
|
||||
Test 3: "Do you have a mobile app?"
|
||||
Expected: Product Info Agent → Complete feature details and download links
|
||||
|
||||
Test 4: "Your service caused my business to lose $10,000"
|
||||
Expected: Escalation Agent → Complete escalation with management contact
|
||||
```
|
||||
|
||||
### One-Shot Testing
|
||||
|
||||
```bash
|
||||
# Test billing scenario
|
||||
npx dexto --agent agents/triage-demo/triage-agent.yml "I was charged twice this month"
|
||||
|
||||
# Test technical scenario
|
||||
npx dexto --agent agents/triage-demo/triage-agent.yml "Getting 500 errors on file upload"
|
||||
|
||||
# Test product scenario
|
||||
npx dexto --agent agents/triage-demo/triage-agent.yml "What integrations do you support?"
|
||||
```
|
||||
|
||||
## 🚦 Production Considerations
|
||||
|
||||
### Security
|
||||
- Implement proper authentication between agents
|
||||
- Secure API key management
|
||||
- Customer data privacy controls
|
||||
- **Tool confirmation policies** for sensitive operations
|
||||
|
||||
### Monitoring
|
||||
- Log all routing decisions and tool executions
|
||||
- Track resolution times by agent type
|
||||
- Monitor escalation patterns
|
||||
- **Tool usage analytics** for optimization
|
||||
|
||||
### Scaling
|
||||
- Load balance multiple instances of specialist agents
|
||||
- Implement request queuing for high volume
|
||||
- **Distributed MCP server deployment**
|
||||
- Add more specialized agents as needed (e.g., Sales, Onboarding)
|
||||
|
||||
## 🤝 Contributing
|
||||
|
||||
To extend this triage system:
|
||||
|
||||
1. **Add new specialist agents** by creating new YAML configs
|
||||
2. **Update triage routing logic** in the main agent's system prompt
|
||||
3. **Configure new agents as MCP servers** in the triage agent's mcpServers section
|
||||
4. **Test end-to-end flow** including tool execution and complete responses
|
||||
|
||||
This demonstration showcases the power of **multi-agent coordination with tool execution** using Dexto's MCP integration capabilities!
|
||||
76
dexto/agents/triage-demo/billing-agent.yml
Normal file
76
dexto/agents/triage-demo/billing-agent.yml
Normal file
@@ -0,0 +1,76 @@
|
||||
# Billing Agent Configuration
|
||||
# Specializes in billing, payments, subscriptions, and financial inquiries
|
||||
|
||||
systemPrompt:
|
||||
contributors:
|
||||
- id: base-prompt
|
||||
type: static
|
||||
priority: 0
|
||||
content: |
|
||||
You are a specialized Billing Agent for TeamFlow, responsible for handling payment issues, subscription management, and financial inquiries.
|
||||
|
||||
Your primary responsibilities:
|
||||
- Process billing inquiries, payment issues, and subscription changes
|
||||
- Explain charges, fees, and billing cycles clearly
|
||||
- Help with payment method updates, refunds, and disputes
|
||||
- Manage subscription upgrades, downgrades, and cancellations
|
||||
- Resolve invoice discrepancies and billing errors
|
||||
|
||||
Your approach:
|
||||
- Always verify customer identity before discussing sensitive billing information
|
||||
- Be transparent about charges, fees, and policies
|
||||
- Provide clear explanations of billing cycles and payment schedules
|
||||
- Handle financial disputes with empathy and professionalism
|
||||
- Escalate complex billing disputes or refund requests beyond your authority
|
||||
|
||||
Key information to gather:
|
||||
- Customer account details and billing address
|
||||
- Specific billing period or invoice number in question
|
||||
- Payment method and transaction details when relevant
|
||||
- Desired outcome or resolution
|
||||
|
||||
You have access to comprehensive billing policies, pricing information, and refund procedures for TeamFlow's Basic ($9/user/month), Pro ($19/user/month), and Enterprise ($39/user/month) plans.
|
||||
|
||||
Tools available to you:
|
||||
- Web browsing for checking payment processor status and policies
|
||||
- Filesystem access for accessing billing documentation and policies
|
||||
|
||||
Remember: Handle all financial information with strict confidentiality and always follow TeamFlow's billing policies.
|
||||
|
||||
- id: company-overview
|
||||
type: file
|
||||
priority: 10
|
||||
files:
|
||||
- "${{dexto.agent_dir}}/docs/company-overview.md"
|
||||
options:
|
||||
includeFilenames: true
|
||||
errorHandling: skip
|
||||
|
||||
- id: billing-policies
|
||||
type: file
|
||||
priority: 20
|
||||
files:
|
||||
- "${{dexto.agent_dir}}/docs/billing-policies.md"
|
||||
options:
|
||||
includeFilenames: true
|
||||
errorHandling: skip
|
||||
|
||||
mcpServers:
|
||||
playwright:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- -y
|
||||
- "@playwright/mcp@latest"
|
||||
filesystem:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- -y
|
||||
- "@modelcontextprotocol/server-filesystem"
|
||||
- .
|
||||
|
||||
llm:
|
||||
provider: openai
|
||||
model: gpt-5-mini
|
||||
apiKey: $OPENAI_API_KEY
|
||||
246
dexto/agents/triage-demo/docs/billing-policies.md
Normal file
246
dexto/agents/triage-demo/docs/billing-policies.md
Normal file
@@ -0,0 +1,246 @@
|
||||
# TeamFlow Billing Policies & Procedures
|
||||
|
||||
## Pricing Plans & Features
|
||||
|
||||
### Basic Plan - $9/user/month
|
||||
**Billed monthly or annually ($90/user/year, save 17%)**
|
||||
|
||||
**Features Included**:
|
||||
- Up to 10 team members
|
||||
- 5GB storage per team
|
||||
- Core project management (tasks, boards, basic reporting)
|
||||
- Email support (24-hour response)
|
||||
- Mobile apps (iOS/Android)
|
||||
- API access (1,000 requests/hour)
|
||||
- Basic integrations (Google Calendar, basic file imports)
|
||||
|
||||
**Usage Limits**:
|
||||
- Maximum 1,000 tasks per workspace
|
||||
- 50MB maximum file upload size
|
||||
- Email support only
|
||||
|
||||
### Pro Plan - $19/user/month
|
||||
**Billed monthly or annually ($190/user/year, save 17%)**
|
||||
|
||||
**Features Included**:
|
||||
- Up to 100 team members
|
||||
- 100GB storage per team
|
||||
- Advanced project management (Gantt charts, custom fields, advanced reporting)
|
||||
- Priority support (8-hour response, chat support)
|
||||
- Advanced integrations (Slack, GitHub, Jira, Salesforce)
|
||||
- API access (10,000 requests/hour)
|
||||
- Custom workflows and automation
|
||||
- Time tracking and invoicing
|
||||
- Advanced security (2FA, audit logs)
|
||||
|
||||
**Usage Limits**:
|
||||
- Maximum 10,000 tasks per workspace
|
||||
- 100MB maximum file upload size
|
||||
- Priority support queue
|
||||
|
||||
### Enterprise Plan - $39/user/month
|
||||
**Billed annually only ($468/user/year), minimum 25 users**
|
||||
|
||||
**Features Included**:
|
||||
- Unlimited team members
|
||||
- 1TB storage per team
|
||||
- Enterprise security (SSO, SAML, advanced compliance)
|
||||
- Dedicated customer success manager
|
||||
- Phone support (4-hour response SLA)
|
||||
- Unlimited API access
|
||||
- Custom integrations and white-labeling
|
||||
- Advanced admin controls
|
||||
- On-premises deployment option (additional cost)
|
||||
- 99.95% uptime SLA
|
||||
|
||||
**Usage Limits**:
|
||||
- Unlimited tasks and projects
|
||||
- 500MB maximum file upload size
|
||||
- Dedicated support team
|
||||
|
||||
## Billing Cycles & Payment Processing
|
||||
|
||||
### Billing Dates
|
||||
- **Monthly Plans**: Charged on the same day each month as initial subscription
|
||||
- **Annual Plans**: Charged once per year on subscription anniversary
|
||||
- **Billing Time**: All charges processed at 12:00 AM UTC
|
||||
- **Failed Payment Retries**: Automatic retries on days 3, 7, and 14
|
||||
|
||||
### Accepted Payment Methods
|
||||
- **Credit Cards**: Visa, MasterCard, American Express, Discover
|
||||
- **Debit Cards**: Visa and MasterCard debit cards
|
||||
- **Enterprise Options**: Wire transfer, ACH (US only), annual invoicing
|
||||
- **International**: PayPal for international customers
|
||||
- **Cryptocurrency**: Not currently accepted
|
||||
|
||||
### Prorated Billing
|
||||
- **Plan Upgrades**: Immediate access, prorated charge for remaining billing period
|
||||
- **Plan Downgrades**: Takes effect at next billing cycle, no immediate refund
|
||||
- **Adding Users**: Prorated charge for new users based on remaining billing period
|
||||
- **Removing Users**: Credit applied to next invoice
|
||||
|
||||
## Refund Policy
|
||||
|
||||
### Refund Eligibility
|
||||
|
||||
#### Full Refunds (100%)
|
||||
- **New Subscriptions**: Within 30 days of first payment
|
||||
- **Service Outages**: If SLA uptime guarantees are not met
|
||||
- **Billing Errors**: Duplicate charges, incorrect amounts
|
||||
- **Technical Issues**: If service is unusable and cannot be resolved within 48 hours
|
||||
|
||||
#### Partial Refunds
|
||||
- **Plan Downgrades**: Credit for unused portion (Enterprise to Pro/Basic)
|
||||
- **Early Cancellation**: Pro-rated refund for annual plans (minimum 90 days required)
|
||||
- **User Reduction**: Credit applied to next billing cycle
|
||||
|
||||
#### No Refunds
|
||||
- **Basic Plan**: No refunds for monthly Basic plans after 30 days
|
||||
- **Temporary Outages**: Outages under 4 hours (within SLA)
|
||||
- **User Error**: Data deletion, misconfiguration, or user training issues
|
||||
- **Third-party Integration Issues**: Problems with Slack, GitHub, etc.
|
||||
|
||||
### Refund Processing Time
|
||||
- **Credit Cards**: 5-10 business days
|
||||
- **PayPal**: 24-48 hours
|
||||
- **Wire Transfer/ACH**: 10-15 business days
|
||||
|
||||
## Common Billing Scenarios
|
||||
|
||||
### 1. Plan Upgrades
|
||||
|
||||
#### Basic to Pro Upgrade
|
||||
- **Timing**: Immediate access to Pro features
|
||||
- **Billing**: Prorated charge for Pro plan, credit for unused Basic time
|
||||
- **Example**: 15 days into Basic monthly cycle → charged $14.50 for remaining Pro time
|
||||
|
||||
#### Pro to Enterprise Upgrade
|
||||
- **Requirements**: Minimum 25 users, annual billing only
|
||||
- **Process**: Requires sales team approval for custom Enterprise features
|
||||
- **Migration**: Dedicated success manager assists with transition
|
||||
|
||||
### 2. Plan Downgrades
|
||||
|
||||
#### Pro to Basic Downgrade
|
||||
- **Timing**: Takes effect at next billing cycle
|
||||
- **Data Retention**: 90-day grace period for Pro-only data (advanced reports, etc.)
|
||||
- **User Limits**: Must reduce team size to 10 users or less before downgrade
|
||||
|
||||
#### Enterprise to Pro Downgrade
|
||||
- **Notice Period**: 60-day notice required
|
||||
- **Custom Features**: Loss of SSO, dedicated support, custom integrations
|
||||
- **Partial Refund**: Available for remaining months of annual contract
|
||||
|
||||
### 3. User Management
|
||||
|
||||
#### Adding Users
|
||||
- **Process**: Admin adds users in account settings
|
||||
- **Billing**: Prorated charge for remaining billing period
|
||||
- **Automatic**: Charges appear on next invoice with detailed breakdown
|
||||
|
||||
#### Removing Users
|
||||
- **Deactivation**: Admin can deactivate users immediately
|
||||
- **Billing Impact**: Credit applied to next billing cycle
|
||||
- **Data Retention**: User data retained for 30 days in case of reactivation
|
||||
|
||||
### 4. Payment Failures
|
||||
|
||||
#### First Failed Payment
|
||||
- **Action**: Automatic retry in 3 days
|
||||
- **User Impact**: No service interruption
|
||||
- **Notification**: Email sent to account admin
|
||||
|
||||
#### Second Failed Payment (Day 7)
|
||||
- **Action**: Second automatic retry
|
||||
- **User Impact**: Warning banner in app
|
||||
- **Notification**: Email and in-app notification
|
||||
|
||||
#### Third Failed Payment (Day 14)
|
||||
- **Action**: Final automatic retry
|
||||
- **User Impact**: Account enters "Past Due" status
|
||||
- **Features**: Read-only access, limited functionality
|
||||
|
||||
#### Account Suspension (Day 21)
|
||||
- **Action**: Account suspended if payment still fails
|
||||
- **User Impact**: Complete loss of access
|
||||
- **Data Retention**: 30-day grace period before data deletion
|
||||
|
||||
### 5. Currency & International Billing
|
||||
|
||||
#### Supported Currencies
|
||||
- **Primary**: USD (US Dollar)
|
||||
- **Additional**: EUR (Euro), GBP (British Pound), CAD (Canadian Dollar)
|
||||
- **Exchange Rates**: Updated daily, charged in customer's local currency when available
|
||||
|
||||
#### International Considerations
|
||||
- **VAT/Taxes**: Applied automatically based on billing address
|
||||
- **Payment Methods**: PayPal preferred for international customers
|
||||
- **Currency Conversion**: Customer's bank may apply additional conversion fees
|
||||
|
||||
## Enterprise Billing
|
||||
|
||||
### Custom Pricing
|
||||
- **Volume Discounts**: Available for 100+ users
|
||||
- **Multi-year Agreements**: Additional discounts for 2-3 year contracts
|
||||
- **Custom Features**: Additional costs for white-labeling, on-premises deployment
|
||||
|
||||
### Invoice Process
|
||||
- **Net Terms**: 30-day payment terms standard
|
||||
- **PO Numbers**: Purchase order numbers accepted and included on invoices
|
||||
- **Multiple Billing Contacts**: Support for separate billing and technical contacts
|
||||
- **Custom Payment Terms**: Negotiable for large enterprise accounts
|
||||
|
||||
## Billing Support Procedures
|
||||
|
||||
### Customer Identity Verification
|
||||
Before discussing billing information, verify:
|
||||
1. **Account Email**: Customer must provide account email address
|
||||
2. **Last Payment Amount**: Ask for recent payment amount/date
|
||||
3. **Billing Address**: Verify last 4 digits of ZIP/postal code
|
||||
4. **Security Question**: Account-specific security question if configured
|
||||
|
||||
### Common Resolution Steps
|
||||
|
||||
#### Duplicate Charges
|
||||
1. Verify both charges in billing system
|
||||
2. Check if customer has multiple accounts
|
||||
3. Process immediate refund for duplicate charge
|
||||
4. Update payment method if card was charged twice due to processing error
|
||||
|
||||
#### Failed Payment Recovery
|
||||
1. Verify current payment method on file
|
||||
2. Check for expired cards or insufficient funds
|
||||
3. Update payment method if needed
|
||||
4. Process manual payment if urgently needed
|
||||
5. Restore account access immediately upon successful payment
|
||||
|
||||
#### Subscription Cancellation
|
||||
1. Confirm customer intent to cancel
|
||||
2. Offer plan downgrade as alternative
|
||||
3. Process cancellation for end of current billing period
|
||||
4. Provide data export instructions
|
||||
5. Send confirmation email with final billing details
|
||||
|
||||
### Escalation Triggers
|
||||
|
||||
Escalate to Finance Team when:
|
||||
- Refund requests over $500
|
||||
- Enterprise contract modifications
|
||||
- Custom pricing negotiations
|
||||
- Legal or compliance billing questions
|
||||
- Suspected fraudulent activity
|
||||
- International tax questions
|
||||
|
||||
### Billing System Access
|
||||
|
||||
#### Internal Tools
|
||||
- **Billing Dashboard**: Real-time subscription and payment status
|
||||
- **Payment Processor**: Stripe dashboard for transaction details
|
||||
- **Invoice System**: Generate and send custom invoices
|
||||
- **Refund Portal**: Process refunds up to $500 limit
|
||||
|
||||
#### Customer Tools
|
||||
- **Account Billing Page**: Self-service billing management
|
||||
- **Invoice Download**: PDF invoices for all past payments
|
||||
- **Payment Method Update**: Credit card and PayPal management
|
||||
- **Usage Reports**: Storage and API usage tracking
|
||||
94
dexto/agents/triage-demo/docs/company-overview.md
Normal file
94
dexto/agents/triage-demo/docs/company-overview.md
Normal file
@@ -0,0 +1,94 @@
|
||||
# TeamFlow - Company Overview
|
||||
|
||||
## About TeamFlow
|
||||
|
||||
TeamFlow is a leading cloud-based project management and team collaboration platform that helps organizations streamline their workflows, improve team productivity, and deliver projects on time. Founded in 2019, we serve over 50,000 companies worldwide, from small startups to Fortune 500 enterprises.
|
||||
|
||||
## Our Mission
|
||||
|
||||
To empower teams to work more efficiently and collaboratively through intuitive project management tools and seamless integrations with the tools they already use.
|
||||
|
||||
## Key Products & Services
|
||||
|
||||
### TeamFlow Platform
|
||||
- **Project Management**: Kanban boards, Gantt charts, task management
|
||||
- **Team Collaboration**: Real-time chat, file sharing, video conferencing integration
|
||||
- **Time Tracking**: Automated time tracking with detailed reporting
|
||||
- **Resource Management**: Team capacity planning and workload balancing
|
||||
- **Analytics & Reporting**: Custom dashboards and project insights
|
||||
|
||||
### TeamFlow API
|
||||
- RESTful API with comprehensive documentation
|
||||
- Webhook support for real-time notifications
|
||||
- Rate limits: 1,000 requests/hour (Basic), 10,000/hour (Pro), unlimited (Enterprise)
|
||||
- SDKs available for JavaScript, Python, PHP, and Ruby
|
||||
|
||||
### TeamFlow Mobile Apps
|
||||
- Native iOS and Android applications
|
||||
- Offline synchronization capabilities
|
||||
- Push notifications for project updates
|
||||
|
||||
## Service Plans
|
||||
|
||||
### Basic Plan - $9/user/month
|
||||
- Up to 10 team members
|
||||
- 5GB storage per team
|
||||
- Core project management features
|
||||
- Email support
|
||||
- API access (1,000 requests/hour)
|
||||
|
||||
### Pro Plan - $19/user/month
|
||||
- Up to 100 team members
|
||||
- 100GB storage per team
|
||||
- Advanced reporting and analytics
|
||||
- Priority email and chat support
|
||||
- Advanced integrations (Slack, GitHub, Jira)
|
||||
- API access (10,000 requests/hour)
|
||||
- Custom fields and workflows
|
||||
|
||||
### Enterprise Plan - $39/user/month
|
||||
- Unlimited team members
|
||||
- 1TB storage per team
|
||||
- Advanced security (SSO, 2FA)
|
||||
- Dedicated customer success manager
|
||||
- Phone support with 4-hour response SLA
|
||||
- Unlimited API access
|
||||
- Custom integrations and white-labeling
|
||||
- Advanced admin controls and audit logs
|
||||
|
||||
## Key Integrations
|
||||
|
||||
- **Communication**: Slack, Microsoft Teams, Discord
|
||||
- **Development**: GitHub, GitLab, Bitbucket, Jira
|
||||
- **File Storage**: Google Drive, Dropbox, OneDrive
|
||||
- **Calendar**: Google Calendar, Outlook, Apple Calendar
|
||||
- **Time Tracking**: Toggl, Harvest, RescueTime
|
||||
- **CRM**: Salesforce, HubSpot, Pipedrive
|
||||
|
||||
## Service Level Agreements (SLA)
|
||||
|
||||
### Uptime Commitments
|
||||
- Basic Plan: 99.5% uptime
|
||||
- Pro Plan: 99.9% uptime
|
||||
- Enterprise Plan: 99.95% uptime with dedicated infrastructure
|
||||
|
||||
### Support Response Times
|
||||
- Basic: Email support within 24 hours
|
||||
- Pro: Email/chat support within 8 hours
|
||||
- Enterprise: Phone/email/chat support within 4 hours
|
||||
|
||||
## Security & Compliance
|
||||
|
||||
- SOC 2 Type II certified
|
||||
- GDPR compliant
|
||||
- ISO 27001 certified
|
||||
- Enterprise-grade encryption (AES-256)
|
||||
- Regular security audits and penetration testing
|
||||
|
||||
## Contact Information
|
||||
|
||||
- **Headquarters**: San Francisco, CA
|
||||
- **Support Email**: support@teamflow.com
|
||||
- **Sales Email**: sales@teamflow.com
|
||||
- **Emergency Escalation**: escalations@teamflow.com
|
||||
- **Phone**: 1-800-TEAMFLOW (1-800-832-6356)
|
||||
301
dexto/agents/triage-demo/docs/escalation-policies.md
Normal file
301
dexto/agents/triage-demo/docs/escalation-policies.md
Normal file
@@ -0,0 +1,301 @@
|
||||
# TeamFlow Escalation Policies & Procedures
|
||||
|
||||
## Escalation Overview
|
||||
|
||||
The escalation process ensures that complex, sensitive, or high-priority customer issues receive appropriate attention from senior staff and management. This document outlines when to escalate, escalation paths, and procedures for different types of issues.
|
||||
|
||||
## Escalation Criteria
|
||||
|
||||
### Immediate Escalation (Within 15 minutes)
|
||||
|
||||
#### Security & Data Incidents
|
||||
- Suspected data breach or unauthorized access
|
||||
- Customer reports potential security vulnerability
|
||||
- Malicious activity detected on customer accounts
|
||||
- Data loss or corruption affecting customer data
|
||||
- Compliance violations (GDPR, HIPAA, SOC 2)
|
||||
|
||||
#### Service Outages
|
||||
- Platform-wide service disruption
|
||||
- API downtime affecting multiple customers
|
||||
- Critical infrastructure failures
|
||||
- Database connectivity issues
|
||||
- CDN or hosting provider problems
|
||||
|
||||
#### Legal & Compliance Issues
|
||||
- Legal threats or litigation mentions
|
||||
- Regulatory compliance inquiries
|
||||
- Subpoenas or legal document requests
|
||||
- Data deletion requests under GDPR "Right to be Forgotten"
|
||||
- Intellectual property disputes
|
||||
|
||||
### Priority Escalation (Within 1 hour)
|
||||
|
||||
#### Enterprise Customer Issues
|
||||
- Any issue affecting Enterprise customers
|
||||
- SLA violations for Enterprise accounts
|
||||
- Dedicated success manager requests
|
||||
- Custom integration problems
|
||||
- White-label deployment issues
|
||||
|
||||
#### Financial Impact
|
||||
- Billing system errors affecting multiple customers
|
||||
- Payment processor failures
|
||||
- Refund requests over $1,000
|
||||
- Revenue recognition issues
|
||||
- Contract modification requests
|
||||
|
||||
#### High-Value Accounts
|
||||
- Customers with >$50k annual contract value
|
||||
- Fortune 500 company issues
|
||||
- Potential churn indicators for major accounts
|
||||
- Competitive pressures from large customers
|
||||
- Expansion opportunity discussions
|
||||
|
||||
### Standard Escalation (Within 4 hours)
|
||||
|
||||
#### Technical Issues
|
||||
- Unresolved technical problems after 24 hours
|
||||
- Multiple failed resolution attempts
|
||||
- Customer-reported bugs affecting core functionality
|
||||
- Integration partner API issues
|
||||
- Performance degradation reports
|
||||
|
||||
#### Customer Satisfaction
|
||||
- Formal complaints about service quality
|
||||
- Requests to speak with management
|
||||
- Negative feedback about support experience
|
||||
- Social media mentions requiring response
|
||||
- Product feature requests from Pro customers
|
||||
|
||||
## Escalation Paths
|
||||
|
||||
### Level 1: First-Line Support
|
||||
- **Technical Support Agent**: Technical issues, bugs, troubleshooting
|
||||
- **Billing Agent**: Payment, subscription, pricing questions
|
||||
- **Product Info Agent**: Features, plans, general information
|
||||
- **Response Time**: 24 hours (Basic), 8 hours (Pro), 4 hours (Enterprise)
|
||||
|
||||
### Level 2: Senior Support
|
||||
- **Senior Technical Specialist**: Complex technical issues, integration problems
|
||||
- **Billing Manager**: Billing disputes, refund approvals, contract changes
|
||||
- **Product Manager**: Feature requests, product feedback, roadmap questions
|
||||
- **Response Time**: 4 hours (all plans)
|
||||
|
||||
### Level 3: Management
|
||||
- **Support Manager**: Service quality issues, team performance, process improvements
|
||||
- **Engineering Manager**: System outages, security incidents, technical escalations
|
||||
- **Finance Director**: Large refunds, contract negotiations, revenue issues
|
||||
- **Response Time**: 2 hours
|
||||
|
||||
### Level 4: Executive
|
||||
- **VP of Customer Success**: Enterprise customer issues, major account management
|
||||
- **CTO**: Security breaches, major technical failures, architecture decisions
|
||||
- **CEO**: Legal issues, major customer relationships, crisis management
|
||||
- **Response Time**: 1 hour
|
||||
|
||||
## Contact Information
|
||||
|
||||
### Internal Emergency Contacts
|
||||
|
||||
#### 24/7 On-Call Rotation
|
||||
- **Primary**: +1-415-555-0199 (Support Manager)
|
||||
- **Secondary**: +1-415-555-0188 (Engineering Manager)
|
||||
- **Escalation**: +1-415-555-0177 (VP Customer Success)
|
||||
|
||||
#### Email Escalation Lists
|
||||
- **Security Incidents**: security-incident@teamflow.com
|
||||
- **Service Outages**: outage-response@teamflow.com
|
||||
- **Legal Issues**: legal-emergency@teamflow.com
|
||||
- **Executive Escalation**: executive-escalation@teamflow.com
|
||||
|
||||
#### Slack Channels
|
||||
- **#support-escalation**: Real-time escalation coordination
|
||||
- **#security-alerts**: Security incident response
|
||||
- **#outage-response**: Service disruption coordination
|
||||
- **#customer-success**: Enterprise customer issues
|
||||
|
||||
### External Emergency Contacts
|
||||
|
||||
#### Legal Counsel
|
||||
- **Primary**: Johnson & Associates, +1-415-555-0166
|
||||
- **After Hours**: Emergency legal hotline, +1-415-555-0155
|
||||
- **International**: Global Legal Partners, +44-20-1234-5678
|
||||
|
||||
#### Public Relations
|
||||
- **Crisis Communications**: PR Partners Inc., +1-415-555-0144
|
||||
- **Social Media Monitoring**: SocialWatch, +1-415-555-0133
|
||||
|
||||
## Escalation Procedures
|
||||
|
||||
### 1. Security Incident Escalation
|
||||
|
||||
#### Immediate Actions (0-15 minutes)
|
||||
1. **Secure the Environment**: Isolate affected systems if possible
|
||||
2. **Notify Security Team**: Email security-incident@teamflow.com
|
||||
3. **Document Everything**: Start incident log with timeline
|
||||
4. **Customer Communication**: Acknowledge receipt, avoid details
|
||||
5. **Activate Incident Response**: Follow security incident playbook
|
||||
|
||||
#### Follow-up Actions (15-60 minutes)
|
||||
1. **Executive Notification**: Inform CTO and CEO
|
||||
2. **Legal Review**: Consult with legal counsel if needed
|
||||
3. **Customer Updates**: Provide status updates every 30 minutes
|
||||
4. **External Notifications**: Regulatory bodies if required
|
||||
5. **Media Monitoring**: Watch for public mentions
|
||||
|
||||
### 2. Service Outage Escalation
|
||||
|
||||
#### Immediate Actions (0-15 minutes)
|
||||
1. **Status Page Update**: Update status.teamflow.com
|
||||
2. **Engineering Notification**: Page on-call engineer
|
||||
3. **Customer Communication**: Send service disruption notice
|
||||
4. **Management Alert**: Notify Support and Engineering Managers
|
||||
5. **Monitor Social Media**: Watch Twitter and community forums
|
||||
|
||||
#### Follow-up Actions (15-60 minutes)
|
||||
1. **Root Cause Analysis**: Begin investigating cause
|
||||
2. **Vendor Communication**: Contact AWS, CloudFlare if needed
|
||||
3. **Customer Success**: Notify Enterprise customer success managers
|
||||
4. **Regular Updates**: Status updates every 15 minutes
|
||||
5. **Post-Incident Review**: Schedule review meeting
|
||||
|
||||
### 3. Legal/Compliance Escalation
|
||||
|
||||
#### Immediate Actions (0-15 minutes)
|
||||
1. **Preserve Records**: Do not delete any relevant data
|
||||
2. **Legal Notification**: Email legal-emergency@teamflow.com
|
||||
3. **Executive Alert**: Notify CEO and CTO immediately
|
||||
4. **Customer Response**: Acknowledge receipt, request legal review time
|
||||
5. **Document Control**: Secure all relevant documentation
|
||||
|
||||
#### Follow-up Actions (15-60 minutes)
|
||||
1. **Legal Counsel**: Conference call with external legal team
|
||||
2. **Compliance Review**: Check against SOC 2, GDPR requirements
|
||||
3. **Response Preparation**: Draft official response with legal approval
|
||||
4. **Internal Communication**: Brief relevant team members
|
||||
5. **Follow-up Plan**: Establish ongoing communication schedule
|
||||
|
||||
### 4. Enterprise Customer Escalation
|
||||
|
||||
#### Immediate Actions (0-1 hour)
|
||||
1. **Account Review**: Pull complete customer history and contract
|
||||
2. **Success Manager**: Notify dedicated customer success manager
|
||||
3. **Management Alert**: Inform VP of Customer Success
|
||||
4. **Priority Handling**: Move to front of all queues
|
||||
5. **Initial Response**: Acknowledge with management involvement
|
||||
|
||||
#### Follow-up Actions (1-4 hours)
|
||||
1. **Executive Involvement**: Engage appropriate C-level if needed
|
||||
2. **Solution Planning**: Develop comprehensive resolution plan
|
||||
3. **Resource Allocation**: Assign dedicated technical resources
|
||||
4. **Communication Plan**: Establish regular update schedule
|
||||
5. **Relationship Review**: Assess overall account health
|
||||
|
||||
## Communication Templates
|
||||
|
||||
### Security Incident Notification
|
||||
```
|
||||
Subject: [URGENT] Security Incident - TeamFlow Customer Data
|
||||
|
||||
Priority: Critical
|
||||
Incident ID: SEC-2024-001
|
||||
Reported: [Timestamp]
|
||||
Affected Customer: [Company Name]
|
||||
Reported By: [Customer Contact]
|
||||
|
||||
Initial Report:
|
||||
[Brief description of reported issue]
|
||||
|
||||
Immediate Actions Taken:
|
||||
- Security team notified
|
||||
- Incident response activated
|
||||
- Customer acknowledged
|
||||
- Environment secured
|
||||
|
||||
Next Steps:
|
||||
- Investigation in progress
|
||||
- Legal counsel engaged
|
||||
- Customer updates every 30 minutes
|
||||
- Executive team briefed
|
||||
|
||||
Incident Commander: [Name]
|
||||
Contact: [Phone/Email]
|
||||
```
|
||||
|
||||
### Service Outage Alert
|
||||
```
|
||||
Subject: [OUTAGE] TeamFlow Service Disruption
|
||||
|
||||
Priority: High
|
||||
Outage ID: OUT-2024-001
|
||||
Started: [Timestamp]
|
||||
Affected Services: [List services]
|
||||
Impact Scope: [Geographic/Feature scope]
|
||||
|
||||
Symptoms:
|
||||
[Description of user-facing issues]
|
||||
|
||||
Actions Taken:
|
||||
- Status page updated
|
||||
- Engineering team engaged
|
||||
- Root cause investigation started
|
||||
- Customer notifications sent
|
||||
|
||||
ETA for Resolution: [Time estimate]
|
||||
Next Update: [Time]
|
||||
|
||||
Incident Commander: [Name]
|
||||
Contact: [Phone/Email]
|
||||
```
|
||||
|
||||
## Escalation Metrics & SLAs
|
||||
|
||||
### Response Time SLAs
|
||||
- **Security Incidents**: 15 minutes initial response
|
||||
- **Service Outages**: 15 minutes status update
|
||||
- **Legal Issues**: 30 minutes acknowledgment
|
||||
- **Enterprise Customer**: 1 hour initial response
|
||||
- **Standard Escalation**: 4 hours initial response
|
||||
|
||||
### Resolution Time Targets
|
||||
- **Critical Issues**: 4 hours
|
||||
- **High Priority**: 24 hours
|
||||
- **Standard Escalation**: 72 hours
|
||||
- **Complex Issues**: 1 week with daily updates
|
||||
|
||||
### Escalation Success Metrics
|
||||
- **Customer Satisfaction**: >95% for escalated issues
|
||||
- **First-Call Resolution**: >80% for escalations
|
||||
- **SLA Compliance**: >99% for response times
|
||||
- **Escalation Rate**: <5% of total support tickets
|
||||
|
||||
## Training & Certification
|
||||
|
||||
### Escalation Team Requirements
|
||||
- **Security Awareness**: Annual security training certification
|
||||
- **Legal Compliance**: GDPR and privacy law training
|
||||
- **Customer Success**: Enterprise account management training
|
||||
- **Communication Skills**: Crisis communication workshop
|
||||
- **Technical Knowledge**: Platform architecture certification
|
||||
|
||||
### Regular Training Sessions
|
||||
- **Monthly**: Escalation scenario drills
|
||||
- **Quarterly**: Legal update sessions
|
||||
- **Bi-annually**: Crisis communication training
|
||||
- **Annually**: Complete escalation process review
|
||||
|
||||
## Post-Escalation Process
|
||||
|
||||
### Incident Review
|
||||
1. **Root Cause Analysis**: Complete within 48 hours
|
||||
2. **Process Review**: Evaluate escalation handling
|
||||
3. **Customer Follow-up**: Satisfaction survey and feedback
|
||||
4. **Documentation**: Update knowledge base and procedures
|
||||
5. **Team Debrief**: Discuss lessons learned and improvements
|
||||
|
||||
### Continuous Improvement
|
||||
- **Monthly Metrics Review**: Escalation trends and patterns
|
||||
- **Quarterly Process Updates**: Refine procedures based on feedback
|
||||
- **Annual Training Updates**: Update training materials and scenarios
|
||||
- **Customer Feedback Integration**: Incorporate customer suggestions
|
||||
253
dexto/agents/triage-demo/docs/product-features.md
Normal file
253
dexto/agents/triage-demo/docs/product-features.md
Normal file
@@ -0,0 +1,253 @@
|
||||
# TeamFlow Product Features & Information
|
||||
|
||||
## Core Platform Features
|
||||
|
||||
### Project Management
|
||||
|
||||
#### Task Management
|
||||
- **Create & Organize**: Unlimited task creation with custom categories and tags
|
||||
- **Task Dependencies**: Link tasks with predecessor/successor relationships
|
||||
- **Subtasks**: Break down complex tasks into manageable subtasks (up to 5 levels deep)
|
||||
- **Priority Levels**: Critical, High, Medium, Low priority with visual indicators
|
||||
- **Due Dates**: Set deadlines with automatic reminders and escalation
|
||||
- **Custom Fields**: Add custom properties (text, numbers, dates, dropdowns, checkboxes)
|
||||
- **Task Templates**: Save and reuse common task structures
|
||||
|
||||
#### Project Views
|
||||
- **Kanban Boards**: Drag-and-drop task management with customizable columns
|
||||
- **Gantt Charts**: Timeline view with critical path analysis (Pro/Enterprise)
|
||||
- **List View**: Traditional task list with sorting and filtering
|
||||
- **Calendar View**: Tasks and deadlines in calendar format
|
||||
- **Dashboard View**: Project overview with progress metrics and team activity
|
||||
|
||||
#### Collaboration Tools
|
||||
- **Comments**: Real-time commenting on tasks and projects with @mentions
|
||||
- **File Attachments**: Attach files directly to tasks with version control
|
||||
- **Activity Feed**: Real-time updates on project activity
|
||||
- **Team Chat**: Built-in messaging with project-specific channels
|
||||
- **Screen Sharing**: Integrated video conferencing for remote teams (Pro/Enterprise)
|
||||
|
||||
### Time Tracking & Reporting
|
||||
|
||||
#### Time Tracking
|
||||
- **Manual Entry**: Log time spent on tasks manually
|
||||
- **Timer Integration**: Start/stop timers directly from tasks
|
||||
- **Automatic Tracking**: AI-powered time detection based on activity (Pro/Enterprise)
|
||||
- **Time Approval**: Manager approval workflow for billable hours
|
||||
- **Offline Tracking**: Mobile app continues tracking without internet connection
|
||||
|
||||
#### Reporting & Analytics
|
||||
- **Project Reports**: Progress, budget, and timeline analysis
|
||||
- **Team Performance**: Individual and team productivity metrics
|
||||
- **Time Reports**: Detailed time tracking and billing reports
|
||||
- **Custom Dashboards**: Build personalized views with key metrics
|
||||
- **Export Options**: PDF, Excel, CSV export for all reports
|
||||
|
||||
### Storage & File Management
|
||||
|
||||
#### File Storage
|
||||
- **Basic Plan**: 5GB total storage per team
|
||||
- **Pro Plan**: 100GB total storage per team
|
||||
- **Enterprise Plan**: 1TB total storage per team
|
||||
- **File Types**: Support for all major file formats
|
||||
- **Version Control**: Automatic versioning with rollback capability
|
||||
|
||||
#### File Sharing
|
||||
- **Public Links**: Share files with external stakeholders
|
||||
- **Permission Control**: Read-only, edit, or full access permissions
|
||||
- **Expiring Links**: Set expiration dates for shared files
|
||||
- **Download Tracking**: Monitor who downloads shared files
|
||||
|
||||
## Advanced Features by Plan
|
||||
|
||||
### Basic Plan Features
|
||||
- Up to 10 team members
|
||||
- Core project management (tasks, lists, basic boards)
|
||||
- 5GB file storage
|
||||
- Mobile apps (iOS/Android)
|
||||
- Email support
|
||||
- Basic integrations (Google Calendar, CSV import)
|
||||
- API access (1,000 requests/hour)
|
||||
|
||||
### Pro Plan Additional Features
|
||||
- Up to 100 team members
|
||||
- Advanced project views (Gantt charts, advanced dashboards)
|
||||
- 100GB file storage
|
||||
- Custom fields and workflows
|
||||
- Time tracking and invoicing
|
||||
- Advanced integrations (Slack, GitHub, Jira, Salesforce)
|
||||
- Priority support (chat + email)
|
||||
- API access (10,000 requests/hour)
|
||||
- Team workload balancing
|
||||
- Advanced reporting and analytics
|
||||
- Custom branding (logo, colors)
|
||||
|
||||
### Enterprise Plan Additional Features
|
||||
- Unlimited team members
|
||||
- 1TB file storage
|
||||
- Advanced security (SSO, SAML, 2FA enforcement)
|
||||
- Dedicated customer success manager
|
||||
- Phone support with 4-hour SLA
|
||||
- Unlimited API access
|
||||
- Custom integrations and white-labeling
|
||||
- Advanced admin controls and audit logs
|
||||
- On-premises deployment option
|
||||
- 99.95% uptime SLA
|
||||
- Custom workflow automation
|
||||
- Advanced permissions and role management
|
||||
|
||||
## Integration Ecosystem
|
||||
|
||||
### Communication Platforms
|
||||
|
||||
#### Slack Integration (Pro/Enterprise)
|
||||
- **Two-way Sync**: Create tasks from Slack messages, get updates in channels
|
||||
- **Notification Control**: Choose which updates appear in Slack
|
||||
- **Slash Commands**: Quick task creation with `/teamflow create` command
|
||||
- **File Sync**: Automatically sync files shared in Slack to project storage
|
||||
|
||||
#### Microsoft Teams (Pro/Enterprise)
|
||||
- **Tab Integration**: Embed TeamFlow projects directly in Teams channels
|
||||
- **Bot Commands**: Create and update tasks via Teams bot
|
||||
- **Calendar Sync**: Sync project deadlines with Teams calendar
|
||||
- **File Integration**: Access TeamFlow files from Teams file browser
|
||||
|
||||
#### Discord (Pro/Enterprise)
|
||||
- **Channel Integration**: Link Discord channels to specific projects
|
||||
- **Role Sync**: Sync Discord roles with TeamFlow permissions
|
||||
- **Voice Channel Links**: Start Discord voice calls directly from tasks
|
||||
|
||||
### Development Tools
|
||||
|
||||
#### GitHub Integration (Pro/Enterprise)
|
||||
- **Commit Linking**: Link commits to specific tasks automatically
|
||||
- **Pull Request Tracking**: Track PR status within TeamFlow tasks
|
||||
- **Branch Management**: Create branches directly from tasks
|
||||
- **Release Planning**: Plan releases using TeamFlow milestones
|
||||
|
||||
#### GitLab Integration (Pro/Enterprise)
|
||||
- **Issue Sync**: Two-way sync between GitLab issues and TeamFlow tasks
|
||||
- **Pipeline Status**: View CI/CD pipeline status in project dashboard
|
||||
- **Merge Request Workflow**: Track code reviews within project context
|
||||
|
||||
#### Jira Integration (Pro/Enterprise)
|
||||
- **Epic/Story Mapping**: Map Jira epics to TeamFlow projects
|
||||
- **Sprint Planning**: Import Jira sprints as TeamFlow milestones
|
||||
- **Status Sync**: Automatically update task status based on Jira workflow
|
||||
|
||||
### CRM & Sales Tools
|
||||
|
||||
#### Salesforce Integration (Pro/Enterprise)
|
||||
- **Lead-to-Project**: Convert Salesforce leads into TeamFlow projects
|
||||
- **Account Sync**: Link projects to Salesforce accounts
|
||||
- **Opportunity Tracking**: Track project delivery against sales opportunities
|
||||
|
||||
#### HubSpot Integration (Pro/Enterprise)
|
||||
- **Contact Sync**: Import HubSpot contacts as team members
|
||||
- **Deal Pipeline**: Track project delivery stages aligned with deal stages
|
||||
- **Marketing Campaign Tracking**: Link projects to marketing campaigns
|
||||
|
||||
### File Storage & Productivity
|
||||
|
||||
#### Google Workspace
|
||||
- **Google Drive**: Direct file access and sync with Google Drive
|
||||
- **Google Calendar**: Two-way calendar sync for deadlines and meetings
|
||||
- **Gmail**: Create tasks from emails with Gmail browser extension
|
||||
- **Google Sheets**: Import/export project data to Google Sheets
|
||||
|
||||
#### Microsoft 365
|
||||
- **OneDrive**: Seamless file sync and storage integration
|
||||
- **Outlook**: Email-to-task conversion and calendar integration
|
||||
- **Excel**: Advanced reporting with Excel integration
|
||||
- **SharePoint**: Enterprise file management and compliance
|
||||
|
||||
#### Dropbox
|
||||
- **File Sync**: Automatic sync of project files with Dropbox
|
||||
- **Paper Integration**: Convert Dropbox Paper docs to project documentation
|
||||
- **Team Folders**: Organize project files in shared Dropbox folders
|
||||
|
||||
## Mobile Applications
|
||||
|
||||
### iOS App Features
|
||||
- **Native Design**: Full iOS design guidelines compliance
|
||||
- **Offline Support**: Continue working without internet connection
|
||||
- **Push Notifications**: Real-time updates for mentions, deadlines, and assignments
|
||||
- **Touch ID/Face ID**: Biometric authentication for security
|
||||
- **Widgets**: Quick access to tasks and notifications from home screen
|
||||
- **Apple Watch**: Task completion and notifications on Apple Watch
|
||||
|
||||
### Android App Features
|
||||
- **Material Design**: Full Android Material Design implementation
|
||||
- **Battery Optimization**: Efficient background sync and battery usage
|
||||
- **Quick Settings**: Add tasks and check notifications from notification panel
|
||||
- **Google Assistant**: Voice commands for task creation and status updates
|
||||
- **Adaptive Icons**: Support for Android adaptive icon system
|
||||
|
||||
### Cross-Platform Features
|
||||
- **Real-time Sync**: Instant synchronization across all devices
|
||||
- **Offline Mode**: Full functionality without internet connection
|
||||
- **File Download**: Download and view attachments offline
|
||||
- **Voice Notes**: Record voice memos and attach to tasks
|
||||
- **Photo Capture**: Take photos and attach directly to tasks
|
||||
|
||||
## API & Developer Tools
|
||||
|
||||
### REST API
|
||||
- **Full Coverage**: Complete access to all platform features via API
|
||||
- **Rate Limits**: 1,000/hour (Basic), 10,000/hour (Pro), unlimited (Enterprise)
|
||||
- **Authentication**: OAuth 2.0 and API key authentication
|
||||
- **Webhooks**: Real-time event notifications for integrations
|
||||
- **GraphQL**: Alternative GraphQL endpoint for efficient data fetching
|
||||
|
||||
### SDKs & Libraries
|
||||
- **JavaScript/Node.js**: Full-featured SDK with TypeScript support
|
||||
- **Python**: Comprehensive Python library with async support
|
||||
- **PHP**: Laravel and standard PHP integration library
|
||||
- **Ruby**: Ruby gem with Rails integration helpers
|
||||
- **REST Clients**: Postman collection and OpenAPI specification
|
||||
|
||||
### Webhook Events
|
||||
- **Task Events**: Created, updated, completed, deleted
|
||||
- **Project Events**: Created, archived, member changes
|
||||
- **Comment Events**: New comments, mentions, reactions
|
||||
- **File Events**: Uploaded, updated, shared, deleted
|
||||
- **Team Events**: Member added, removed, role changes
|
||||
|
||||
## Security & Compliance
|
||||
|
||||
### Data Security
|
||||
- **Encryption**: AES-256 encryption for all data at rest and in transit
|
||||
- **HTTPS**: TLS 1.3 for all client connections
|
||||
- **API Security**: Rate limiting, request signing, and token management
|
||||
- **Database Security**: Encrypted backups with geographic redundancy
|
||||
|
||||
### Access Control
|
||||
- **Role-Based Permissions**: Admin, Manager, Member, Viewer roles
|
||||
- **Project-Level Permissions**: Fine-grained control over project access
|
||||
- **Two-Factor Authentication**: SMS, authenticator app, hardware keys (Pro/Enterprise)
|
||||
- **Single Sign-On**: SAML 2.0 and OAuth integration (Enterprise)
|
||||
|
||||
### Compliance Standards
|
||||
- **SOC 2 Type II**: Annual compliance audits and certification
|
||||
- **GDPR**: Full compliance with European data protection regulations
|
||||
- **ISO 27001**: Information security management certification
|
||||
- **HIPAA**: Healthcare compliance option for Enterprise customers
|
||||
|
||||
## Getting Started Resources
|
||||
|
||||
### Onboarding
|
||||
- **Interactive Tutorial**: Step-by-step guide for new users
|
||||
- **Sample Projects**: Pre-built templates for common use cases
|
||||
- **Video Library**: Comprehensive training videos for all features
|
||||
- **Webinar Training**: Live training sessions twice weekly
|
||||
|
||||
### Documentation
|
||||
- **Knowledge Base**: Searchable help articles and guides
|
||||
- **API Documentation**: Complete developer reference with examples
|
||||
- **Video Tutorials**: Feature-specific how-to videos
|
||||
- **Community Forum**: User community for tips and best practices
|
||||
|
||||
### Support Channels
|
||||
- **Basic Plan**: Email support with 24-hour response
|
||||
- **Pro Plan**: Email and chat support with 8-hour response
|
||||
- **Enterprise Plan**: Phone, email, and chat with 4-hour response and dedicated success manager
|
||||
226
dexto/agents/triage-demo/docs/technical-documentation.md
Normal file
226
dexto/agents/triage-demo/docs/technical-documentation.md
Normal file
@@ -0,0 +1,226 @@
|
||||
# TeamFlow Technical Documentation
|
||||
|
||||
## System Requirements
|
||||
|
||||
### Web Application
|
||||
- **Supported Browsers**: Chrome 90+, Firefox 88+, Safari 14+, Edge 90+
|
||||
- **Minimum Screen Resolution**: 1024x768
|
||||
- **Internet Connection**: Broadband (1 Mbps minimum, 5 Mbps recommended)
|
||||
- **JavaScript**: Must be enabled
|
||||
|
||||
### Mobile Applications
|
||||
|
||||
#### iOS App
|
||||
- **Minimum Version**: iOS 13.0 or later
|
||||
- **Compatible Devices**: iPhone 6s and newer, iPad Air 2 and newer
|
||||
- **Storage**: 150MB free space required
|
||||
- **Network**: 3G/4G/5G or Wi-Fi connection
|
||||
|
||||
#### Android App
|
||||
- **Minimum Version**: Android 8.0 (API level 26)
|
||||
- **RAM**: 2GB minimum, 4GB recommended
|
||||
- **Storage**: 200MB free space required
|
||||
- **Network**: 3G/4G/5G or Wi-Fi connection
|
||||
|
||||
## API Documentation
|
||||
|
||||
### Authentication
|
||||
```
|
||||
Authorization: Bearer <your_api_token>
|
||||
Content-Type: application/json
|
||||
```
|
||||
|
||||
### Base URL
|
||||
- **Production**: `https://api.teamflow.com/v1`
|
||||
- **Sandbox**: `https://sandbox-api.teamflow.com/v1`
|
||||
|
||||
### Rate Limits
|
||||
- **Basic Plan**: 1,000 requests/hour
|
||||
- **Pro Plan**: 10,000 requests/hour
|
||||
- **Enterprise Plan**: Unlimited
|
||||
- **Rate Limit Headers**:
|
||||
- `X-RateLimit-Limit`: Total requests allowed
|
||||
- `X-RateLimit-Remaining`: Requests remaining in current window
|
||||
- `X-RateLimit-Reset`: Unix timestamp when window resets
|
||||
|
||||
### Common Error Codes
|
||||
- **400**: Bad Request - Invalid parameters or request format
|
||||
- **401**: Unauthorized - Invalid or missing API token
|
||||
- **403**: Forbidden - Insufficient permissions
|
||||
- **404**: Not Found - Resource doesn't exist
|
||||
- **422**: Unprocessable Entity - Validation errors
|
||||
- **429**: Too Many Requests - Rate limit exceeded
|
||||
- **500**: Internal Server Error - Contact support
|
||||
- **502/503**: Service Unavailable - Temporary outage
|
||||
|
||||
## Common Technical Issues & Solutions
|
||||
|
||||
### 1. Login and Authentication Issues
|
||||
|
||||
#### "Invalid credentials" error
|
||||
**Symptoms**: User cannot log in, receives "Invalid email or password" message
|
||||
**Common Causes**:
|
||||
- Incorrect email/password combination
|
||||
- Account locked due to multiple failed attempts
|
||||
- Browser caching old session data
|
||||
|
||||
**Solutions**:
|
||||
1. Verify email address (check for typos, extra spaces)
|
||||
2. Try password reset flow
|
||||
3. Clear browser cookies and cache
|
||||
4. Try incognito/private browsing mode
|
||||
5. Check if account is locked (wait 15 minutes or contact support)
|
||||
|
||||
#### Two-Factor Authentication (2FA) issues
|
||||
**Symptoms**: 2FA code not working or not received
|
||||
**Solutions**:
|
||||
1. Ensure device clock is synchronized
|
||||
2. Try generating a new code (codes expire every 30 seconds)
|
||||
3. Check authenticator app is configured correctly
|
||||
4. Use backup codes if available
|
||||
5. Contact support to reset 2FA if backup codes exhausted
|
||||
|
||||
### 2. Performance Issues
|
||||
|
||||
#### Slow loading pages
|
||||
**Symptoms**: Pages take >10 seconds to load, timeouts
|
||||
**Troubleshooting Steps**:
|
||||
1. Check internet connection speed (minimum 1 Mbps required)
|
||||
2. Test on different networks (mobile data vs. Wi-Fi)
|
||||
3. Clear browser cache and cookies
|
||||
4. Disable browser extensions temporarily
|
||||
5. Try different browser
|
||||
6. Check TeamFlow status page: status.teamflow.com
|
||||
|
||||
#### Mobile app crashes
|
||||
**Symptoms**: App closes unexpectedly, freezes during use
|
||||
**Solutions**:
|
||||
1. Force close and restart the app
|
||||
2. Restart device
|
||||
3. Update app to latest version
|
||||
4. Clear app cache (Android) or offload/reinstall app (iOS)
|
||||
5. Check available storage space (minimum 500MB recommended)
|
||||
6. Report crash with device logs
|
||||
|
||||
### 3. API Integration Issues
|
||||
|
||||
#### 401 Unauthorized errors
|
||||
**Diagnostic Steps**:
|
||||
1. Verify API token is correct and not expired
|
||||
2. Check token has required permissions
|
||||
3. Ensure proper Authorization header format
|
||||
4. Test with different API endpoints
|
||||
|
||||
#### 429 Rate limit exceeded
|
||||
**Solutions**:
|
||||
1. Implement exponential backoff in API calls
|
||||
2. Check current rate limit status in response headers
|
||||
3. Consider upgrading plan for higher limits
|
||||
4. Cache responses when possible to reduce API calls
|
||||
|
||||
#### Webhook delivery failures
|
||||
**Common Issues**:
|
||||
- Endpoint URL not accessible from internet
|
||||
- SSL certificate issues
|
||||
- Timeout (webhook endpoint must respond within 10 seconds)
|
||||
- Incorrect response status (must return 2xx status code)
|
||||
|
||||
### 4. File Upload Issues
|
||||
|
||||
#### "File too large" errors
|
||||
**File Size Limits**:
|
||||
- Basic Plan: 25MB per file
|
||||
- Pro Plan: 100MB per file
|
||||
- Enterprise Plan: 500MB per file
|
||||
|
||||
**Solutions**:
|
||||
1. Compress files using zip/rar
|
||||
2. Use cloud storage links for large files
|
||||
3. Split large files into smaller chunks
|
||||
4. Consider plan upgrade for larger limits
|
||||
|
||||
#### Unsupported file formats
|
||||
**Supported Formats**:
|
||||
- Images: JPG, PNG, GIF, SVG, WebP
|
||||
- Documents: PDF, DOC, DOCX, XLS, XLSX, PPT, PPTX
|
||||
- Archives: ZIP, RAR, 7Z
|
||||
- Text: TXT, CSV, MD
|
||||
- Code: JS, HTML, CSS, JSON, XML
|
||||
|
||||
### 5. Integration Problems
|
||||
|
||||
#### Slack integration not working
|
||||
**Setup Requirements**:
|
||||
1. Slack workspace admin permissions
|
||||
2. TeamFlow Pro or Enterprise plan
|
||||
3. Proper webhook configuration
|
||||
|
||||
**Troubleshooting**:
|
||||
1. Verify Slack workspace URL is correct
|
||||
2. Check webhook permissions in Slack admin
|
||||
3. Test with simple message first
|
||||
4. Ensure both apps are updated to latest versions
|
||||
|
||||
#### GitHub integration issues
|
||||
**Common Problems**:
|
||||
- Repository access permissions
|
||||
- Webhook authentication failures
|
||||
- Branch protection rules blocking commits
|
||||
|
||||
**Solutions**:
|
||||
1. Verify GitHub personal access token has correct scopes
|
||||
2. Check repository permissions for TeamFlow app
|
||||
3. Review webhook logs in GitHub settings
|
||||
4. Test with public repository first
|
||||
|
||||
## Browser-Specific Issues
|
||||
|
||||
### Chrome
|
||||
- **File download issues**: Check download settings and blocked downloads
|
||||
- **Extension conflicts**: Disable ad blockers and privacy extensions temporarily
|
||||
|
||||
### Safari
|
||||
- **Cookie issues**: Enable cross-site tracking prevention exceptions
|
||||
- **Local storage**: Ensure not in private browsing mode
|
||||
|
||||
### Firefox
|
||||
- **Security settings**: Adjust strict enhanced tracking protection
|
||||
- **Add-on conflicts**: Test in safe mode
|
||||
|
||||
## Server Infrastructure
|
||||
|
||||
### Data Centers
|
||||
- **Primary**: AWS US-West-2 (Oregon)
|
||||
- **Secondary**: AWS EU-West-1 (Ireland)
|
||||
- **CDN**: CloudFlare global network
|
||||
|
||||
### Maintenance Windows
|
||||
- **Scheduled Maintenance**: Sundays 2:00-4:00 AM PST
|
||||
- **Emergency Maintenance**: As needed with 30-minute notice
|
||||
- **Status Updates**: status.teamflow.com and @TeamFlowStatus on Twitter
|
||||
|
||||
## Escalation Criteria
|
||||
|
||||
Escalate to Level 2 Support when:
|
||||
- Data loss or corruption suspected
|
||||
- Security breach indicators
|
||||
- API downtime affecting multiple customers
|
||||
- Integration partner (Slack, GitHub, etc.) reporting issues
|
||||
- Customer reports SLA violations
|
||||
- Enterprise customer experiencing any service disruption
|
||||
|
||||
## Diagnostic Tools
|
||||
|
||||
### Browser Developer Tools
|
||||
1. **Console Errors**: Check for JavaScript errors (F12 → Console)
|
||||
2. **Network Tab**: Monitor failed requests and response times
|
||||
3. **Application Tab**: Check local storage and cookies
|
||||
|
||||
### API Testing
|
||||
- Use Postman or curl to test API endpoints
|
||||
- Check response headers for rate limit information
|
||||
- Verify request format matches API documentation
|
||||
|
||||
### Mobile Debugging
|
||||
- iOS: Connect device to Xcode for detailed crash logs
|
||||
- Android: Enable developer options and use ADB logcat
|
||||
82
dexto/agents/triage-demo/escalation-agent.yml
Normal file
82
dexto/agents/triage-demo/escalation-agent.yml
Normal file
@@ -0,0 +1,82 @@
|
||||
# Escalation Agent Configuration
|
||||
# Handles complex issues requiring human intervention or management approval
|
||||
|
||||
systemPrompt:
|
||||
contributors:
|
||||
- id: base-prompt
|
||||
type: static
|
||||
priority: 0
|
||||
content: |
|
||||
You are a specialized Escalation Agent for TeamFlow, responsible for handling complex, sensitive, or high-priority issues that require management intervention.
|
||||
|
||||
Your primary responsibilities:
|
||||
- Manage escalated cases from other support agents
|
||||
- Handle Enterprise customer issues and urgent requests
|
||||
- Process complaints, disputes, and sensitive matters
|
||||
- Coordinate with management and specialized teams
|
||||
- Document incident reports and follow-up actions
|
||||
|
||||
Your approach:
|
||||
- Take detailed notes of the issue history and previous resolution attempts
|
||||
- Gather all relevant context and supporting documentation
|
||||
- Assess urgency level and potential business impact
|
||||
- Communicate clearly with both customers and internal teams
|
||||
- Follow up promptly on all escalated matters
|
||||
|
||||
Types of issues you handle:
|
||||
- Unresolved technical issues after multiple attempts
|
||||
- Billing disputes requiring management approval
|
||||
- Enterprise customer feature requests and contract issues
|
||||
- Security incidents and data privacy concerns
|
||||
- Legal or compliance-related inquiries (GDPR, SOC 2, etc.)
|
||||
- Customer complaints about service quality
|
||||
|
||||
You have access to comprehensive escalation policies, procedures, and contact information for TeamFlow's management team, including security incident protocols and legal compliance procedures.
|
||||
|
||||
Tools available to you:
|
||||
- Email and communication tools for coordinating with teams
|
||||
- Filesystem access for documentation and case management
|
||||
- Web research for regulatory and legal information
|
||||
|
||||
Remember: Maintain professionalism, document everything thoroughly, and ensure proper follow-up on all escalated cases according to TeamFlow's escalation policies.
|
||||
|
||||
- id: company-overview
|
||||
type: file
|
||||
priority: 10
|
||||
files:
|
||||
- "${{dexto.agent_dir}}/docs/company-overview.md"
|
||||
options:
|
||||
includeFilenames: true
|
||||
errorHandling: skip
|
||||
|
||||
- id: escalation-policies
|
||||
type: file
|
||||
priority: 20
|
||||
files:
|
||||
- "${{dexto.agent_dir}}/docs/escalation-policies.md"
|
||||
options:
|
||||
includeFilenames: true
|
||||
errorHandling: skip
|
||||
|
||||
mcpServers:
|
||||
filesystem:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- -y
|
||||
- "@modelcontextprotocol/server-filesystem"
|
||||
- .
|
||||
tavily:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- -y
|
||||
- tavily-mcp@0.1.3
|
||||
env:
|
||||
TAVILY_API_KEY: $TAVILY_API_KEY
|
||||
connectionMode: lenient
|
||||
|
||||
llm:
|
||||
provider: openai
|
||||
model: gpt-5
|
||||
apiKey: $OPENAI_API_KEY
|
||||
85
dexto/agents/triage-demo/product-info-agent.yml
Normal file
85
dexto/agents/triage-demo/product-info-agent.yml
Normal file
@@ -0,0 +1,85 @@
|
||||
# Product Information Agent Configuration
|
||||
# Specializes in product features, comparisons, and general information
|
||||
|
||||
systemPrompt:
|
||||
contributors:
|
||||
- id: base-prompt
|
||||
type: static
|
||||
priority: 0
|
||||
content: |
|
||||
You are a specialized Product Information Agent for TeamFlow, with comprehensive knowledge about our project management and team collaboration platform.
|
||||
|
||||
Your primary responsibilities:
|
||||
- Answer questions about TeamFlow's features, capabilities, and specifications
|
||||
- Provide product comparisons and recommendations between Basic, Pro, and Enterprise plans
|
||||
- Explain how to use specific features and functionalities
|
||||
- Share information about integrations and API capabilities
|
||||
- Guide users to appropriate documentation and resources
|
||||
|
||||
Your approach:
|
||||
- Provide accurate, up-to-date product information
|
||||
- Use clear, non-technical language when explaining complex features
|
||||
- Offer relevant examples and use cases
|
||||
- Suggest the best product tier or plan for user needs
|
||||
- Direct users to detailed documentation or demos when helpful
|
||||
|
||||
Key information to gather:
|
||||
- User's specific use case or requirements
|
||||
- Current product tier or plan (if applicable)
|
||||
- Specific features or functionality they're asking about
|
||||
- Their technical expertise level
|
||||
|
||||
You have access to comprehensive product documentation covering all TeamFlow features, integrations (Slack, GitHub, Salesforce, etc.), mobile apps, API capabilities, and plan comparisons.
|
||||
|
||||
Tools available to you:
|
||||
- Web research for latest product information and competitor analysis
|
||||
- Filesystem access to read product documentation and specs
|
||||
|
||||
Remember: Always provide accurate information about TeamFlow and acknowledge when you need to research or verify details.
|
||||
|
||||
- id: company-overview
|
||||
type: file
|
||||
priority: 10
|
||||
files:
|
||||
- "${{dexto.agent_dir}}/docs/company-overview.md"
|
||||
options:
|
||||
includeFilenames: true
|
||||
errorHandling: skip
|
||||
|
||||
- id: product-features
|
||||
type: file
|
||||
priority: 20
|
||||
files:
|
||||
- "${{dexto.agent_dir}}/docs/product-features.md"
|
||||
options:
|
||||
includeFilenames: true
|
||||
errorHandling: skip
|
||||
|
||||
mcpServers:
|
||||
tavily:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- -y
|
||||
- tavily-mcp@0.1.3
|
||||
env:
|
||||
TAVILY_API_KEY: $TAVILY_API_KEY
|
||||
connectionMode: lenient
|
||||
filesystem:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- -y
|
||||
- "@modelcontextprotocol/server-filesystem"
|
||||
- .
|
||||
playwright:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- -y
|
||||
- "@playwright/mcp@latest"
|
||||
|
||||
llm:
|
||||
provider: openai
|
||||
model: gpt-5-mini
|
||||
apiKey: $OPENAI_API_KEY
|
||||
70
dexto/agents/triage-demo/technical-support-agent.yml
Normal file
70
dexto/agents/triage-demo/technical-support-agent.yml
Normal file
@@ -0,0 +1,70 @@
|
||||
# Technical Support Agent Configuration
|
||||
# Specializes in technical issues, troubleshooting, and bug reports
|
||||
|
||||
systemPrompt:
|
||||
contributors:
|
||||
- id: base-prompt
|
||||
type: static
|
||||
priority: 0
|
||||
content: |
|
||||
You are a specialized Technical Support Agent for TeamFlow, a cloud-based project management and team collaboration platform.
|
||||
|
||||
Your primary responsibilities:
|
||||
- Diagnose and resolve technical problems, bugs, and system issues
|
||||
- Provide step-by-step troubleshooting guidance
|
||||
- Analyze error logs, system configurations, and performance issues
|
||||
- Escalate complex technical issues when necessary
|
||||
- Document common issues and their solutions
|
||||
|
||||
Your approach:
|
||||
- Always ask for specific details: error messages, system info, steps to reproduce
|
||||
- Provide clear, step-by-step instructions
|
||||
- Verify solutions work before considering the issue resolved
|
||||
- Be patient and explain technical concepts in simple terms
|
||||
- When unsure, ask clarifying questions or escalate to senior technical support
|
||||
|
||||
Tools available to you:
|
||||
- Filesystem access for log analysis and configuration checks
|
||||
- Terminal access for system diagnostics and troubleshooting commands
|
||||
|
||||
You have access to comprehensive technical documentation and troubleshooting guides for TeamFlow's platform, API, mobile apps, and integrations. Use this knowledge to provide accurate, specific solutions.
|
||||
|
||||
Remember: Your goal is to resolve technical issues efficiently while educating the user about TeamFlow's features and capabilities.
|
||||
|
||||
- id: company-overview
|
||||
type: file
|
||||
priority: 10
|
||||
files:
|
||||
- "${{dexto.agent_dir}}/docs/company-overview.md"
|
||||
options:
|
||||
includeFilenames: true
|
||||
errorHandling: skip
|
||||
|
||||
- id: technical-docs
|
||||
type: file
|
||||
priority: 20
|
||||
files:
|
||||
- "${{dexto.agent_dir}}/docs/technical-documentation.md"
|
||||
options:
|
||||
includeFilenames: true
|
||||
errorHandling: skip
|
||||
|
||||
mcpServers:
|
||||
filesystem:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- -y
|
||||
- "@modelcontextprotocol/server-filesystem"
|
||||
- .
|
||||
playwright:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- -y
|
||||
- "@playwright/mcp@latest"
|
||||
|
||||
llm:
|
||||
provider: openai
|
||||
model: gpt-5
|
||||
apiKey: $OPENAI_API_KEY
|
||||
209
dexto/agents/triage-demo/test-scenarios.md
Normal file
209
dexto/agents/triage-demo/test-scenarios.md
Normal file
@@ -0,0 +1,209 @@
|
||||
# TeamFlow Triage Agent Test Scenarios
|
||||
|
||||
Use these realistic TeamFlow customer support scenarios to test the triage agent's **complete customer support workflow**. The triage agent will analyze each request, route to the appropriate specialist agent, execute the specialist via MCP tools, and provide complete customer responses.
|
||||
|
||||
## 🔧 Technical Support Scenarios
|
||||
|
||||
### Scenario T1: API Integration Issue
|
||||
```
|
||||
Hi, I'm trying to integrate the TeamFlow API with our system but I keep getting a 401 unauthorized error even though I'm using the correct API key. I've checked the documentation but can't figure out what's wrong. Our rate limit should be 10,000/hour on our Pro plan. Can you help?
|
||||
```
|
||||
**Expected Route**: Technical Support Agent
|
||||
**Expected Response**: Complete troubleshooting guide including API key validation steps, common 401 causes, rate limit verification, and Pro plan API specifications
|
||||
**Tool Execution**: `chat_with_agent` → Technical Support provides detailed debugging steps
|
||||
|
||||
### Scenario T2: App Crash
|
||||
```
|
||||
My TeamFlow mobile app crashes every time I try to export project data. It worked fine last week but now it just freezes and closes. I'm using iPhone 15 with iOS 17.2. This is really urgent as I need this data for a client presentation tomorrow.
|
||||
```
|
||||
**Expected Route**: Technical Support Agent
|
||||
**Expected Response**: Complete crash resolution including device-specific troubleshooting, export alternatives, and immediate workarounds for urgent timeline
|
||||
**Tool Execution**: `chat_with_agent` → Technical Support provides iOS-specific fixes and emergency data export options
|
||||
|
||||
### Scenario T3: Performance Issue
|
||||
```
|
||||
Your web dashboard has been extremely slow for the past 3 days. Pages take 30+ seconds to load and sometimes timeout completely. My internet connection is fine and other websites work normally.
|
||||
```
|
||||
**Expected Route**: Technical Support Agent
|
||||
**Expected Response**: Complete performance troubleshooting including browser optimization, cache clearing, system status check, and escalation to infrastructure team if needed
|
||||
**Tool Execution**: `chat_with_agent` → Technical Support provides systematic performance diagnosis steps
|
||||
|
||||
## 💳 Billing Support Scenarios
|
||||
|
||||
### Scenario B1: Double Charge
|
||||
```
|
||||
I just checked my credit card statement and I was charged twice for this month's subscription - once on the 1st for $49.99 and again on the 3rd for the same amount. I need the duplicate charge refunded immediately.
|
||||
```
|
||||
**Expected Route**: Billing Agent
|
||||
**Expected Response**: Complete refund process including charge verification, refund timeline (3-5 business days), and account credit options for immediate resolution
|
||||
**Tool Execution**: `chat_with_agent` → Billing Agent provides specific refund procedures and account investigation steps
|
||||
|
||||
### Scenario B2: Subscription Management
|
||||
```
|
||||
I want to upgrade from the Basic plan to Pro plan but I'm confused about the pricing. Will I be charged the full Pro amount or just the difference? Also, when would the upgrade take effect?
|
||||
```
|
||||
**Expected Route**: Billing Agent
|
||||
**Expected Response**: Complete upgrade explanation including prorated billing calculation, immediate feature access, next billing cycle details, and upgrade procedure
|
||||
**Tool Execution**: `chat_with_agent` → Billing Agent provides detailed prorated pricing explanation and upgrade process
|
||||
|
||||
### Scenario B3: Payment Failure
|
||||
```
|
||||
My payment failed this morning and now my account is suspended. I updated my credit card last week so I'm not sure why it didn't work. How can I get my account reactivated quickly?
|
||||
```
|
||||
**Expected Route**: Billing Agent
|
||||
**Expected Response**: Complete reactivation process including payment method verification, retry options, account status restoration timeline, and prevention steps
|
||||
**Tool Execution**: `chat_with_agent` → Billing Agent provides immediate account reactivation steps and payment troubleshooting
|
||||
|
||||
## 📖 Product Information Scenarios
|
||||
|
||||
### Scenario P1: Feature Comparison
|
||||
```
|
||||
What's the difference between TeamFlow's Pro and Enterprise plans? I specifically need to know about API rate limits, user management features, and data export capabilities. We're a team of 25 people and currently on the Basic plan.
|
||||
```
|
||||
**Expected Route**: Product Info Agent
|
||||
**Expected Response**: Complete plan comparison including detailed feature matrix, specific API limits (Pro: 10K/hour, Enterprise: 100K/hour), user management differences, and upgrade recommendation for 25-person team
|
||||
**Tool Execution**: `chat_with_agent` → Product Info Agent provides comprehensive plan comparison with team-size specific recommendations
|
||||
|
||||
### Scenario P2: How-To Question
|
||||
```
|
||||
How do I set up automated reports to be sent to my team every Monday? I see the reporting feature but can't figure out how to schedule them. Is this available in my current plan?
|
||||
```
|
||||
**Expected Route**: Product Info Agent
|
||||
**Expected Response**: Complete setup guide including step-by-step report scheduling instructions, plan feature verification, and links to relevant documentation
|
||||
**Tool Execution**: `chat_with_agent` → Product Info Agent provides detailed automated reporting setup walkthrough
|
||||
|
||||
### Scenario P3: Integration Capabilities
|
||||
```
|
||||
Does TeamFlow integrate with Salesforce and Slack? I need to sync customer project data and get notifications in our Slack channels. What's the setup process like and are there any limitations I should know about? We're on the Pro plan.
|
||||
```
|
||||
**Expected Route**: Product Info Agent
|
||||
**Expected Response**: Complete integration overview including supported Salesforce/Slack features, Pro plan limitations, setup documentation links, and configuration best practices
|
||||
**Tool Execution**: `chat_with_agent` → Product Info Agent provides comprehensive integration capabilities and setup guidance
|
||||
|
||||
## 🚨 Escalation Scenarios
|
||||
|
||||
### Scenario E1: Legal Threat
|
||||
```
|
||||
This is my fourth email about data privacy violations. Your service exposed my customer data to unauthorized parties and I'm considering legal action. I need to speak with a manager immediately about this data breach.
|
||||
```
|
||||
**Expected Route**: Escalation Agent
|
||||
**Expected Response**: Complete escalation including immediate management contact information, legal/compliance team connection, incident escalation procedure, and 2-hour response commitment
|
||||
**Tool Execution**: `chat_with_agent` → Escalation Agent provides senior management contact and legal compliance escalation process
|
||||
|
||||
### Scenario E2: Business Impact
|
||||
```
|
||||
Your system outage yesterday caused my e-commerce site to be down for 6 hours during Black Friday. This resulted in approximately $50,000 in lost sales. I need compensation for this business interruption and want to discuss SLA violations.
|
||||
```
|
||||
**Expected Route**: Escalation Agent
|
||||
**Expected Response**: Complete business impact assessment including SLA review, compensation evaluation process, senior account manager contact, and formal incident investigation
|
||||
**Tool Execution**: `chat_with_agent` → Escalation Agent provides business impact claim process and executive contact information
|
||||
|
||||
### Scenario E3: Service Quality Complaint
|
||||
```
|
||||
I've been a customer for 3 years and the service quality has declined dramatically. Multiple support tickets have been ignored, features are constantly broken, and I'm considering switching to a competitor. I want to speak with someone who can actually resolve these ongoing issues.
|
||||
```
|
||||
**Expected Route**: Escalation Agent
|
||||
**Expected Response**: Complete retention process including account review, senior support contact, service improvement plan, and customer success manager assignment
|
||||
**Tool Execution**: `chat_with_agent` → Escalation Agent provides customer retention specialist contact and service quality improvement plan
|
||||
|
||||
## 🤔 Mixed/Complex Scenarios
|
||||
|
||||
### Scenario M1: Technical + Billing
|
||||
```
|
||||
My API requests started failing yesterday with 429 rate limit errors, but I'm on the Pro plan which should have higher limits. Did my plan get downgraded? I'm still being charged the Pro price but getting Basic plan limits.
|
||||
```
|
||||
**Expected Route**: Technical Support Agent (primary) or Billing Agent
|
||||
**Expected Response**: Complete investigation including API limit verification, account status check, billing verification, and either technical resolution or billing escalation
|
||||
**Tool Execution**: `chat_with_agent` → Technical Support investigates API limits and coordinates with billing if needed
|
||||
|
||||
### Scenario M2: Product + Escalation
|
||||
```
|
||||
I was promised during the sales call that your Enterprise plan includes custom integrations. However, after upgrading, I'm being told this requires an additional $10,000 implementation fee. This contradicts what I was told by your sales team.
|
||||
```
|
||||
**Expected Route**: Escalation Agent
|
||||
**Expected Response**: Complete sales promise review including sales team consultation, Enterprise feature verification, implementation fee clarification, and senior sales manager contact
|
||||
**Tool Execution**: `chat_with_agent` → Escalation Agent provides sales promise investigation and senior management contact
|
||||
|
||||
### Scenario M3: Vague Request
|
||||
```
|
||||
Hi, I'm having trouble with your service. Can you help me?
|
||||
```
|
||||
**Expected Route**: Should ask for clarification before routing
|
||||
**Expected Response**: Polite clarification request with specific questions to help identify the issue type and appropriate specialist
|
||||
**Tool Execution**: Triage agent asks clarifying questions without executing specialist tools
|
||||
|
||||
## 🎯 Testing Instructions
|
||||
|
||||
### Interactive Testing
|
||||
|
||||
1. **Start the complete triage system**:
|
||||
```bash
|
||||
npx dexto --agent agents/triage-demo/triage-agent.yml
|
||||
```
|
||||
|
||||
2. **Copy and paste** scenarios from above into the chat
|
||||
|
||||
3. **Observe the complete workflow**:
|
||||
- **Routing analysis** (which specialist is chosen and why)
|
||||
- **Tool execution** (`chat_with_agent` tool calls)
|
||||
- **Complete customer response** (routing confirmation + specialist answer)
|
||||
- **Response quality** (specificity, completeness, helpfulness)
|
||||
|
||||
### One-Shot Testing
|
||||
|
||||
Test scenarios quickly with command-line execution:
|
||||
|
||||
```bash
|
||||
# Test Technical Support scenario
|
||||
npx dexto --agent agents/triage-demo/triage-agent.yml "My TeamFlow mobile app crashes every time I try to export project data. I'm using iPhone 15 with iOS 17.2. This is urgent."
|
||||
|
||||
# Test Billing scenario
|
||||
npx dexto --agent agents/triage-demo/triage-agent.yml "I want to upgrade from Basic to Pro but confused about pricing. Will I be charged the full amount?"
|
||||
|
||||
# Test Product Info scenario
|
||||
npx dexto --agent agents/triage-demo/triage-agent.yml "What's the difference between Pro and Enterprise plans? I need API access for 25 people."
|
||||
|
||||
# Test Escalation scenario
|
||||
npx dexto --agent agents/triage-demo/triage-agent.yml "Your system outage cost my business $50,000 in lost sales. I need compensation and want to discuss SLA violations."
|
||||
```
|
||||
|
||||
### Expected Response Quality
|
||||
|
||||
For each test, verify that responses include:
|
||||
|
||||
1. **Brief routing confirmation** (one sentence about which specialist was consulted)
|
||||
2. **Complete specialist answer** with specific, actionable information
|
||||
3. **Relevant details** from TeamFlow's business documentation
|
||||
4. **Appropriate tone** (professional, helpful, empathetic when needed)
|
||||
5. **Follow-up invitation** (offering additional help if needed)
|
||||
|
||||
## 📊 Expected Results Summary
|
||||
|
||||
| Category | Count | Expected Workflow |
|
||||
|----------|-------|-------------------|
|
||||
| Technical | 3 | Route → Execute Technical Support → Complete troubleshooting response |
|
||||
| Billing | 3 | Route → Execute Billing Agent → Complete billing/payment resolution |
|
||||
| Product Info | 3 | Route → Execute Product Info Agent → Complete feature/plan information |
|
||||
| Escalation | 3 | Route → Execute Escalation Agent → Complete escalation with contacts |
|
||||
| Mixed/Complex | 3 | Route → Execute Primary Agent → Complete investigation/resolution |
|
||||
|
||||
## 🔍 Success Criteria
|
||||
|
||||
The triage system should demonstrate:
|
||||
|
||||
- **95%+ routing accuracy** to appropriate specialist agents
|
||||
- **100% tool execution** success (no failed `chat_with_agent` calls)
|
||||
- **Complete responses** that directly address customer needs
|
||||
- **Professional tone** with empathy for customer situations
|
||||
- **Specific information** from TeamFlow business context (plans, policies, features)
|
||||
- **Clear next steps** for customer resolution
|
||||
|
||||
## 🚫 Common Issues to Watch For
|
||||
|
||||
- **Routing without execution**: Agent identifies correct specialist but doesn't call `chat_with_agent`
|
||||
- **Tool confirmation prompts**: Should auto-approve due to configuration
|
||||
- **Incomplete responses**: Missing specialist answers or generic routing messages
|
||||
- **Wrong specialist**: Incorrect routing based on request analysis
|
||||
- **Multiple tool calls**: Unnecessary repeated calls to specialists
|
||||
|
||||
The complete triage system should provide **seamless, professional customer support** that customers would expect from a real enterprise support team!
|
||||
187
dexto/agents/triage-demo/triage-agent.yml
Normal file
187
dexto/agents/triage-demo/triage-agent.yml
Normal file
@@ -0,0 +1,187 @@
|
||||
# Customer Support Triage Agent Configuration
|
||||
# Main coordination agent that routes requests to specialized support agents
|
||||
|
||||
# Optional greeting shown at chat start (UI can consume this)
|
||||
greeting: "🎯 Hello! I'm your Support Triage Agent. How can I help you today?"
|
||||
|
||||
systemPrompt:
|
||||
contributors:
|
||||
- id: base-prompt
|
||||
type: static
|
||||
priority: 0
|
||||
content: |
|
||||
You are an intelligent Customer Support Triage Agent for TeamFlow, responsible for analyzing incoming customer requests and routing them to the most appropriate specialized support agent.
|
||||
|
||||
## Your Core Mission
|
||||
Quickly analyze each customer inquiry to determine:
|
||||
1. The primary issue category
|
||||
2. Urgency level
|
||||
3. Which specialized agent should handle it
|
||||
4. Any immediate information needed for effective routing
|
||||
|
||||
## Available Specialized Agents
|
||||
|
||||
**Technical Support Agent** - Route here for:
|
||||
- Bug reports, error messages, system failures
|
||||
- API integration problems, technical troubleshooting
|
||||
- Performance problems, crashes, connectivity issues
|
||||
- Mobile app issues, browser compatibility problems
|
||||
- Integration issues (Slack, GitHub, Salesforce, etc.)
|
||||
|
||||
**Billing Agent** - Route here for:
|
||||
- Payment failures, billing questions, invoice disputes
|
||||
- Plan changes (Basic $9/month, Pro $19/month, Enterprise $39/month)
|
||||
- Refund requests, pricing inquiries
|
||||
- Account billing setup and payment method issues
|
||||
- Subscription cancellations or upgrades
|
||||
|
||||
**Product Info Agent** - Route here for:
|
||||
- Feature questions, product capabilities, specifications
|
||||
- How-to questions, usage guidance, best practices
|
||||
- Plan comparisons and recommendations
|
||||
- Integration capabilities and setup guidance
|
||||
- General product information and documentation requests
|
||||
|
||||
**Escalation Agent** - Route here for:
|
||||
- Unresolved issues after specialist attempts
|
||||
- Enterprise customer requests and contract issues
|
||||
- Complaints about service quality or agent performance
|
||||
- Legal, compliance, or security-related inquiries (GDPR, SOC 2)
|
||||
- Issues requiring management approval or special handling
|
||||
|
||||
## Your Triage Process
|
||||
|
||||
1. **Analyze the Request**: Read the customer's message carefully
|
||||
2. **Categorize**: Determine the primary issue type and any secondary concerns
|
||||
3. **Assess Urgency**: Is this urgent, normal, or low priority?
|
||||
4. **Route Intelligently**: Choose the best-suited specialist agent
|
||||
5. **Provide Context**: Give the specialist agent relevant background
|
||||
|
||||
## Routing Guidelines
|
||||
|
||||
- **Multiple Issues**: Route to the agent handling the most critical/urgent aspect
|
||||
- **Unclear Requests**: Ask clarifying questions before routing
|
||||
- **Previous Escalations**: Route directly to Escalation Agent if this is a follow-up
|
||||
- **Enterprise Customers**: Consider escalation for Enterprise plan customers
|
||||
- **Time-Sensitive**: Prioritize billing issues near payment dates, urgent technical failures
|
||||
|
||||
## Your Response Format
|
||||
|
||||
When routing a request, provide:
|
||||
1. Brief analysis of the issue
|
||||
2. Which agent you're routing to and why
|
||||
3. Any additional context the specialist agent should know
|
||||
4. Expected resolution timeframe (if applicable)
|
||||
|
||||
You have access to TeamFlow's company information to help with context and routing decisions.
|
||||
|
||||
Remember: You are the first line of intelligent support. Your accurate routing ensures TeamFlow customers get expert help quickly and efficiently.
|
||||
|
||||
## Tool Usage Instructions
|
||||
|
||||
After you decide which specialist should handle the inquiry, you MUST:
|
||||
1. Call the `chat_with_agent` tool with the full customer message as the `message` argument. The runtime will automatically route this call to the correct specialist agent based on the current connection mapping.
|
||||
2. Wait for the tool to return the specialist agent’s answer.
|
||||
3. Respond back to the customer with a concise helpful answer that includes:
|
||||
- A short confirmation of the routing you performed (one sentence max).
|
||||
- The detailed answer from the specialist agent.
|
||||
|
||||
Only use `chat_with_agent` once per customer request unless follow-up questions arise.
|
||||
|
||||
- id: company-overview
|
||||
type: file
|
||||
priority: 10
|
||||
files:
|
||||
- "${{dexto.agent_dir}}/docs/company-overview.md"
|
||||
options:
|
||||
includeFilenames: true
|
||||
errorHandling: skip
|
||||
|
||||
# Auto-approve tool executions so the triage agent can seamlessly delegate tasks
|
||||
|
||||
toolConfirmation:
|
||||
mode: auto-approve
|
||||
allowedToolsStorage: memory
|
||||
|
||||
mcpServers:
|
||||
# Filesystem for logging and case management
|
||||
filesystem:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- -y
|
||||
- "@modelcontextprotocol/server-filesystem"
|
||||
- .
|
||||
|
||||
# Web research for understanding customer context and company info
|
||||
tavily:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- -y
|
||||
- tavily-mcp@0.1.3
|
||||
env:
|
||||
TAVILY_API_KEY: $TAVILY_API_KEY
|
||||
connectionMode: lenient
|
||||
|
||||
# Specialized support agents running as MCP servers via npx
|
||||
technical_support:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- dexto
|
||||
- --mode
|
||||
- mcp
|
||||
- --agent
|
||||
- "${{dexto.agent_dir}}/technical-support-agent.yml"
|
||||
connectionMode: lenient
|
||||
|
||||
billing_support:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- dexto
|
||||
- --mode
|
||||
- mcp
|
||||
- --agent
|
||||
- "${{dexto.agent_dir}}/billing-agent.yml"
|
||||
connectionMode: lenient
|
||||
|
||||
product_info:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- dexto
|
||||
- --mode
|
||||
- mcp
|
||||
- --agent
|
||||
- "${{dexto.agent_dir}}/product-info-agent.yml"
|
||||
connectionMode: lenient
|
||||
|
||||
escalation:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- dexto
|
||||
- --mode
|
||||
- mcp
|
||||
- --agent
|
||||
- "${{dexto.agent_dir}}/escalation-agent.yml"
|
||||
connectionMode: lenient
|
||||
|
||||
# Storage configuration
|
||||
storage:
|
||||
cache:
|
||||
type: in-memory
|
||||
database:
|
||||
type: sqlite
|
||||
blob:
|
||||
type: local # CLI provides storePath automatically
|
||||
maxBlobSize: 52428800 # 50MB per blob
|
||||
maxTotalSize: 1073741824 # 1GB total storage
|
||||
cleanupAfterDays: 30
|
||||
|
||||
llm:
|
||||
provider: openai
|
||||
model: gpt-5
|
||||
apiKey: $OPENAI_API_KEY
|
||||
Reference in New Issue
Block a user