Zendesk

How to Create Zendesk Tickets From Community Posts

  • 9 April 2019
  • 4 replies
  • 1680 views

Userlevel 1
'

Sometimes community members post issues that can’t be solved by the community, like a bug with one of your products, or an issue that’s unique to their account. In this case, one of the best routes to a solution is to pass the customer’s issue on to your support team. Using our Zendesk escalation integration, your moderation team can quickly escalate any question, conversation, or reply to a Zendesk Support ticket. Save yourself time and eliminate the frustration of switching between different platforms!

Make sure you’ve installed the Zendesk app on CC first:

 

How To Escalate a Community Post To Zendesk

Please make sure that:

  • You’ve connected a Zendesk Support account to CC (following the steps above in "How To Install the Zendesk Integrations").
  • You’re logged in as a moderator, community manager, or administrator.
  1. Navigate to the post you want to escalate to Zendesk in Control.
  2. Press ‘Create Zendesk ticket’
  3. Edit the ‘Subject’ and ‘Public Reply’ if needed.
  4. Press ‘Create’.
  5. After you create the ticket, you’ll see the message: ‘Zendesk ticket has been created’ - this will remain attached to the post in Control.
  6. When you click on the ‘Zendesk ticket’ link, you’ll see the ticket on your Zendesk Support instance, so that you can follow it up and check in on its status.
? A link to the original topic on the frontend, where any user can view it, is automatically appended to the Public Reply for your Zendesk agents.

? We automatically add a tag ''community_escalation'' to all tickets created using our integration, so you can easily report/filter on tickets that came from the CC.

⚠️ Whether the ‘Requester’ (the author of the post you’re escalating) receives a notification about the creation of a Zendesk Support ticket, including the ‘Public Reply’, is dependent on your Zendesk Support settings (see Zendesk’s knowledge base for detailed instructions on setting up triggers).

⚠️ It’s better to carry out moderation tasks before escalating a post, rather than after. Converting the content type (question, conversation) of an escalated topic, promoting an escalated reply to a new topic, and moving an escalated reply to another topic will all delete the escalation.

⚠️ Articles cannot be escalated into Zendesk tickets by default, as articles are official company content which can only be created in the control environment. Replies to articles, and all other posts can be escalated to Zendesk.

?It’s not possible to escalate a single post to Zendesk more than once. It is possible to escalate multiple replies from the same topic.

? You can set up a custom view on Zendesk for these tickets by using information from the description (contains the following string: ''This ticket was generated from: https://community.yourdomain.com/'') and channel (‘Web service (API’).
 
'

4 replies

Where do replies from within Zendesk end up? Do they go back to the email of the person who opened the post?

Badge

Hiya @kaponte ,

From my understanding, once anything is escalated to Zendesk and a ticket is created there, it’ll continue running as if it was any other Zendesk ticket. This generally means that replies on that side will show up in the portal (if the user wishes to use it) and via email. It should generally attach to the same email address that the forum account is linked to.

Personally, I prefer using the web portal that Zendesk offers rather than email myself, but since they both sync up with each other anyway, users can feel free to pick whichever side works for them - or even mix and match if they’d like to.

Given that the contents of support tickets tend to be private, anything posted on the ticket in Zendesk generally won’t get transferred back to inSided automatically, to help prevent leaks.

hi, 

is there an option to customize the “Create Zendesk ticket” pop-up?

I can only see “Subject” and “Public Reply”, what if additional custom fields are needed in my organization for creating a ticket?

 

Hi @Frank and @Blastoise186 when a ticket is ‘pushed’ to Zendesk from inSided, does it also bring along the user’s email? In Zendesk, we use the users email to identify who the user is. The user is also able to identify their previous tickets based on their user email.

Also, do you know if any best practices articles for the Zendesk side? We have two products and for some reason the tickets are being pushed to the other product so looking into the possibility of a custom trigger in Zendesk?

Reply