How to flag repeat customer contacts in Gorgias and alert your team in Slack

Why flag repeat contacts?

A customer who reaches out three times in a week is telling you something — even if each individual ticket looks routine. Repeat contacts are one of the strongest leading indicators of churn, and most support teams miss them entirely because each ticket gets handled in isolation. Research consistently shows that customers who contact support 3+ times in a week are 4-5x more likely to churn than single-contact customers. By the time someone on the team notices the pattern, the customer has already decided to leave.

Proactive flagging changes the conversation. Instead of treating each ticket independently, your team sees the full picture: this customer has an unresolved frustration pattern. Teams that implement repeat contact detection typically reduce churn among flagged customers by 20-30% — simply because the agent reads all recent tickets before responding, addresses the root cause, and escalates when needed.

Gorgias Rules can match keywords and tags on individual tickets, but they cannot query a customer's ticket history or count how many times someone has contacted you recently. That limitation means there is no native Gorgias approach for this recipe — you need an external workflow that can look up past tickets and apply logic across them.

How it works

Regardless of which tool you use, every approach follows the same three-step pattern:

1. Scan recent tickets — pull tickets from the past 7 days and group them by customer. This requires cross-ticket aggregation that individual Rules can't do.
2. Identify repeat contacts — flag customers whose ticket count exceeds your threshold (default: 3 tickets in 7 days). Exclude known high-volume accounts like agencies or resellers.
3. Alert and tag — post a Slack alert with the customer's ticket history and tag the latest ticket in Gorgias for easy filtering.

Which approach should I use?

• n8n (Recommended) — a scheduled workflow fetches tickets, groups by customer, and alerts Slack when repeats are detected. Best for teams that want reliable, scheduled detection with no LLM costs. Free self-hosted or $24/mo on n8n Cloud.
• Claude Code — a guided Claude Code skill that scans tickets conversationally. You can ask "who are the top repeat contacts this month?" or "flag anyone with 5+ tickets in 14 days." Best for teams already using Claude Code who want analysis alongside detection.

What you'll need

Choose your approach

Select an approach below to see the full step-by-step guide.