# Zendesk Ticket Escalation to Slack

> Get critical support tickets in front of your team instantly. No more missed escalations buried in a queue.

Source: https://cotera.co/solutions/support/zendesk-ticket-escalation-slack

---

- **Team:** Support
- **Tools:** Zendesk, Slack
- **Difficulty:** medium
- **Setup time:** 10 min
- **Time saved:** 1 hr/day

## How it works
1. **Smart Escalation** — Flag tickets by priority, keywords, and customer tier
2. **Slack Alerts** — Post formatted, scannable alerts to any channel
3. **Auto-Tag Tickets** — Mark escalated tickets so they aren't re-flagged
4. **Audit Trail** — Add internal comments with escalation timestamps

## Example requests
- Escalate all urgent tickets from the last hour to #support-critical
- Post enterprise customer P1 and P2 tickets to #vip-support
- Alert #on-call about any ticket mentioning outage or data loss

## Prompt

```markdown
## Task

Monitor Zendesk tickets for high-priority or escalation-worthy issues and automatically post structured alerts to a Slack channel using @Slack/Send Message. After posting, tag the Zendesk ticket with an escalation marker using @Zendesk/Update Tickets so the same ticket doesn't get flagged twice.

**Example:** When a P1 ticket comes in about a production outage, post a formatted alert to #support-escalations with ticket details, customer info, and a direct link.

## Input

The user will provide:
1. Ticket data (individual ticket or a batch of recent tickets)
2. Slack channel for escalation alerts (e.g., #support-escalations)
3. Escalation criteria (priority level, keywords, customer tier, or SLA breach)

**Example:** "Escalate any P1 or P2 tickets from enterprise customers to #critical-support"

## Context

### Escalation Criteria

**Auto-escalate when:**
- Priority is "urgent" or "high"
- Customer is on an enterprise or premium plan
- Ticket has been open longer than the SLA threshold
- Keywords like "outage," "data loss," "security," or "billing error" appear
- Multiple tickets from the same customer in a short window

**Include in the Slack alert:**
- Ticket ID and subject line
- Customer name and account tier
- Priority level and current status
- Brief summary of the issue (2-3 sentences max)
- Time since ticket was created
- Direct link to the Zendesk ticket

### Escalation Strategy

1. Review ticket details against escalation criteria
2. Format a concise, scannable Slack message with key details
3. Post to the designated Slack channel
4. Tag the Zendesk ticket with "escalated" and "slack-notified" so it isn't re-flagged
5. Add an internal comment noting the escalation

### What Makes a Good Escalation Alert

- Scannable at a glance — use bold headers and bullet points
- Includes enough context to act without clicking through
- Tags the right severity so on-call knows whether to drop everything
- Links directly to the ticket for one-click access

## Output

**Slack Alert Format:**

🚨 **Escalation Alert — Ticket #[ID]**

**Subject:** [Ticket subject]
**Customer:** [Name] ([Account tier])
**Priority:** [Urgent/High]
**Status:** [Open/Pending]
**Age:** [Time since created]

**Summary:**
[2-3 sentence description of the issue]

**🔗 View Ticket:** [Zendesk link]

---

**Zendesk Updates Applied:**
- Added tags: escalated, slack-notified
- Internal comment: "Escalated to [#channel] on [date/time]"

---

**Escalation Summary:**

| Ticket | Customer | Priority | Channel | Status |
|--------|----------|----------|---------|--------|
| #[ID] | [Name] | Urgent | #support-escalations | Notified |
```

## Related reading
- [Slack Bot Customer Support Guide](https://cotera.co/articles/slack-bot-customer-support-guide.md)
- [Slack Chatbot Customer Support](https://cotera.co/articles/slack-chatbot-customer-support.md)
- [AI Customer Support Shopify](https://cotera.co/articles/ai-customer-support-shopify.md)