최근 검색
최근 검색 없음
How to create an auto reply for Facebook
2017년 1월 25일에 게시됨
I saw lately a couple of posts here that people are looking for a auto-reply function for the connected Facebook pages.
https://support.zendesk.com/hc/en-us/articles/226599587
https://support.zendesk.com/hc/en-us/community/posts/203597387
I've set this up for our account last month and will share it with you ... and yes, i am also interested in the Zendesk Swag offered in the january e-mail 😎
I will try to explain as simple as possible, if you need it more detailed please comment. But enough talked, let's start :)
Why I've implemented it?
We have around 3k tickets per month in our company, approx. 10% of them are via Facebook Messenger Channel. At a certain point this were simply too much tickets each month, which have not the same customer service experience as over the E-Mail or Help-Center channel, where we've set up dozens of automated service e-mails.
I think especially for Facebook messages, this missing feature is very critical for Zendesk, since customers expect an answer within minutes not hours.
Implementation
In fact it just consists of 2 parts:
- Trigger for determining when it should be sent
- Extension for posting a public reply
Trigger
Conditions
-
Integration Account: Choose your Facebook page (watch out if you are using global pages, they have all the same name!)
-
Ticket Is: of course only created when we are dealing with an auto-response
-
Tags: just in case i am adding a tag to prevent multiple auto-replies, since I remember a service outage where Facebook messages got fetched dozens of times.
- Requester Tractive: This is a user flag I've added to all the "Users" of our Facebook pages (Every Facebook page has a user in Zendesk, which is used when you write a customer first, or somebody is replying via business manager), so that a message created from ort marketing team e.g. reply to a post with a PM does also not get an auto-reply.
Actions
- Before sending the message, I am checking if the tag is not set already, to prevent duplicate messages as written before
- I am using my Extension to update the ticket with a public reply.
Extension
This extension will update the ticket itself via an API call. I know this is not the proper way according to Zendesk documentation, however i saw plenty of forum posts which are using this for example to write internal notes from triggers.
Url:
https://YOUR.zendesk.com/api/v2/tickets/{{ticket.id}}.json?ticket[comment][public]=true
Attribute Name:
ticket[comment][body]
Basic Authentication
Username: e-mail address + "/token"
Password: create an API token in your settings
Voila, after you made this everything should work. 👍
I hope i could help you a little bit, in case there is something not understandable or missing please let me know 😃
Andreas
PS: In addition to the nice auto replies you have, the facebook page you manage will also get the very responsive badge quickly :)
0
댓글 31개
Ice Manalili
Sadly we don't have a way to exclude it as part of the First Response Time at this moment, please refer to this article for more information about Understanding Ticket Reply Time. I understand this may not be the answer you are looking for, but I hope it helps.
0
GoGet Support
Hi there,
We have recently learned that the triggered that is going out to our Users via the mobile SDK is considered as a first public response and this has skewed our first response time data drastically.
Just wondering anyone from the community has any suggestions on the work around as we are not able to exclude those tickets as suggested in this thread.
THANK YOU IN ADVANCE!
0
Blanca
Hi Donald,
For your question re: automation, it runs on a ticket once an hour, unlike the trigger that is being applied immediately. Concerning multiple actions in one automation, it depends on the conditions that were set. It is highly recommended to use automation to set up a workflow that applies automatic updates to tickets based on time. I can proceed to create a ticket if you wish to discuss the sample ticket.
As for the error message, it means that the limit exceeded is 30 updates per 10 minutes per user per ticket. Here's API Rate Limits for your reference.
Please let me know how do you want to proceed with the automation settings.
Cheers,
Blanca | Customer Advocate
Chat with our live support!
https://support.zendesk.com/hc/en-us
0
Donald
Hi, I got this error after several successful fired actions via the automation.
Anyone has the idea how to resolve or prevent this using this use case?
0
Donald
Hi Blanca,
Appreciate your feedback. It worked after some revision on the conditions of my automation. I just noticed that sometimes it took more than an hour or two from the scheduled notification to notify end-user. There's also this on instance of having multiple actions in one automation together with this target, when it was executed the target notification to facebook did not fire but the others were ok.
0
Blanca
Hi Donald,
Thank you for reaching out. Automation is possible for this workaround. For example, if you add a tag to a user or organization, that tag will be added to any tickets where that user is the requester. But It may help to provide more information on the tag. I'm rather limited on what I can assist with on my end.
Alternatively, I can create another ticket if you are to provide more specific information.
Cheers,
Blanca | Customer Advocate
Chat with our live support!
https://support.zendesk.com/hc/en-us
0
Donald
Hey @Andreas
This article really a big help.
Just want to clarify if this target action is only applicable in a Trigger?
Because I tried it in an Automation and it did not fire. So what I did was a combination of automation (setup a tag) & trigger (validate the tag then execute ng target action).
0
Catherine Labrie
This worked perfectly for me as well ! Thank you !
0
helen moskowich
Thank you guys for the suggestions,
I think I have no choice but to do the auto replay from Facebook itself
The Facebook SLA is too important from being ignored
0
Andreas Schuster
Hi Helen,
The "auto-reply" is basically a public agent reply via the Zendesk API, that's why it is also the correct behavior that the SLA fires.
As mentioned by Brett I recommend you to add a tag to exclude such tickets with a facebook auto reply from your SLAs. This does not work however with the URL target below since Tags need to be set with a separate API call.
The easiest solution (but costly) would be to use a separate account for this auto-reply, and then you can set a tag with a trigger when this account replies to a ticket.
0
로그인하세요.