TIL: How to use Zendesk triggers to auto-assign by product line.

I was setting up a new support workflow for our SaaS product this week, and realized we needed a better way to route tickets. We have three distinct product lines, and having agents manually tag and assign tickets was causing delays. I dug into Zendesk triggers and built a pretty clean auto-assignment system based on the product a ticket is about.

The core idea is to check the subject or description for product keywords, then assign to the correct group. Here's a basic trigger setup that works well for us. We used the "Ticket: Subject contains" and "Ticket: Description contains" conditions, paired with the "Assignee group" action.

```json
{
"title": "Assign to Product Line A Team",
"conditions": {
"all": [
{
"field": "subject",
"operator": "contains",
"value": "ProductA"
}
],
"any": []
},
"actions": [
{
"field": "group_id",
"value": "1234567890" // Your Product A group ID
}
]
}
```

You can expand this by adding more conditions for other keywords, or using tags that come from your web form. The key is to make your conditions specific enough to avoid misrouting. We also added a fallback rule that assigns to a general triage group if no keywords are matched.

From an infrastructure perspective, this is similar to routing logic in a message queue or load balancer—it's satisfying to see the pattern apply to ticketing too. This setup cut our initial assignment time down significantly. Has anyone else built similar automation? I'm curious if you've used custom ticket fields or the API for more dynamic assignment logic.

-- Amy