How to create an auto reply for Facebook



Posted Jan 25, 2017

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

31 comments

Hey Helen,

The only other suggestion I have is updating your auto-reply trigger to add another tag that you can use to exclude these particular Facebook tickets from your SLA. I'm afraid there's no alternative solution as a first reply time metric can only be met from a manual response from the agent.

Perhaps someone else can jump in here and offer up an alternative solution for you.

0


Hi Brett, thank for the quick answer,

truth is - most of my tickets come from facebook so I need a solution for those kinds of tickets

any other idea?

0


Hey Helen,

It may be worth excluding Facebook tickets from your SLA policies as a whole so they don't skew your FRT metrics.

You could create a trigger that tags all Facebook tickets and set up your SLA policy to only apply to tickets that do not contain that tag.

When updating your policy, there should be a Tags > Contains none of the following > (tag) condition.

I hope this helps!

0


Hi @andreas and thank you so much for the detailed guide!

 

I'm having a problem with the SLA because of the auto replay implantation

my SLA was 4 hours for the first replay and 4 hours for the second replay,

since the implantation the auto replay "count" as a first replay

the SLA "first replay" is shot when the auto replay shot instead of my agent first respond.

Any creative idea? 

 

0


Hi 1149673957,

Thanks your article save my day :)

 

0


Hey Dion,

It may help to provide a screenshot of the target you've set up on your end so users can take a look. I'm rather limited on what I can assist with on my end but some additional information may help other users :)

Cheers!

0


Thanks @Andreas! I'm trying to create the extension, but I think something is wrong with the URL. I'm getting the attached error. Any ideas?

0


Hi @Andreas, 

I am having the same problem as Kelsa. After adding the URL target, I am not seeing the option to add a public reply. Can you help us please?

Thanks!!

0


Hey @Andreas,

Like Sachin, I would like an updated version to the post since the UI has changed so much.  Not seeing the option to add a public reply under Actions and would love to implement this for our business.

Any assistance would be great!

0


Hey @Andreas,

Totally get your point :) there are some customers who do not have complicated workflows, so they don't take those points into account. I just posted my solution for those who are looking for a simple auto reply and they are not aware of that option existing on Facebook.

0


Sign in to leave a comment.

ADDITIONAL CONTENT

More about

Didn't find what you're looking for?

New post