How to email ticket info automatically to Non-Agents | Community
Skip to main content

How to email ticket info automatically to Non-Agents

  • August 14, 2013
  • 34 replies
  • 0 views

Show first post
This topic has been closed for replies.

34 replies

Matt40
  • May 23, 2017

Any way to setup an email target to go to more then one person.  I need to notify my leadership team.  Seems silly to setup one target per email.


Dan28
  • May 23, 2017

Hi Matt,

We use distribution groups in our targets to send to multiple people and it works out really well for us.


  • October 26, 2017

@Andrew J .... I'm in need of this same feature

(the ability to have both public and private comments pushed to my target using "notify target - email")

Have your mod team members come up with a way to do this?

 

The use case here is essentially escalating tickets to outside teams.

For instance, if an issue comes up that requires a legal consultation, the external legal advisor needs to see the full ticket thread with all comments.

 

I looked at the liquid markup page you linked, and didn't see anything that spoke to the issue of including private comments.


  • Author
  • November 1, 2017

Hello David, nothing about liquid has come back to me.

For your use case, I'd suggest forwarding one our your notification emails directly to the lawyer.

Fundamentally, private comments are 'agent only', to allow these to go to non-agents is both dangerous (private data could get sent to a user), and not good business sense for Zendesk (basically allowing non-agents to act as agents)


  • November 2, 2017

Thanks for the reply Andrew.
Certainly the idea of forwarding emails to third parties had occurred to us as well, but it doesn't allow the tracking of those requests the way that setting a tag and notifying a target does.

In addition, most of our agents don't get notification emails when the update a ticket themselves. The email notifications are only triggered when a non-self agent updates a ticket. So generating a current email to "self" that can then be forwarded is a hassle.

Another use case where a full thread of comments would be very handy is in sending threads to an external system. For example, our development group uses a tracking system they built in house. Currently the process of sending a ticket to the dev group is manual, but the ability to send the full thread would allow us to close out the zendesk ticket, and at the same time create a project in the devgroup tracking system complete with all details and attachments.

I understand your points, but disagree slightly. sending full thread emails to targets wouldn't create false-agents... since "replies" to those emails aren't threaded into the original ticket. Instead they spawn new tickets... so the external targets can't act like agents, since they can only receive information. if they send information, it is received just like from any email address in an open zendesk setup... as a new ticket.

So the bottom line is that once again I'm left high and dry... with a use case that isn't supported, but must be followed regardless. Nothing new, just frustrating.

Have a good day.

 

P.S. official prediction. One day someone is going to create a ticket system geared towards small companies, with few, if any, mandated workflows... and they will sweep the small business market. Zendesk and her competitors will still own the enterprise market, but the small business segment will jump ship in a heartbeat. --david-circa-2017


  • Author
  • November 2, 2017

Hello David,

Those replies CAN be threaded to the ticket though - I've done it. So the risk of abuse is real if it allows full functionality.

Make the third party an agent and you'll be away. you could add light agents for this.  

Oh, another option we've utilised, get the third party set up on a low value Zendesk plan, and share the ticket to them.

Another option, create a linked ticket and make this other person the requester, then paste the whole ticket stream for them. When they update with info, put this info on the parent ticket.

 

 


  • November 9, 2017

Hi Andrew,

That's really quite interesting, as I've tried in the past to create a workflow that would allow CC's to reply into ticket threads with no success. Granted, it's been a few years since I tried, so perhaps things have changed. Would you mind walking me through the steps to implement threaded CC replies?

 

I'd be happy to try to duplicate tickets, and more than happy in fact, since separating engineer/programmer comments from possible customer viewing is a positive good in my eyes. But I know of no automation etc that can do a copy/paste operation... so that's still a manual operation, so no benefit over forwarding emails.

Regarding light agents, I recall the price point for that is something like 250 per month... which is just about the same as what our entire 5 person organization is running altogether right now, so, not really an option).

 

The low value zendesk option I've never heard of. I see some plans starting at 5$ per month, which would likely be something our ceo etc would be okay with paying for our consulting entities. Can you talk a bit about how that option would work?

Thanks for listing some options, not everyone takes the time for that.


  • March 27, 2018

Might sound silly, but once the ticket comes into Zendesk its "unassigned" what action do I use to forward the ticket onto the external email (email target)? How do you assign it to the email target? I've tried running the macro but when I Submit as solved I get an error saying an assignee is required.


Nicole17
  • April 2, 2018

Hey Darren - 

The steps in the original post above outline what you need to do in order to notify the external email of the ticket. 

You cannot assign the ticket to an external email; tickets can only be assigned to Agents in your Zendesk. This is why you're receiving an assignment error for the macro. You can use this to notify external individuals and pass ticket info to them, but you cannot use it to assign things to them.