• Support tickets with full threads — the complete conversation, not just a summary someone wrote in a rush
• Customer records — company, plan, and revenue data so every ticket has business context
• Tags and custom fields — your existing Zendesk organization carries over
• Historical data — choose how far back to sync, so you're not starting from zero

Pilea then does the heavy lifting:

• Clusters similar feedback automatically — "22 customers hit the same API timeout issue this week"
• Links feedback to your backlog — see which open items have the most customer evidence behind them
• Tracks sentiment shifts — catch problems before they become churn conversations
• Attributes everything to real customers and real revenue — so you can prioritize by business impact, not volume alone

• "Alert when tickets mentioning 'export' spike this week" — catch emerging issues before they snowball into a crisis
• "Weekly breakdown of top ticket themes by customer segment" — see what enterprise customers are struggling with vs. what SMBs are asking for
• "Notify when a high-MRR customer submits 3+ tickets in a week" — a simple churn early-warning system that runs itself
• "Flag any ticket where a customer mentions switching to a competitor" — stay on top of competitive risk without reading every ticket

The agents run in the background, so the signal finds you — you don't have to go digging through tickets.