Overview
Automatically create Zendesk support tickets when conversations need human attention, seamlessly integrating AI support with your existing ticketing system.Requirements
- Active Zendesk account
- Zendesk integration connected (see Integration Setup below)
- API token with ticket creation permissions
- Appropriate support group assignments
Setup Instructions
Step 1: Connect Zendesk Integration
Zendesk Integration
Connect your Zendesk account first
Step 2: Create Escalation Path
- Navigate to Agents → Your Agent → Escalations
- Click “Create Escalation Path”
- Fill in the basic information:
- Name: Descriptive name (e.g., “Zendesk Support Tickets”)
- Platform: Select “Zendesk”
- Platform Integration: Choose your connected Zendesk account
Step 3: Configure Zendesk Settings
Configure ticket creation settings:- Default Priority: normal, low, high, or urgent
- Default Type: question, incident, problem, or task
- Tags (optional): Auto-apply tags (e.g., “ai-escalation”, “chatbot”)
- Group ID (optional): Assign to specific support group
- Subject Template (optional): Custom ticket subject format
Step 4: Set Up Triggers (Optional)
Choose when to automatically escalate:- Manual Only: Only when customer requests or AI determines need
- Message Count: After specific number of messages
- Keywords: When certain words detected
Step 5: Save Configuration
Click “Save” to create the escalation path.Configuration Options
| Option | Description | Required | Values |
|---|---|---|---|
| Default Priority | Ticket priority level | Yes | low, normal, high, urgent |
| Default Type | Ticket type | Yes | question, incident, problem, task |
| Tags | Comma-separated tags | No | Any string |
| Group ID | Zendesk group to assign | No | Numeric ID |
| Subject Template | Custom subject format | No | Text with variables |
Priority Levels
Choose the appropriate priority for escalated tickets:- Low: General inquiries, non-urgent questions
- Normal: Standard support requests (default)
- High: Important issues needing prompt attention
- Urgent: Critical issues requiring immediate response
Ticket Types
Select the appropriate type:- Question: General customer inquiries
- Incident: Service disruptions or errors
- Problem: Root cause of multiple incidents
- Task: Work items or requests
Subject Template
Customize the ticket subject line:Available Variables
{{customer_name}}: Customer’s name or identifier{{channel_name}}: Communication channel{{escalation_reason}}: Why escalated{{agent_name}}: AI agent name{{timestamp}}: When escalated
Ticket Content
The ticket description automatically includes:- Escalation Reason: Why the conversation was escalated
- Channel: Where the conversation took place (Live Chat, SMS, etc.)
- Full Transcript: Complete conversation history
- Customer Information: Name, email, identifier
- Timestamp: When escalation occurred
- Link to Conversation: Direct link in Support Unicorn
Tags
Use tags to categorize and track AI escalations: Common Tags:ai-escalation: Identifies AI-escalated ticketschatbot: Originated from chatbotchannel-livechat/channel-sms: Indicates channelbilling,technical,sales: Topic categories
ai-escalation, chatbot, channel-livechat, billing
Group Assignment
Assign tickets to specific Zendesk groups:-
Find your group ID in Zendesk:
- Go to Admin → People → Groups
- Click on a group
- Group ID is in the URL:
.../groups/[GROUP_ID]/edit
- Enter the Group ID in escalation settings
- Tier 1 Support:
123456 - Billing Team:
234567 - Technical Support:
345678
Escalation Triggers
Manual Only
Create ticket only when:- Customer explicitly requests human help
- AI determines it cannot assist
Message Count Trigger
Create ticket after specific number of messages. Use Case: If conversation exceeds 5 messages, AI may not be resolving the issue.Keyword Trigger
Create ticket when keywords detected. Example Keywords:- Billing: “refund”, “charge”, “billing”
- Technical: “error”, “broken”, “not working”
- Escalation: “manager”, “complaint”
How It Works
When escalation is triggered:- Ticket Created: New ticket created in Zendesk
- AI Pauses: AI agent stops responding
- Agent Assigned: Ticket routed per Zendesk rules
- Context Included: Full conversation in ticket description
- Notification Sent: Agent receives Zendesk notification
- Human Response: Agent responds through Zendesk
Managing Zendesk Escalations
Test Connection
- Navigate to Agents → Your Agent → Escalations
- Find your Zendesk escalation path
- Click “Test Connection”
- Verify test ticket appears in Zendesk
Activate/Deactivate
Toggle the “Active” switch to enable or disable the escalation path.Edit Settings
- Navigate to Agents → Your Agent → Escalations
- Click the Zendesk escalation path
- Update configuration
- Click “Save Changes”
Best Practices
- Clear Tagging: Use consistent tags for reporting and filtering
- Appropriate Priority: Set realistic default priorities
- Group Assignment: Route to appropriate teams
- Subject Templates: Include key information in subject
- SLA Monitoring: Track response times for escalated tickets
- Regular Review: Analyze escalation patterns to improve AI
Example Use Cases
Use Case 1: Billing Issues
Configuration:- Priority: High
- Type: Question
- Tags:
ai-escalation, billing, urgent - Group: Billing Team (ID: 234567)
- Trigger: Keywords (“refund”, “charge”, “billing”)
Use Case 2: Technical Problems
Configuration:- Priority: Normal
- Type: Incident
- Tags:
ai-escalation, technical, bug - Group: Technical Support (ID: 345678)
- Trigger: Keywords (“error”, “broken”, “not working”)
Use Case 3: General Escalations
Configuration:- Priority: Normal
- Type: Question
- Tags:
ai-escalation, general - Group: Tier 1 Support (ID: 123456)
- Trigger: Message count > 5
Using in Procedures
Reference the escalation path in AI procedures:Procedures Guide
Learn how to use escalations in procedures
Troubleshooting
Tickets Not Being Created
- Verify Zendesk integration is connected and active
- Check API token has ticket creation permissions
- Ensure escalation path is activated
- Test connection using “Test Connection” button
- Review Zendesk API logs for errors
Tickets Created in Wrong Group
- Verify Group ID is correct
- Check that group exists in Zendesk
- Ensure API user has permission to assign to group
- Review Zendesk automation rules (may override)
Tags Not Applied
- Verify tag syntax (comma-separated, no special chars)
- Check Zendesk tag permissions
- Ensure tags don’t conflict with Zendesk triggers
Missing Conversation Context
- Verify escalation template includes transcript
- Check webhook configuration
- Review escalation service logs