Helpdesk Automation Rules: Triggers, Conditions, and Actions

Helpdesk automation rules let you eliminate repetitive manual work from your support workflow. Instead of hand-routing every ticket, manually chasing overdue items, or remembering to notify the right people, you define rules once and let the system handle the rest.

Jitbit's automation rules engine works as an "if this, then that" system built directly into the helpdesk software. Each rule consists of three parts:

A trigger — the event that starts the rule. For example: a new ticket is created, a reply is added, or a status changes.
Conditions (optional) — filters that narrow when the rule fires. For example: only if the ticket is high-priority and comes from a VIP company.
Actions — what the rule actually does. For example: assign the ticket to a senior agent, send an SLA-breach notification, or generate an AI reply.

You can combine multiple conditions and actions in a single rule, and even chain rules together for complex multi-step automation. This article is a complete reference of every trigger, condition, and action available in Jitbit Helpdesk.

Automation Rule Triggers

A trigger defines when an automation rule runs. Every rule needs exactly one trigger. Jitbit Helpdesk supports the following triggers:

Ticket Lifecycle Triggers

Ticket is created — fires every time a new ticket is submitted, whether via email, the web portal, live chat, or the mobile app. Useful for auto-routing, auto-tagging, or sending instant confirmations.
Ticket is closed — runs when a ticket is closed. Commonly used to trigger satisfaction surveys or post-resolution follow-ups.
Ticket is re-opened — fires when a closed ticket's status changes back to an open state. Helps you catch unresolved issues before they slip through the cracks.
Ticket becomes overdue — triggers when a ticket's due date passes. Essential for SLA enforcement and escalation workflows.

Reply and Update Triggers

A new reply is added to a ticket — fires on any reply from any participant (technician or customer).
A new reply from the ticket submitter — fires only when the person who created the ticket adds a reply. Use this to re-prioritize tickets when customers follow up.
Ticket has not been updated for 30+ minutes — triggers after a configurable idle period with no new replies. Ideal for nudge reminders or auto-escalation.

Field Change Triggers

Ticket is moved to a new category — runs when a ticket's category changes. Useful for re-assigning tickets to category-specific agents.
Ticket is assigned to a user — fires when a technician is assigned to a ticket.
Ticket status has changed — triggers on any status transition, including changes to custom statuses.
Ticket priority has changed — runs when priority is updated by a user or an agent.
A custom field has been edited — triggers when any custom field value changes in a ticket.
Ticket due date has changed — fires when a due date is set or modified.
Tag is added to a ticket — runs when a ticket is tagged.

Advanced Trigger

Triggered by another rule — lets you chain multiple automation rules together for complex, multi-step workflows. For example: Rule 1 categorizes the ticket, Rule 2 (triggered by Rule 1) assigns it to the right agent and sets a due date.

Automation Rule Conditions

Conditions act as filters. The rule's actions only execute when all conditions are met. Conditions are optional — skip them if you want a rule to fire on every trigger event. Most conditions also support a "negative" variant (e.g., "due date is set" vs. "due date is NOT set").

Ticket Timing Conditions

Ticket is overdue by X hours — checks how long a ticket has been past its due date. Includes an option to factor in business hours. Pair this with the "ticket becomes overdue" trigger for tiered SLA escalation.
Ticket will be overdue in X hours or less — proactively catches tickets approaching their deadline, so you can act before an SLA breach.
Ticket was not updated for X minutes — checks for a period of inactivity from technicians.
Current time is between — restricts rule execution to specific hours of the day (e.g., only during business hours).
Current day of week is — restricts rule execution to specific days.

Ticket Content Conditions

Ticket subject contains or equals — matches text in the ticket subject line.
Ticket body contains — searches the ticket body for a specific string.
Latest reply contains — searches the most recent reply text for a match.
Ticket has tag — checks if a ticket has a specific tag.
Ticket has zero replies — true when a ticket has no replies (excludes system messages).

Custom Field Conditions

Custom field equals — checks if a custom field matches a specific value.
Custom field was updated and the field is — fires when a particular custom field is modified. Works best with the "custom field edited" trigger.

Ticket Sender Conditions

Ticket submitter email contains — matches the ticket creator's email address. Use this to route tickets from specific email domains to specialized teams.
Latest responder's email contains — checks the email domain of whoever last replied.
Ticket comes from company — filters by the submitter's company, useful for VIP or enterprise routing.
Ticket comes from department — filters by the submitter's department.
Ticket comes from location — filters by the location set in the ticket creator's user profile.
Ticket submitter's 'user-lookup' data contains — filters based on external user lookup data integrated from third-party systems.
Ticket is 'on-behalf', logged by technician X — identifies tickets submitted on behalf of a customer by a specific technician.

Ticket State Conditions

