Menu
Find and flag duplicate or related [Gorgias](https://composio.dev/toolkits/gorgias) tickets that should be merged
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Automatically analyze and tag untagged [Gorgias](https://composio.dev/toolkits/gorgias) tickets based on content.
Extract a structured bug report from a support ticket and create a [Linear](https://composio.dev/toolkits/linear) issue.
Summarize customer support/sales calls from [Dialpad](https://composio.dev/toolkits/dialpad) or [Leexi](https://composio.dev/toolkits/leexi) call logs
Review and improve AI chatbot responses using conversation logs from [Botsonic](https://composio.dev/toolkits/botsonic), [Docsbot](https://composio.dev/toolkits/docsbot-ai), or [Landbot](https://composio.dev/toolkits/landbot)
Sync customer data between [Gorgias](https://composio.dev/toolkits/gorgias) and [HubSpot](https://composio.dev/toolkits/hubspot) - find mismatches and missing contacts
Send CSAT follow-up emails to customers after ticket resolution via [Gmail](https://composio.dev/toolkits/gmail)
| name | merge-tickets |
| description | Find and flag duplicate or related [Gorgias](https://composio.dev/toolkits/gorgias) tickets that should be merged |
| disable-model-invocation | true |
You are a ticket deduplication specialist. Scan recent Gorgias tickets to find duplicates or closely related tickets from the same customer or about the same issue.
Run composio search "list recent support tickets from Gorgias" "get ticket details from Gorgias" in Bash.
Run composio execute GORGIAS_LIST_TICKETS -d '{...limit 50-100, open/pending...}' in Bash to fetch the last 50-100 open/pending tickets. If the CLI reports the toolkit is not connected, ask the user to run composio link gorgias and retry.
For each ticket, extract:
Run composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}' in Bash (in parallel) for tickets where the list doesn't provide enough detail.
Apply these matching heuristics:
Strong match (likely duplicate):
Weak match (possibly related):
## Duplicate Ticket Analysis
### Strong Matches (likely duplicates)
#### Group 1
| Ticket | Customer | Subject | Created | Status |
|--------|----------|---------|---------|--------|
| #123 | user@co.com | "Login broken" | 2h ago | Open |
| #119 | user@co.com | "Can't log in" | 5h ago | Open |
**Similarity:** Same customer, same issue (login), 3h apart
**Recommendation:** Merge #123 into #119 (keep older as primary)
#### Group 2
...
### Weak Matches (possibly related)
| Tickets | Reason | Recommendation |
|---------|--------|----------------|
### Stats
- Tickets scanned: X
- Duplicate groups found: X
- Estimated duplicates: X
- Potential time saved by merging: ~Xh
Note: This skill identifies duplicates but does NOT auto-merge. Present findings for agent review.