Support-to-Eng Escalator
Bridge support and engineering. Given an Intercom conversation, pull context, attempt reproduction, file a Jira issue, and notify the team — end to end.
How to invoke
Provide:
- Intercom conversation ID (required)
- Jira project key for the engineering project (e.g.
ENG, BACKEND)
- Slack channel for support notifications (e.g.
#support-escalations)
Process
1. Pull the conversation from Intercom
Extract:
- Customer name, plan tier, and account ID
- Environment details (browser, OS, app version, region)
- Any attached logs, error messages, or screenshots
- Support rep's notes and tags
- Timeline of the issue
2. Attempt reproduction in the session environment
- Follow the steps described by the customer exactly
- Capture the minimal triggering command, request payload, or UI flow
- If repro succeeds: record the exact reproducing case
- If repro fails: document every variation attempted and why each failed
Never file a vague "cannot reproduce" issue. If you can't repro, list what you tried.
3. Create the Jira issue
Fields to set:
- Summary: concise, specific (e.g. "Checkout fails with 500 when cart has >10 items on Pro plan")
- Description: customer context, minimal repro steps, environment, suspected component (from code search)
- Links: Intercom conversation URL, any relevant GitHub commits or PRs
- Labels:
customer-reported, plan tier, component
- Priority: based on plan tier + user impact (P1 for Enterprise/data-loss, P2 for paying users, P3 for free)
4. Notify the support Slack channel
Post a single message:
- Conversation escalated ✅
- Jira issue link
- One-sentence severity assessment
- Tag the on-call engineer if P1
5. Update the Intercom conversation
- Add an internal note with the Jira link
- Mark the conversation as escalated
- Set the next follow-up reminder
Output summary
After completing all steps, reply with:
Escalation complete:
- Jira: [PROJ-XXX](link) — [Summary]
- Slack: notified #channel
- Intercom: internal note added, marked escalated
- Repro: [success / failed — tried: X, Y, Z]
Requirements
- Intercom MCP required. Configure at
https://mcp.intercom.com/mcp.
- Atlassian MCP required for Jira. Configure at
https://mcp.atlassian.com/v1/mcp.
- Slack MCP required for notifications. Configure at
https://mcp.slack.com/mcp.
1---2name: support-escalator3description: Reads an Intercom conversation, reproduces the bug, and files a linked Jira issue with repro steps.4---56# Support-to-Eng Escalator78Bridge support and engineering. Given an Intercom conversation, pull context, attempt reproduction, file a Jira issue, and notify the team — end to end.910## How to invoke1112Provide:13- **Intercom conversation ID** (required)14- **Jira project key** for the engineering project (e.g. `ENG`, `BACKEND`)15- **Slack channel** for support notifications (e.g. `#support-escalations`)1617## Process1819### 1. Pull the conversation from Intercom20Extract:21- Customer name, plan tier, and account ID22- Environment details (browser, OS, app version, region)23- Any attached logs, error messages, or screenshots24- Support rep's notes and tags25- Timeline of the issue2627### 2. Attempt reproduction in the session environment28- Follow the steps described by the customer exactly29- Capture the minimal triggering command, request payload, or UI flow30- If repro succeeds: record the exact reproducing case31- If repro fails: document every variation attempted and why each failed3233**Never file a vague "cannot reproduce" issue.** If you can't repro, list what you tried.3435### 3. Create the Jira issue36Fields to set:37- **Summary**: concise, specific (e.g. "Checkout fails with 500 when cart has >10 items on Pro plan")38- **Description**: customer context, minimal repro steps, environment, suspected component (from code search)39- **Links**: Intercom conversation URL, any relevant GitHub commits or PRs40- **Labels**: `customer-reported`, plan tier, component41- **Priority**: based on plan tier + user impact (P1 for Enterprise/data-loss, P2 for paying users, P3 for free)4243### 4. Notify the support Slack channel44Post a single message:45- Conversation escalated ✅46- Jira issue link47- One-sentence severity assessment48- Tag the on-call engineer if P14950### 5. Update the Intercom conversation51- Add an internal note with the Jira link52- Mark the conversation as escalated53- Set the next follow-up reminder5455## Output summary5657After completing all steps, reply with:58```59Escalation complete:60- Jira: [PROJ-XXX](link) — [Summary]61- Slack: notified #channel62- Intercom: internal note added, marked escalated63- Repro: [success / failed — tried: X, Y, Z]64```6566## Requirements6768- **Intercom MCP** required. Configure at `https://mcp.intercom.com/mcp`.69- **Atlassian MCP** required for Jira. Configure at `https://mcp.atlassian.com/v1/mcp`.70- **Slack MCP** required for notifications. Configure at `https://mcp.slack.com/mcp`.