Applying macro on multiple tickets
Macro is a set of predefined actions that can be applied to tickets to automate repetitive tasks, such as sending acknowledgment emails, updating ticket statuses, or creating follow-up tasks.
When agents can select multiple tickets and apply the same macro across them, it saves a considerable amount of time, ensuring consistency and accuracy.
For example, a travel agency receiving a series of support tickets from customers who have questions about their flight cancelations due to weather issues. The agents need to send a standard response explaining the cancellation policies, offer rebooking options, and set a follow-up task to check on customer feedback after rebooking.
Rather than responding to each ticket individually, an agent can use the mass macro action. They can select all the tickets related to flight cancelations, apply the macro, and the following actions will be taken care of all at once:
- Sends a response to each customer explaining the cancellation policies and rebooking options.
- Updates the ticket status to "Awaiting Customer Confirmation."
- Sets a follow-up task for agents to check customer satisfaction post-rebooking.
This action is department-specific.
To apply the macro for multiple tickets:
- Navigate to the Ticket module.
- Select the desired tickets.
- Click Macro.
Revoking blueprint on tickets at a scale
Revoking the blueprint option takes the ticket out of the predefined path set by the applied blueprint. This comes in handy when agents have work on tickets that are misdirected to the department, are special cases, or simply when the blueprint path cannot result in resolution.
With mass and bulk revoke blueprint option agents can make this move on tickets at a scale. For example, a WiFi service provider receives a large number of tickets related to account verification requests. However, some of these tickets are submitted to the wrong department like customer service instead of accounts management. These tickets are automatically associated with a standard service blueprint that involves troubleshooting issues, which is irrelevant for account verification.
To resolve this, the agent can use the revoke blueprint option in mass or bulk to disassociate all those tickets from the blueprint at once.
After disassociating the tickets, the agent can make use of the mass move option to transfer them to the correct department, accounts management, where the process of account verification can begin, ensuring that the tickets are handled by the appropriate team.
To mass revoke a blueprint:
- Navigate to the Tickets module.
- Select the desired tickets.
- Click Revoke Blueprint from the above panel.
- Click Revoke.
Updating resolution in scale
A resolution is the final solution that the agent provides to the customer that leads to the closure of the ticket. In many cases, when agents are working on similar tickets even though the resolution is the same, they have to open individual tickets and add the resolution.
With the mass and bulk update resolution option, the agent can select all the similar queries and update the resolution at once. For example, multiple customers have raised tickets reporting bugs after a recent software update. Once the development team has identified the issue and provided the solution, the agent does not have to individually select ticket and add the same resolution for all. The agent can make use of this mass action and update the resolution in multiple tickets in a single action.

Note: If a ticket already has a resolution and a user attempts to update it via mass action, the existing resolution will be replaced with the new one.
To add mass or bulk ticket resolution:
- Navigate to the Tickets module.
- Select the desired tickets.
- Click the Update Resolution option from the above panel.
- Add the resolution.
- Click Update.
Viewing mass and bulk actions log
When either a mass or bulk action is applied, the action is not executed on all tickets simultaneously. Instead, it is initiated, and the tickets are queued for processing. For example, when an agent applies the mass reply action, the reply is queued and sent to each ticket one by one rather than all at once.
Agents can check the status of the action under the bulk actions log. Here, there are two separate tabs for bulk logs and mass logs.
Viewing bulk actions log
In the bulk actions log, you can view a list of the bulk actions that are in-progress and those completed. It also shows the module, action type, the execution time, who executed it, the view name, the department name, and the status.
To view the bulk action log:
Navigate to Setup > Data Administration > Bulk Actions Log > Bulk Action.
Viewing mass actions log
The log shows the status of mass replies, comments, and IMs. The actions are grouped under the initiated tab and the completed tabs. The actions can be filtered by department and by action.
To view the mass action log:
Navigate to Setup > Data Administration > Bulk Actions Log > Mass Action.