This month's updates give you more control over the tools you use every day, across both Helpdesk and Statements.
Trigger improvements protect your Helpdesk automation setup from accidental changes and a rebuilt recipient field makes replies faster.
On Statements, triggers have gained a wave of new rule options so you can automate more of your actions and comments.
Helpdesk
1. Duplicate, lock and archive triggers
We've given you more control over your Helpdesk triggers, so managing your automation setup stays simple as it grows.
Duplicate a trigger to use it as a starting point for a new one, fully editable before you save
Lock kicks in automatically once a trigger has run at least once, so its conditions and actions can't be accidentally changed - only the name and description stay editable
Archive a trigger that's run before to hide it from your list while keeping its run history, or delete it outright if it's never run
What this means for you:
→ Reuse existing trigger logic instead of rebuilding from scratch
→ Live triggers can't be misconfigured by accident
2. Rebuilt To, CC and Bcc fields
We've rebuilt how you manage recipients when composing a ticket reply.
Add, edit and remove recipients more easily, paste in a list of emails without cleaning it up first, and get invalid addresses flagged automatically before you send.
What this means for you:
→ Faster recipient entry with fewer mistakes
→ Identify invalid email addresses before sending
→ Paste a list of recipients directly from Excel without manual cleanup
→ Reuse previous participants through autocomplete suggestions
→ Cleaner management of large recipient lists
→ Drag and drop recipients between To/CC/BCC - no more delete-and-retype gymnastics
Statements
1. More rules for Statement Triggers
We've expanded what you can build with Statement Triggers, so you can automate more of your actions and comments.
Statement columns are now available as trigger conditions, including your org's own custom columns
MATCH and DOES NOT MATCH let you compare a statement column directly against a ledger column
OR condition groups let you combine multiple scenarios into a single rule, instead of building one rule per scenario
New fields on Ledger (invoice number, invoice date, invoice amount, System) and Xelix (Assigned Action) columns
The condition dropdown now groups fields by Xelix column, Ledger column and Statement column, so it's clearer where each piece of data is coming from
What this means for you:
→ Build more rules to automate your actions and comments
→ Consolidate multiple scenarios into a single rule with OR groups