Side conversation notifications

Thanks once again, Shmuel Holzman! 

I've one last question (I hope!) if I make the triggers for the e-mail side of things, would that in any way interfere the triggers made for the ticket side conversations?

We generally use Side Conversations to communicate with stakeholders that don't use Zendesk; for stakeholders who use Zendesk we just communicate via Internal Comments on the ticket. 

Side Conversations via email works like as any other email service. The only Triggers we set up were the ones I mentioned at the top, here, to notify the Assignee when someone replied to the Side Conversation. 

Hope this helps!

And do you have some good triggers I could see when using Side Conversations via E-mail? :-)

Thanks, Shmuel Holzman!

I'll try it out. 

Would you mind explain a bit why you've chosen via e-mail instead of via ticket? :-) 

Glad to hear that it worked! 

You can add a Rule to the above Trigger `Assignee is not (current user)`. 

And then duplicate the same Trigger but with a small change:

Rules

Channel is Side conversation

Ticket is created OR Ticket is updated

Requester is not (current user)

Action

Email user: (requester)

Email Subject: Someone sent a Side Conversation to you - Ticket # {{ticket.id}}

Email body: 

Here are the details of the side conversation:

Ticket #{{ticket.id}}

{{ticket.title}}

{{ticket.description}}

Disclaimer: I have never tried this but in theory it should work. Let me know how it goes!

Shmuel Holzman

That worked. Thanks a lot! 

What if I then wants to have a mail being sent everytime the Side conversation is replied to? So for example: 

I'll start a Side conversation: Agent A gets first notification. Then Agent A answers this Side conversation, either through the ticket or directly through the mail. Then I want to receive a notification about this answer and so forth. 

Thanks in advance!

It seems I may have misunderstood your question; I was under the impression that you are looking to have the agent who created the side conversation notified when there is a response. 

Are you looking to address a scenario where a side conversation is sent to an agent? If so, we use side conversations via email instead of side conversations via ticket. 

If you prefer to create side conversations via a ticket, your Trigger can be set up like this: 

Rules

Channel is Side conversation

Ticket is created OR Ticket is updated

Action

Email user: (assignee)

Email Subject: Someone sent a Side Conversation to you - Ticket # {{ticket.id}}

Email body: 

Here are the details of the side conversation:

Ticket #{{ticket.id}}

{{ticket.title}}

{{ticket.description}}

Let me know if this makes more sense! 

(Side note: If you remove the space between the # and the {{ticket.id}}, it will hyperlink the {{ticket.id}}. Just found this out today, thanks to Ahmed Zaid's comment here) 

Hi, Shmuel Holzman

Thanks for your input! 

I like your triggers, however I want to understand it a bit more: 

When you say 'Assignee is not "-" = There is an assignee to the main ticket, right? Can you elaborate a bit on the first trigger; why would the agent added to the 'To'-field in the Side Conversation get a notification this way? I mean; the trigger fires when an agent is added as assignee to the main ticket, right? And if I opened the ticket and added myself as assignee, because I want to resolve the ticket, then, according to your trigger, I'll be the current user and therefore get the notification. 

Am I wrong? 

Hi. Raphaël Péguet!

Thanks for getting back.

With "assignee is not empty" is that Assignee is "-"? 

Thanks!

Hey Christian, 

We've created the following Trigger to address this:

Rules

Side conversation is created

Assignee is not "-" 

Action

Assignee is (current user)

It is then followed by a second Trigger (along the lines of what Raphaël mentioned):

Rules

Side conversation is Replied to

Action

Email user: (assignee)

Email Subject: Someone replied to a Side Conversation - Ticket # {{ticket.id}}

Email body: 

Someone replied to a side conversation in Ticket # {{ticket.id}}

{{ticket.title}}

Link to ticket: {{ticket.url}}