# Automation rules

> Rules that assign, tag, prioritize, email and close tickets. Test any rule on a real ticket first, and every change names the rule that made it.

URL: https://office.greatwork.company/desk/features/automation-rules
Last updated: 2026-11-21

Rules assign, tag, prioritize, email and close tickets for you, and you can test each one on a real ticket before turning it on.

## When, if, then

A rule has an event (**When** a ticket is created, a customer replies, a field changes, an SLA is about to be missed, a survey comes back, or every 15 minutes), conditions (**If** the subject contains "invoice", the customer's domain is acme.com, it arrived outside business hours) and actions (**Then** set fields, assign, tag, add a note, email someone, send a webhook, close).

Rules run top to bottom, each one seeing what the one above changed. You can have as many as you need.

## Test before you trust it

Click **Test on ticket** and pick a ticket number. Desk shows which conditions matched and what each action would change, without changing anything. Once a rule is live, every change it makes appears in the ticket's activity with the rule's name.

## Guard rails

Update rules can filter on who made the change (an agent, the customer, a rule or the API), so "email the customer when a ticket closes" doesn't fire when a rule closes it. A rule can't re-trigger itself in the same chain, and there's a daily cap on rule emails per ticket.

## Rules you start with

New workspaces come with a few editable rules so you can see how they work: a new ticket confirmation, assign to the first responder, reopen when a customer replies to a closed ticket, an automated-sender spam rule, and a "close after 7 days waiting on the customer" rule that starts switched off.

## Example: Billing questions go to billing

**When** a ticket is created, **if** the subject or body contains "invoice", "charge" or "receipt", **then** set the category to Billing, assign the Billing group by round robin and add the tag billing.

Before turning it on, the admin tests it on #1286 ("Change my billing email"). The test shows the body matched "invoice" and the ticket would go to Billing, assigned to Ines. She turns the rule on, and the next morning #1301 shows "Assigned to Ines by [Assign] Billing to the billing group".

## How to set it up

1. Open Settings, then Rules, and click **New rule**.
2. Pick the event, add conditions, and add actions.
3. Click **Test on ticket** with a real ticket number and check the result.
4. Turn the rule on and drag it into place in the list.

## Questions

### Is there a limit on rules?

No. Every plan has unlimited rules, and they all run the same way.

---

Office by Great Work. Questions or corrections: hello@greatwork.company
