Salto for
Zendesk
Articles
SHARE
Tomas Vaitkevičius
April 25, 2023
7
min read
Sending email reminders to clients is a common requirement for almost every support team. Whether it’s to request more information about a support ticket, ask clients to perform a certain action to aid in solving a task, or something else, sending these email reminders is crucial—but doing so manually can end up taking a lot of time and manpower.
One solution for bypassing this problem is to set an automation that will reopen pending tickets a certain number of days after they are marked as pending. Although this is a workable solution, it doesn’t completely rid teams of manual work as a support agent will still need to reply manually, add a tag to the ticket, and even submit it as pending again.
In this article, we propose a better solution: configuring Zendesk to automatically send email reminders and reference the last message sent to the customer. This way, agents won’t need to send reminders manually and support teams can save on wasted time and effort. Here, we’ll walk you through the entire configuration process for setting these automated reminders in Zendesk.
To illustrate, let’s suppose you work for an e-commerce business that sells tech gadgets. Your support team receives a notification—perhaps from your shipping provider or CRM—that the order cannot be fulfilled due to inaccurate shipping information. You reach out to your customer via Zendesk to alert them of the issue.
Now, let’s also imagine that, according to your company policy, the order must be canceled and a refund issued if the customer does not respond within 6 days. To encourage a response from the customer, you set their ticket to reopen every 2 days so that an agent can send a reminder, add a tag, and submit the ticket as pending again. That adds up to a lot of wasted time and effort.
However, by configuring Zendesk to automatically send the customer an email reminder referencing the last message sent to them, your support agents won’t need to do it manually. The only thing they’ll need to do is tick a box on the ticket field enabling auto-reminders for that ticket—pretty easy stuff!
Setting up automated email reminders in Zendesk is pretty simple. In fact, the entire configuration consists of only a ticket field, 3 automations, 3 triggers, and a view.
Let’s go through the set-up process step by step.
1. Create an “enable reminder” ticket field
This step ensures that when an agent ticks the “Enable reminder” checkbox, the tag email_reminder will be added to the ticket. This tag will be used in the email reminder automations and triggers we’re about to set up.
2. Create the first email reminder automation, which sends a reminder after 48 hours
This step creates an automation that will send an email reminder to the customer if they haven’t replied within 2 days. It will also add the tag email_reminder_1st to the ticket, which we’ll use in subsequent steps.
3. Create the second email reminder automation, which sends a reminder after 96 hours
This step creates a second automation, which will send the customer another reminder email if they haven’t replied within 4 days. It also adds the tag email_reminder_2nd to the ticket, which we’ll use in subsequent steps.
Here’s a quick example of what the customer’s second email will look like, referencing the first:
4. Create an automation that opens the ticket after 144 hours
This step creates a third automation, which will reopen a ticket if the customer hasn’t replied within 6 days. It also adds the tag reminder_open to the ticket, which will be used in the next step to place the ticket in the appropriate view for further handling.
5. Create three triggers that remove all tags when a customer replies
So far, we’ve created 3 automations: two to send email reminders and one to reopen the ticket. Now we’ll create 3 triggers that will remove a ticket from the email reminder automations when a customer replies.
Trigger 1:
This trigger moves the email_reminder tag if the customer replies within 48 hours (that is, before receiving the first email reminder). We remove the email_reminder tag so that the email reminder automation doesn’t run again.
Trigger 2:
This trigger removes the email_reminder tag when the customer replies within 96 hours, but after 48 hours (that is, between receiving the first and second email reminders).
Trigger 3:
This trigger removes the email_reminder tag when the customer replies within 144 hours, but after 96 hours (that is, between the second and third email reminders).
6. Create a view for follow-up tickets
In Step 4, we created an automation that will a) reopen a ticket if the customer hasn’t replied within 6 days and b) add a reminder_open tag to the ticket. That tag comes into play now.
Since these are tickets that never received a reply from the customer, the support team will need to handle them (according to our example). To make things easier for the agents, we’ll gather these tickets into a dedicated view.
Create a new view with these conditions:
And there you have it!
To recap, the schema of the entire process is as follows:
By following these steps, you’ll be able to configure your Zendesk automations to save your support agents time and effort. You’ll also boost your ticket resolution rate—win-win!
Assets: https://miro.com/app/board/uXjVPlOmM-k=/?share_link_id=892152591200
Salto for
Zendesk
Zendesk
SHARE
Tomas Vaitkevičius
April 25, 2023
7
min read
Sending email reminders to clients is a common requirement for almost every support team. Whether it’s to request more information about a support ticket, ask clients to perform a certain action to aid in solving a task, or something else, sending these email reminders is crucial—but doing so manually can end up taking a lot of time and manpower.
One solution for bypassing this problem is to set an automation that will reopen pending tickets a certain number of days after they are marked as pending. Although this is a workable solution, it doesn’t completely rid teams of manual work as a support agent will still need to reply manually, add a tag to the ticket, and even submit it as pending again.
In this article, we propose a better solution: configuring Zendesk to automatically send email reminders and reference the last message sent to the customer. This way, agents won’t need to send reminders manually and support teams can save on wasted time and effort. Here, we’ll walk you through the entire configuration process for setting these automated reminders in Zendesk.
To illustrate, let’s suppose you work for an e-commerce business that sells tech gadgets. Your support team receives a notification—perhaps from your shipping provider or CRM—that the order cannot be fulfilled due to inaccurate shipping information. You reach out to your customer via Zendesk to alert them of the issue.
Now, let’s also imagine that, according to your company policy, the order must be canceled and a refund issued if the customer does not respond within 6 days. To encourage a response from the customer, you set their ticket to reopen every 2 days so that an agent can send a reminder, add a tag, and submit the ticket as pending again. That adds up to a lot of wasted time and effort.
However, by configuring Zendesk to automatically send the customer an email reminder referencing the last message sent to them, your support agents won’t need to do it manually. The only thing they’ll need to do is tick a box on the ticket field enabling auto-reminders for that ticket—pretty easy stuff!
Setting up automated email reminders in Zendesk is pretty simple. In fact, the entire configuration consists of only a ticket field, 3 automations, 3 triggers, and a view.
Let’s go through the set-up process step by step.
1. Create an “enable reminder” ticket field
This step ensures that when an agent ticks the “Enable reminder” checkbox, the tag email_reminder will be added to the ticket. This tag will be used in the email reminder automations and triggers we’re about to set up.
2. Create the first email reminder automation, which sends a reminder after 48 hours
This step creates an automation that will send an email reminder to the customer if they haven’t replied within 2 days. It will also add the tag email_reminder_1st to the ticket, which we’ll use in subsequent steps.
3. Create the second email reminder automation, which sends a reminder after 96 hours
This step creates a second automation, which will send the customer another reminder email if they haven’t replied within 4 days. It also adds the tag email_reminder_2nd to the ticket, which we’ll use in subsequent steps.
Here’s a quick example of what the customer’s second email will look like, referencing the first:
4. Create an automation that opens the ticket after 144 hours
This step creates a third automation, which will reopen a ticket if the customer hasn’t replied within 6 days. It also adds the tag reminder_open to the ticket, which will be used in the next step to place the ticket in the appropriate view for further handling.
5. Create three triggers that remove all tags when a customer replies
So far, we’ve created 3 automations: two to send email reminders and one to reopen the ticket. Now we’ll create 3 triggers that will remove a ticket from the email reminder automations when a customer replies.
Trigger 1:
This trigger moves the email_reminder tag if the customer replies within 48 hours (that is, before receiving the first email reminder). We remove the email_reminder tag so that the email reminder automation doesn’t run again.
Trigger 2:
This trigger removes the email_reminder tag when the customer replies within 96 hours, but after 48 hours (that is, between receiving the first and second email reminders).
Trigger 3:
This trigger removes the email_reminder tag when the customer replies within 144 hours, but after 96 hours (that is, between the second and third email reminders).
6. Create a view for follow-up tickets
In Step 4, we created an automation that will a) reopen a ticket if the customer hasn’t replied within 6 days and b) add a reminder_open tag to the ticket. That tag comes into play now.
Since these are tickets that never received a reply from the customer, the support team will need to handle them (according to our example). To make things easier for the agents, we’ll gather these tickets into a dedicated view.
Create a new view with these conditions:
And there you have it!
To recap, the schema of the entire process is as follows:
By following these steps, you’ll be able to configure your Zendesk automations to save your support agents time and effort. You’ll also boost your ticket resolution rate—win-win!
Assets: https://miro.com/app/board/uXjVPlOmM-k=/?share_link_id=892152591200