Ticket priority is — checks the current priority level.
Ticket category or section is — matches the ticket's category.
Ticket status is — checks the current ticket status.
Ticket is unassigned — true when no agent is assigned.
Ticket is assigned to — checks the currently assigned technician.
Ticket due date is set — checks if the ticket has a due date.
Ticket is 'unanswered' — true when the last update was not from a technician.
Ticket is 'updated by tech' — the most recent reply is from a technician.
Ticket is 'updated for tech' — the most recent reply is marked for technicians only.
Ticket is 'updated by customer' — the most recent reply is from the ticket creator.

Channel and Context Conditions

Ticket comes via — filters by submission channel: email, web, mobile app, live chat, etc.
Ticket comes via email and the TO field contains — checks which support mailbox received the email. Useful when you manage multiple support addresses.
Latest reply came from a non-subscriber — true when a reply comes from someone who is not subscribed to the ticket.
Technician is looking at the ticket — true when a technician currently has the ticket open in a browser or the mobile app. Helps avoid duplicate work.
Ticket's assigned tech is 'out of office' — checks whether the assigned technician has set their status to out-of-office.

Automation Rule Actions

Actions define what a rule does when the trigger fires and all conditions are met. Every rule requires at least one action, and you can combine multiple actions in a single rule.

Ticket Assignment and Routing

Assign to — assigns the ticket to a specific technician.
Assign to least busy technician — automatically routes tickets to the agent with the fewest active tickets, balancing workload across your team.
Set ticket category — moves the ticket to a different category.
Set ticket submitter — changes who is recorded as the ticket creator.

Communication Actions

Add reply to the ticket — posts an automated reply to the ticket. Can be set as a tech-only internal note.
Add AI-generated reply — generates a reply using an LLM, optionally referencing your knowledge base and external documentation. Learn more about AI integration.
Send email to ticket submitter — sends a direct email to the person who created the ticket.
Send email to assigned tech — notifies the assigned agent via email.
Send email to admins — alerts all administrators.
Send email to all ticket subscribers — sends a direct email (not a ticket reply) to everyone subscribed to the ticket.
Send email to all techs in the ticket category — notifies every technician with permissions for the ticket's category.
Send email to users in a department — sends email to everyone in a specific department.
Send email to particular user — sends email to any registered user in your helpdesk.
Cancel further email notifications for this event — suppresses additional automatic emails (e.g., new ticket confirmation) for the current event.

Ticket Status and Property Actions

Set ticket status — changes the status to any value, including custom statuses.
Set ticket priority — changes the ticket's priority level.
Close the ticket — sets the ticket status to "closed."
Reopen the ticket — sets the ticket to "in progress."
Set ticket subject — changes the ticket's subject line.
Set due date — sets the due date to a relative time in the future (e.g., "4 hours from now").
Set start date — changes the start date, which is used to calculate support metrics like resolution time.
Set custom field value — sets any custom field to a specified value.

Tag and Subscriber Management

Add/remove a tag — adds or removes a tag from the ticket.
Remove all tags — clears every tag from the ticket.
Add/remove subscriber — adds or removes users from the ticket's subscriber list. Subscribers can view and reply to the ticket.
Remove all subscribers — unsubscribes everyone from the ticket.

Ticket Visibility and Tracking

Mark the ticket as unanswered — adds the "unanswered" (orange) badge to the ticket.
Mark the ticket as answered — removes the "unanswered" badge.
Mark the ticket as 'upd FOR tech' — adds the "updated for tech" (blue) badge.
Mark latest reply 'for techs only' — makes the most recent reply visible only to technicians.
Add X minutes to 'Time Spent' — increases the time-tracking total for the ticket.

Advanced Actions

Clone the ticket — creates an exact copy of the ticket.
Delete ticket — removes the ticket. Deleted tickets are recoverable via Reports → Deleted Tickets.
Mark ticket as spam — deletes the ticket and disables the submitter's account.
Merge with previous ticket from this user — merges the two most recent tickets from the same user into one.
Delay — pauses execution for a set amount of time before running subsequent actions.
Trigger another automation rule — chains rules together for complex, multi-step workflow automation.
Send HTTP request — sends a request to a third-party API or webhook, enabling integration with external services via Zapier, Slack, or custom endpoints.

Else Actions

Every automation rule also includes an "else do this" section. Else actions execute when the trigger fires but the conditions are not met, giving you full control over both outcomes in a single rule.

Common Helpdesk Automation Examples

Here are some of the most popular ways Jitbit customers use automation rules to streamline their support operations:

Auto-routing by category — When a ticket is created, check its category and assign it to the responsible team automatically.
SLA escalation — When a ticket becomes overdue, send an alert to administrators and reassign to a senior agent. See SLA templates.
Round-robin assignment — Assign new tickets to the least busy technician to distribute workload evenly.
Auto-reply with AI — Generate an instant AI-powered response from your knowledge base when a new ticket arrives.
Out-of-office reassignment — When an assigned tech is out of office, automatically reassign the ticket to an available agent.
Follow-up nudge — If a ticket hasn't been updated in 24 hours, send a reminder to the assigned technician.

Ready to automate your support workflows? Try Jitbit Helpdesk free or explore the self-hosted version.