Category

Automation Rules and Triggers in BoldDesk

Updated:

Automation rules, also known as triggers or workflows, are business rules that automatically perform repetitive ticket-related actions to boost agent productivity. By leveraging these rules, businesses can streamline tasks, minimize manual effort, and ensure faster response times. BoldDesk enhances this process with powerful automation capabilities, helping teams improve efficiency and deliver exceptional customer support. This guide explains how automation rules work, why they matter, and how to use them effectively.



Check out the video tutorial below.

Common Actions Supported

Automation rules can perform actions such as:

  • Route ticket to the appropriate support team
  • Send notifications to user, agent, or group
  • Add watchers or CC recipients
  • Add tags
  • Add a private note
  • Update ticket properties

Available Condition Fields

Conditions can be based on:

  • Ticket properties (status, priority, category, etc.)
  • Requester properties
  • Contact group properties
  • Custom fields

Automation rules are executed sequentially based on their order in the rule list. If multiple rules apply to the same event, they will be processed from top to bottom. You can reorder rules at any time to control execution priority and ensure the desired automation behavior.

Types of Automation Rules in BoldDesk

BoldDesk supports four main types of automation rules:

  • Auto Assignment
  • Create Ticket Triggers
  • Update Ticket Triggers
  • Time Triggers

Each rule consists of conditions and actions. A rule executes only when its conditions are met.

Auto Assignment Rule

  • Automatically assigns incoming tickets to a specific team or group based on ticket properties.
  • Uses round-robin logic to distribute tickets evenly among agents.
  • Executes during ticket creation or update only if assigned agent and group are empty.
  • The first matching rule is applied; remaining rules are ignored.
  • You can also add watchers related to the assigned group.

When both Auto Assignment and Create Ticket Trigger are configured to set the Assignee, the ticket trigger executes first. If its conditions are not met, the system then applies Auto Assignment. To avoid conflicts, it’s recommended to use only one assignee automation. Use Auto Assignment to assign tickets among available agents (or to a configured Group when all agents are offline). Use Create Ticket Trigger to always assign tickets to a specific Group and Agent.

Create Ticket Triggers

  • Executes during ticket creation if conditions match.
  • Common use cases:
    • Add user to watchers list
    • Add tags
    • Assign ticket directly to an agent

Update Ticket Triggers

  • Executes when a ticket is updated and conditions match.
  • Triggered by events such as:
    • Reply added
    • Note added
    • Property update
    • Customer feedback added
  • Common use cases:
    • If requester and agent reply count exceeds a threshold, change priority to High
    • Notify manager when negative feedback is received

Update Ticket Triggers run only when a ticket is updated through supported ticket events (for example: reply added, note added, field/property update, feedback added). There is no trigger/event condition that detects “Activity completed” as a ticket event, so you cannot run an Update Ticket Trigger based solely on an activity/task being marked as completed.

Time Triggers

  • Runs every hour on unclosed tickets if conditions match.
  • Common use cases:
    • Notify group if ticket is unassigned for X hours
    • Auto-solve ticket if waiting for customer response for X hours
    • Auto-close ticket if solved for X hours

A ticket can participate in a time-trigger automation up to 100 times during its lifecycle. Only unclosed tickets that have been updated within the last 30 days are eligible for evaluation. To avoid continuous execution loops, configure hour-based conditions so a rule matches only once and use actions that modify ticket properties, causing the rule conditions to become false after the automation runs.

  • The placeholder for private and public notes actions is only accessible within event triggers (for example, create and update ticket triggers) and is not supported in time triggers.
  • Triggering continuous automation from a prior automation is not supported due to the risk of a potential loop.
  • In Time Trigger Automations, the Add (Public) Reply action is not available. It allows Add Public Note and Add Private Note.
  • Time Triggers are evaluated periodically, typically once per hour, and may not run at an exact scheduled time. If a Time Trigger sends an email, the email activity is not recorded in the ticket history. To confirm that the trigger has run, check the Usage column on the Time Triggers configuration page.

Trigger Summary

A trigger summary in BoldDesk is a quick, high-level overview of an automation trigger rule. It shows you what the trigger does, including:

  • What event activates the trigger
  • What conditions must be met
  • What actions will be executed

This summary helps admins instantly understand the purpose of a trigger without opening the full editor. To view your trigger summary:

  • Navigate to Admin > Automation > Ticket Automation, then click the kebab icon on the particular trigger.

    View Summary.png

  • Click on view summary, and the trigger summary will be displayed.

    Trigger Summary.png

How to Deactivate a Trigger in BoldDesk

BoldDesk allows you to disable automation rules (Create Ticket Triggers, Update Ticket Triggers, Time Triggers) by editing or removing the rule so it no longer executes. To deactivate a trigger, follow the steps below:

  • Navigate to: Admin > Automation > Ticket Automation, then click the kebab icon on the particular trigger.
  • Click on deactivate.

    Deactivate.png

  • Click on Yes, deactivate to confirm the action. Once it is deactivated, you can find the trigger under the inactive triggers tab.

    Confirm Deactivate.png

How to Delete a Trigger in BoldDesk

In BoldDesk, triggers are part of Automation Rules (also called workflows). To remove an old trigger, you simply delete the automation rule itself. To delete a trigger, follow the steps below:

  1. Go to Admin Settings.
  2. Locate the Trigger You Want to Delete. Find the rule/trigger you want to remove from the list. For example, Create Ticket Triggers.
  3. Navigate the rule. From the rules, navigate to the trigger you want to delete and click on more options.

    Navigate Rule.png

  4. Click Delete
    Select the delete option and confirm to permanently remove the trigger.

    Delete Trigger.png

