{"id":649,"date":"2018-11-01T17:13:08","date_gmt":"2018-11-01T17:13:08","guid":{"rendered":"https:\/\/feedcheck.co\/blog\/?p=649"},"modified":"2018-11-28T11:45:35","modified_gmt":"2018-11-28T11:45:35","slug":"how-to-convert-your-negative-reviews-into-zendesk-tickets-in-5-easy-steps","status":"publish","type":"post","link":"https:\/\/feedcheck.co\/blog\/how-to-convert-your-negative-reviews-into-zendesk-tickets-in-5-easy-steps\/","title":{"rendered":"How to Convert Your Negative Reviews into Zendesk Tickets (…in 5 easy steps)"},"content":{"rendered":"

Everyone using zendesk has a fervent need for making the help desk tool their central point of complaints and resolutions no matter where their customers have initially made their voice heard.<\/span><\/p>\n

That is how numerous other platforms where customer feedback lands on have been integrated with zendesk in order to allow their users from every businesswalks to collect each and every customer dissatisfaction, bring it into zendesk and track how solutions are provided across multiple input sources.<\/span><\/p>\n

From all the platforms where customer complaints can be collected from, the eCommerce zone represented by marketplaces and online stores, is the most challenging one. In the eCommerce space, customer complaints are not always sent directly (and not only) to the support teams of the stores where a product was purchased from but, more than often nowadays, customers share their complaints publicly, as reviews,<\/strong> in order to advise and be of help to other people who are potentially interested in purchasing the same product.<\/span><\/p>\n

Rated either by 1 or 2 stars and often by 3 stars, depending on the customer culture and level of indulgence, negative reviews are shared in the public space accompanied by a series of data such as a title, the review descriptive content, a rating, the publishing date, the product and particular product model reviewed.<\/span><\/p>\n

Bringing product reviews from the eCommerce public space into zendesk as tickets requires a dedicated tool that has the capability to aggregate reviews and related data in a harmonised way regardless of the store and its geograpiycal origin. FeedCheck platform is one of the solutions that can solve the review aggregation<\/strong> needs and one of the very few solutions that is truly dedicated to product review aggregation<\/strong> in particular.<\/span><\/p>\n

But How It Works?<\/span><\/h2>\n

There are 5 easy steps that you can follow below:<\/span><\/p>\n

 <\/p>\n

Step 1: Create your zendesk account!<\/span><\/h3>\n

First and foremost, you need to make sure that you have a zendesk account set up and ready to receive your new negative reviews as tickets<\/strong>.<\/span><\/p>\n

 <\/p>\n

Step 2: Set up your FeedCheck – zendesk integration<\/span><\/h3>\n

With your zendesk account details ready, go to FeedCheck\/Settings and fill in your zendesk email, password and subdomain.<\/span><\/p>\n

 <\/p>\n

Step 3: Set up the zendesk API authentication method<\/span><\/h3>\n

Go to\u00a0z<\/strong>endesk > Admin > Channels > API > Settings<\/b>\u00a0and make sure that the\u00a0API authentication using an agent\u2019s email address and password<\/em>\u00a0is enabled.<\/span><\/p>\n

 <\/p>\n

Step 4: Test and save your integration setup<\/span><\/h3>\n

Now you\u2019re ready to test if all the above details have been provided correctly. If they\u2019re not then FeedCheck will let you know that by displaying the following message:\u00a0<\/span><\/p>\n

\"\"<\/p>\n

 <\/p>\n

But if they\u2019re correct, you\u2019ll receive a FeedCheck integration test ticket in your zendesk account that looks like this:<\/span><\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Once you have successfully finished the integration setup, you have one more step to do:<\/span><\/p>\n

<\/h3>\n

Step 5: Set up your FeedCheck – zendesk alert<\/span><\/h3>\n

In FeedCheck > Alerts you need to have your alert type set as zendesk<\/em> in order to receive your negative reviews as tickets in zendesk:<\/span><\/p>\n

 <\/p>\n

\"\"<\/p>\n

Now all is set for your FeedCheck – zendesk integration to work right and deliver your reviews as tickets into zendesk together with all other related data specific to reviews as shown below:<\/span><\/p>\n

\"\"<\/p>\n

Thus, you’ll know which product the review ticket is for, the review rating given by your customer, the online store or marketplace where the review was posted on, the review content describing your customer dissatisfaction as well as a direct link to the actual review in the store. You will also see that the ticket has been sent to you by FeedCheck, helping you differentiate it from other ticket sources that feed your zendesk account.<\/p>\n

We hope that you found this post useful for getting started to receiving your negative reviews as zendesk tickets<\/strong> and\u00a0 getting connected with all your customers right away from your zendesk account.<\/span><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Everyone using zendesk has a fervent need for making the help desk tool their central point of complaints and resolutions no matter where their customers have initially made their voice heard.<\/p>\n","protected":false},"author":2,"featured_media":665,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[106,1,109,100],"tags":[6,50,2,5,12],"class_list":["post-649","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-amazon-reviews","category-product-reviews","category-review-aggregation","category-review-monitoring","tag-aggregate-reviews","tag-amazon-reviews","tag-customer-reviews","tag-product-reviews","tag-retail-reviews"],"_links":{"self":[{"href":"https:\/\/feedcheck.co\/blog\/wp-json\/wp\/v2\/posts\/649","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/feedcheck.co\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/feedcheck.co\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/feedcheck.co\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/feedcheck.co\/blog\/wp-json\/wp\/v2\/comments?post=649"}],"version-history":[{"count":11,"href":"https:\/\/feedcheck.co\/blog\/wp-json\/wp\/v2\/posts\/649\/revisions"}],"predecessor-version":[{"id":783,"href":"https:\/\/feedcheck.co\/blog\/wp-json\/wp\/v2\/posts\/649\/revisions\/783"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/feedcheck.co\/blog\/wp-json\/wp\/v2\/media\/665"}],"wp:attachment":[{"href":"https:\/\/feedcheck.co\/blog\/wp-json\/wp\/v2\/media?parent=649"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/feedcheck.co\/blog\/wp-json\/wp\/v2\/categories?post=649"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/feedcheck.co\/blog\/wp-json\/wp\/v2\/tags?post=649"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}