You can use trigger conditions to let assignees know when a side conversation is created, closed, replied to, and reopened. You can also use trigger actions to create email side conversations and child ticket side conversations automatically.
This article includes these sections:
Trigger conditions for side conversations
The default behavior for side conversations is that the assignee on the ticket doesn’t receive emails, but they do see temporary, in-product notifications. If you want the assignee to get emails about side conversations, you need to use triggers.
You can create trigger conditions for side conversations so that assignees know when a side conversation is created, closed, replied to, and reopened. Without them, the agent assigned to the ticket (who, ideally, is also the creator of the side conversation) may have a hard time knowing what’s going on with a particular issue.
This section includes these topics:
About trigger conditions for side conversations
- Side conversation+Is+Created
Createdis the initial state of a newly created side conversation.
- Side conversation+Is+Closed
Closedis the state of a side conversation after the agent clicks the Mark done button to close the side conversation.
- Side conversation+Is+Replied to
Replied tois the state of a side conversation after someone adds a reply.
- Side conversation+Is+Reopened
Reopenedis the state of a side conversation after the agent clicks the Reopen button to reopen a side conversation.
For a complete list of the different conditions and actions that you can use to create triggers, seeTrigger conditions and actions reference.
- Set ticket status topendingoron-holdupon creation of a side conversation
- Automatically assign the author of a side conversation to the ticket
- Send an email notification to the ticket assignee when a conversation side conversation is replied to by others
- Set a ticket’s status to open if a side conversation is replied to by anyone but the assignee
Example 1: When side conversations are created
Here’s an example of a trigger condition about how to handle side conversations when they are created.
Example 2: Updating ticket status when side conversations are replied to
Here’s an example about updating ticket status when side conversation replies are replied to.
Example 3: Notifying ticket assignees when side conversations are replied to
Here’s an example about notifying ticket assignee when side conversations are replied to:
Trigger actions for side conversations
You can save time in certain situations by creating side conversations automatically usingtriggers. You may want to do this if your company has a process that doesn’t really require manual review.
This section includes these topics:
About trigger actions for side conversations
There are two trigger actions that create side conversations. They are:
- Side conversation via email: Creates an email side conversation. To see this option,email side conversationsmust be enabled.
- Side conversation via child ticket: Creates a child ticket side conversation. To see this optionchild ticket side conversationsmust be enabled.
When the conditions in the trigger are met, the trigger runs, and the side conversations specified by action statements are created. These actions are similar to ones for side conversation in macros (seeUsing macros to create side conversations).
It’s also important to note that when a side conversation is created via a trigger, theSide conversation + Is + Created conditionis suppressed.
About creating child ticket side conversation via triggers
When creating a child ticket side conversation, it's best to use a ticket that is already assigned to an agent as the parent ticket. This is true regardless of whether thechild ticket is created manually from the ticket interfaceor via a trigger. When a child ticket is created, if the parent ticket has not been assigned to an agent or group, then the resulting child ticket will include the Zendesk System User as the requester of the child ticket.
If an agent with access to the parent ticket is not part of the group the child ticket is assigned to, the agent cannot update the child ticket, unless they are the requester or follower on the child ticket.
On triggers that create side conversation child tickets, you may want to consider adding an action for setting the assignee to an agent or group.
Example: Onboarding clients
Here’s an example of how someone might use triggers to create side conversations.
Situation
Let’s say that you have a business that operates co-working spaces. You want to streamline your process for onboarding new clients. You can use side conversations to make sure that these things happen automatically:
- Create achild ticket side conversationassigned to the Finance group. Make sure they have the client’s information, know when to start billing, and that they bill the correct amount.
- Create anemail side conversationand send it to the Facilities vendor. Ask them to schedule a deep cleaning of the clients new office before their start date.
Each of these side conversations are repeatable, templated interactions that lend themselves to being automatically created via trigger.
Things you will need
- Ticket formswithcustom ticket fields
- Groups
- New or updated triggers that include side conversation actions
- Side conversationsandchild ticket side conversationsare enabled
- An admin creates a special “New client”ticket formthat includes various required fields for new client info, such as “Name,” “Start date,” and “Office number.”
- An admin creates or updates triggers to automatically create side conversations about onboarding a new client.
- A manager logs a ticket, using the “New client” ticket form.
When the conditions in the triggers in step 2 are met, the triggers run, and these side conversations are created:
- Achild ticket side conversationis created and assigned to the Financegroup. They are asked to set the new client up for billing.
- Anemail side conversationis created and sent to the Facilities vendor. They are asked to schedule a deep cleaning of the client’s office before their start date.
- The manager and the Finance group use the child ticket side conversation to discuss onboarding tasks.
- The manager and the Facilities vendor use the email side conversation to discuss onboarding tasks.
Creating side conversations using triggers
Before you proceed, make sure that side conversations is enabled. You may also want to enable child ticket side conversations.
- InAdmin Center, click
Objects and rulesin the sidebar, then selectBusiness rules > Triggers. - ClickAdd triggertocreate a new trigger, oropen an existing trigger for editinginstead.
- (Recommended) In theConditionssection, add strict condition statements, to avoid creating unnecessary side conversations.
For an example of how to do this, seeCreating strict condition statements for side conversation triggers.
- In theActionssection, type “side conversation” into the field, and then choose one of the available side conversation actions.Note:Email side conversations andchild ticket side conversationsmust be enabled to see these options.
Repeat this step as many times as needed to add additional side conversation actions to the trigger. For a workflow example, seeExample: Onboarding clients.
- (Recommended) Add anAssigneeaction to the trigger.
When the trigger runs, the author of the side conversation (email or child ticket) matches the assignee in the originating ticket. If the ticket is unassigned when the trigger runs, a generic Zendesk system user is used instead.
- Fill in theTo,Subject, andMessagefields, and then clickAdd action.
You can useplaceholdersin these fields.
Make sure that you enter a valid recipient in theTofield. This is especially important with email trigger actions since they must be typed correctly. If you enter an invalid email address, there will be no warning in the user interface that the email wasn’t sent.
- If you are creating a new trigger, clickCreate. If you are editing an existing trigger, clickSaveinstead.
- (Recommended) If you have an existing trigger that includes theSide conversation + Is + Created condition, note which actions are included and then remove them from that trigger. Then, add those actions to the new or updated trigger from the steps above. We recommend doing this because, when a side conversation is created via a trigger, theSide conversation + Is + Created conditionis suppressed.
Creating strict condition statements for side conversation triggers
If you have triggers that create side conversations, we recommend that they include strict condition statements to avoid the creation of unnecessary side conversations. One way of doing this is with tags.
To create strict condition statements for side conversation triggers
- Create atagcalledtriggered_sc.
- Open a trigger for editing that is used to create side conversations.
- Add the followingcondition statementto the trigger:Tags + Contain none of the following + triggered_sc.
Doing this means that the trigger doesn't run, if this tag is already on the ticket.
- Add the following action statement to the trigger:Add tags + triggered_sc.
If the trigger runs and a new side conversation is created, this tag is added to the ticket. The tag is what prevents the trigger from running again in the future and creating new, unnecessary side conversations (because of the condition in step 3).
61 Comments
Is there a way to detect with which slack channel a side conversation has been initiated in triggers?
Hi Zendesk team,
Any news on separating the type of side conversation between:
It was already reported some time ago byNemosome time ago in thispost.
I'm going to bring this into a ticket so we can look into this further with you. You'll receive an email shortly stating your ticket has been created.
To know more about your use case, I'll take our discussion offline for now and convert this into a ticket. Thank you!
The third example sends a notification email to the ticket assignee when someone replies to a side conversation. In this situation, it would be useful to have a placeholder for the text of the side conversation reply. Then, the notification email could include the full side conversation reply so the assignee doesn't have to separately dig through Zendesk to view it.
Would you mind adding details of your use case and upvoting this product feedback thread?Allow side conversation content to viewed via email notification
Thanks, Dave! I will add my use case to that product feedback thread.
MattWe are trying to pursue a method like you suggested where we listen to the response on the side conversation for a specific response from our vendor. We plan on listening for when our vendor sends a customer satisfaction survey. When we receive this survey via the side conversation, it would apply a tag we can use to notify our agents on slack to come to review the ticket and solve it.
We are using the following logic, but this trigger won't fire.
===
Here is an example of the response email we receive from the side conversation we are trying to trigger on.
你有什么建议我们可以让这个有趣吗ction correctly?
Hi @.....
there is a way to add in the side conversation by email what was written in the ticket once a public or private answer arrives?
The problem is that if I add a side conversation, a new side conversation is created, I only need to update the one that I already have open.
Thanks.
Maria
MakyHi Maria, at this time it's only possible to initiate a new side conversation with a trigger action, not reply to an existing one. The primary reason is that trigger actions take place at theticketlevel, so there's no easy way to reference aspecificside conversation when setting up a trigger. Perhaps there could be some sort of way like "update most recently updated side conversation" or something along those lines, but that's not an entirely reliable method. We're definitely thinking about how it could be done, though.
royaleaglethis isn't currently doable because the ticket events for side conversations don't have the entire side conversation text available to them. This is something we could look into for the future, though.
ThanksToby Sterrett!
That could be a method to update the communication to third parties involved in the ticket issues without doing it manually.
Thanks again.
Maky
I have noticed that you have already submitted a request for this concern. Ticket#10651061. Please continue to work with our Advocate assigned to this ticket.
Any plans to be able to trigger a side conversation comment being sent to an agent via email? I get notified via email that a ticket with a side convo has been commented on, but I have to pivot to the ticket, then side convo, to see that update. I'd rather just see what the update was in my inbox (similar to private note) in my inbox.
I don't have any updates at this time, but can you go upvote and add your use case to this product feedback thread?Allow side conversation content to viewed via email notification
Hi ZD Team,
Just wondering why is there no "Is Not" condition available for Side Conversation? Is there any plans to add this option?
I hope all is well! The condition "is not" for side conversations is not available in any plans, as this command is not applicable for side conversation conditions. We have taken your feedback into consideration!
Thanks for your comprehension!
Hi ZD Team,
Able to advised it there any option available so that when a Side Conversation is being Replied to it would also be able to Notify the Follower other than the Assignee?
Currently, there is no option to notify the Assignee and Followers,
Pls adv if there any other workaround or alternative to this, TQ
Natively, it's not possible. You will need a comment on the parent ticket for followers to be notified.
What I can think of is you'll have to use the ticket update API in a webhook and use it on a trigger so that an update on the side conversation will also add a private comment on the parent ticket.
第一步是创建一个webhookusing UpdateTicket API:
Endpoint:
Request metod:
Request Format:
Create a trigger that will notify the webhook. The trigger I designed on my end originally will open the parent ticket when a response is received from the side conversation. I'll just have to add the action "Notify Active Webhook" on that trigger.
Here are the conditions on my trigger:
And here's the old and newly added action.
This is the JSON body that I have added on the trigger.
How do you add the Side Conversation Ticket # into the Subject when applying a macro as ticket.id placeholder is for the main ticket?
As it turns out, there's noplaceholderfor the side conversation ticket ID.
Is there any way from the Zendesk API to get the parent ticket information from the side conversation ticket view? We have been using a custom field on the requester to populate a custom app with data from one of our company APIs. From the side conversation, the requester becomes an agent so we can’t use the same approach there.
I’ve noted that the external_id in a side conversation includes the parent ticketId at the end, so we could use that the fetch the parent ticket information that way. I’m curious if there isn’t a better approach to get the parent requester information from within the side conversation itself.
We’re using the zafClient to make requests.
Hi Alexander! I can't think of a better way to approach that, so I'd run with that. Maybe someone else will chime in with a fun idea!
I think what I've landed on is creating a Side Conversation is Created trigger that calls a webhook. And then we're going to take the ticket ID from that, use that ID to fetch all of the side conversations associated with that parent ticket ID, and then add the necessary data we need to the individual side conversation tickets.
In the future it would be really cool if there were an easy way from zafClient to fetch parent ticket information when you are currently in the ticket sidebar of a side conversation. Right now the side conversation APIs seem focused on going from parent to child but not from child to parent.
In the trigger actions I do not see a Side Conversation with Slack, is that planned or will it be available anytime in the future. I only see Email and Ticket options which you can take action on. We are looking to create a slack convo based off of certain ticket criterias.
目前,使用默认notify-assignee trigger, our agents receive a notification that a side conversation email was replied to, but they don't get a notification with the text of that reply - they need to follow a link to the parent ticket and open the side conversation to see the reply.
我想包括帮助assig占位符nee know where comments on the side conversation when they get the default notify-assignee email. Currently the side conversation template includes information about the ticket itself, but I'm thinking of something like {{ticket.comments}} or {{ticket.latest_public_comment}} where the placeholders provide comments from the side conversation - not the ticket.
做these placeholders work this way, or is there a way to accomplish this?
HelloToby Sterrett
1. I am interested in using automations to send a reply to an individual side conversation.. I need to send an alert if the receiver of a side conversation doesnt reply in 24h. HYou said you've been trying things, how would you manage that ?
2. As well, agents are opening loads of side conversation and they are complaining that the notification system is not efficient enough on Zendesk because notifications disappear after a while. Maybe it would be better to do this with a special view of "answered side conversations", what do you think ?
Thank you
Max- rather thanemail, you can execute standard automations if you create it as a side conversationticket.
mfgyou're right, but a side conversation ticket is only available to send requests to agents or groups. In my case I need to reach out to people outside our organization so my only solution is email
I would like to have a trigger that notifies the assignee as well asall followerswhen a side conversation is updated but under the Email User option, all I see is the following (and the individual agents):
How can I go about this to include the followers? Do I have to use Email group > assigned group?
I could use Email user > all non-restricted agents but it seems that it would cause a lot of spam.
Geoffrey Wang
别人可以确认,但我认为这是一个example of nomenclature being inconsistent. IIRC, followers and CC's on this drop down are the same thing. Is the issue that you can't email just the followers/CCs?
Pleasesign into leave a comment.