If you intend to use a trigger in the future, you may select the deactivate option rather than deleting it. After deactivation, you can reactivate the trigger whenever needed.

Irreversible Actions and Action-Combination Constraints

Some automation actions perform irreversible operations and have special execution requirements.

Scenario Behavior / Recommendation
Delete or Mark as Spam Actions Delete and Mark as Spam cannot be combined with other actions in the same automation rule. When either action is executed, the ticket is immediately scheduled for removal, preventing subsequent actions in the rule from running.
Recommended Approach If additional actions must occur before deletion or spam processing, create separate automation rules. For example, use one rule to send notifications, update fields, or add tags, and another rule to delete or mark the ticket as spam when the required conditions are met.
  • BoldDesk ticket automation supports only ticket-based triggers, including Create Ticket Triggers, Update Ticket Triggers, Time Triggers, and Auto Assignments.
  • A Contact Created trigger is not available. As a result, it is not possible to automatically send an email when a new contact is created based on a contact tag.
  • To identify an automation rule’s ID and name, open the rule in edit mode:
    • The Rule ID is the numeric value at the end of the browser URL.
    • The Rule Name appears in the Rule Name field.

Find the Rule ID of an Automation Trigger

Each automation rule has a unique Rule ID. This ID can be useful when troubleshooting, reviewing configurations, or communicating with support.

To locate the Rule ID:

  1. Navigate to Admin > Ticket Automation.
  2. Open the applicable trigger type:
    • Create Ticket Triggers
    • Update Ticket Triggers
    • Time Triggers
  3. Open the required rule in edit mode.
  4. Review the URL in the browser address bar.
  5. Locate the numeric value at the end of the URL.

For example:

https://yourdomain.bolddesk.com/agent/admin/automation/create-ticket-triggers/147

In this example, 147 is the Rule ID.

The URL path varies depending on the trigger type, but the Rule ID is always the numeric value displayed at the end of the rule’s edit-page URL.

How Automation Appears in Ticket History

When an automation rule’s conditions are met, BoldDesk executes the rule and applies its configured actions. Any action that modifies the ticket record is recorded in the ticket’s History tab.

Examples include:

  • Agent or group assignment changes
  • Status, priority, type, or category updates
  • System-field or custom-field updates
  • Tag additions or removals
  • Watcher or CC changes
  • Other actions that modify ticket data

The History tab records the resulting ticket changes as individual entries.

Automations that only send custom email notifications do not modify the ticket record. Therefore, email-only actions do not create entries in the ticket’s History tab.

What Ticket History Does Not Record

The History tab is not a rule-evaluation log.

BoldDesk records the changes made to a ticket when an automation rule executes successfully, but it does not create History entries for rules whose conditions were evaluated but did not match.

As a result:

  • A matching rule that updates the ticket will create one or more History entries.
  • A rule that does not match creates no History entry.
  • The absence of a History entry does not confirm whether a rule was evaluated; it confirms only that no ticket changes from that rule were recorded.

Use the automation rule’s Trigger Summary to review its configured conditions and actions. Use the ticket’s History tab to verify the ticket changes produced by matching automation rules.

Frequently Asked Questions

  1. Can I reorder automation rules?
    Yes. Automation rules run in the listed order, and administrators can reorder them.

  2. What happens if multiple rules match?
    The first matching rule executes; others are ignored.

  3. How often do time triggers run?
    Time Triggers run every hour, and a ticket can participate up to 100 times during its lifecycle.

  4. Is there an action to change the Brand in a ticket trigger?
    No. Brand changes must be done manually and cannot be done using triggers/automations.

  5. Can BoldDesk AI prompts (AI Summary/Custom Prompts) be used inside automation rules?
    No. BoldDesk does not support AI prompts as automation actions. Agents initiate AI Prompt Actions from the ticket page only.

  6. Why can’t one automation send an email and then delete the ticket?
    Because Delete and Mark as Spam cannot be combined with any other actions in the same automation rule.

  7. Can I see every time a specific automation rule executed?
    Not directly. BoldDesk does not provide a centralized report/dashboard listing each automation execution. You can review automation-driven changes in a ticket’s Activities → History audit trail.

  8. Why are attachments not included when a ticket is forwarded via automation?
    Attachments are not currently supported in automation actions, including Forward Ticket. Attachments can be included only when an agent forwards a ticket manually and explicitly includes them.

  9. Why Did a User Receive an Email That Is Not Visible in the Expected Ticket?

    • The email may have been generated by a separate automation rule rather than added as a public reply to the expected ticket. Review the following automation types:
      • Create Ticket Triggers
      • Update Ticket Triggers
      • Time Triggers
    • For each rule, verify configured conditions, email action and selected recipients, rule execution order, whether another ticket involving the same recipient matched the rule, and whether multiple automation rules matched the same ticket event.
    • An email sent through an automation notification action is not necessarily displayed as a public reply in the ticket conversation.
    • If the email cannot be traced to the expected ticket, search for other tickets involving the same recipient and compare the received email with the email content configured in the automation rules.

Related Articles

  1. How to Send Custom Email Notifications Using Ticket Triggers
  2. How to Set Up Even Distribution Auto-Assignment in BoldDesk
Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Comments (0)
Access denied
Access denied
Access denied
Access denied

No articles or sections found
No articles or sections found