Your support queue, triaged before you open it.
Squash reads every incoming ticket, sorts it into bug, feature request, question or other, pulls out the details that matter, and flags the ones that need a human. You start your day with a queue that's already sorted.
Works with any ticketing system that can send a webhook.
- reported symptom
- CSV export never finishes for larger reports since the latest update
- repro hints
- Export more than ~500 rows · started after yesterday's update
- affected area
- CSV export
- urgency
- Needed for month-end close on Friday
Connect once. Every new ticket arrives sorted.
Connect
Create a connection and get a webhook URL plus a secret. Point your helpdesk's webhook, or a small script, at it. Anything that can POST JSON over HTTPS works.
Classify
Claude reads each ticket the way a support lead would: tone, typos and layout don't throw it. Each ticket gets one category, a confidence level, and the fields that matter for that category.
Review
Open a queue where urgent bugs and anything that needs a human are flagged. If a ticket can't be classified, it's kept with its original text and a one-click retry. Nothing gets dropped.
Structured output for every ticket, not just a label.
Each category comes with its own fields, and empty ones are left out rather than guessed.
- Reported symptom, in plain words
- Reproduction hints the customer gave
- Affected area of your product
- Urgency signals like deadlines or churn risk
- Requested capability, paraphrased
- Stated reason, when the customer gives one
- The question, cleaned up
- Topic area, such as billing or permissions
- Spam, praise and off-topic messages, kept out of your way
- Still visible, never deleted
Bugs arrive ready for engineering.
Every bug also comes out as a GitHub-issue-shaped report: a generated title, the customer's own words, and labels for the affected area. Hand it to an engineer, or to a coding agent, without rewriting anything.
"title": "CSV export hangs on large reports"
"labels": ["bug", "component/csv-export"]
"body": "Since yesterday's update, exporting…"Your customers' words, handled carefully.
Authenticated webhooks
HTTPS only, with a 256-bit secret per connection that you can rotate in one click. Repeated bad-secret attempts are watched for.
Isolated accounts
Each account sees only its own tickets. Connection secrets are stored encrypted, and passwords and session tokens only as hashes.
Ticket text is treated as untrusted
Ticket content is fenced off from instructions and the output is validated, so a malicious ticket can't steer how other tickets are handled.
EU hosting, 90-day retention
Hosted in the EU. Ticket text is sent to Anthropic's API for classification and deleted from Squash after 90 days.
Join the pilot.
We're onboarding a small number of support teams and working closely with each one. Setup takes about 15 minutes, and we'll check accuracy against your own triage with you before you rely on it.