Freshdesk Facebook Integration
The Freshdesk Facebook integration turns public comments and private messages into tickets. Useful, and noisier than anyone expects on the first day.
What the Freshdesk Facebook integration gives you
You authenticate a Facebook Page you administer, and Freshdesk begins pulling activity from it into the ticket queue. The agent answers from the ticket view, and the reply posts back to Facebook as your Page rather than as a person.
Two streams arrive, and they behave very differently.
The permissions come from Facebook, so an admin with the right level of Page access has to do the connection, and a re-auth is occasionally required when tokens expire. If the channel silently stops delivering, that is the first thing to check.
What actually becomes a ticket
This is the setting that decides whether the integration is a help or a flood.
Every comment is a potential ticket, and most comments are not support requests. Tag a friend. A single emoji. An argument between two customers under your post. Turn everything on and a mildly successful campaign post will bury your queue in noise for a week.
Filter at the front. Most implementations let you decide which activity types create tickets and, in some configurations, exclude content matching keyword rules. Start restrictive: private messages always create tickets, public comments create tickets only where they carry a question or a complaint, and use automation rules to auto-close or auto-tag the rest.
Then let the queue tell you what to change. After a fortnight, sample fifty social tickets and count how many needed a human. If it is under half, tighten the filter.
Public replies need a different playbook
A comment thread isn't a private conversation, and treating it like one causes the classic mistake.
Never ask for an order number in public. Answer publicly once, then move the conversation to a private channel.
The pattern that works: a short public acknowledgement that shows you saw it and are handling it, then a Messenger reply or an email to continue. Other readers see a company that responds. The customer gets a channel where they can safely share details.
Deletion is its own trap. Hiding or removing a critical comment is occasionally right, for abuse or genuinely illegal content, and almost always wrong for a complaint. Write the policy down and give agents the authority to follow it, otherwise every borderline case escalates to whoever owns the brand account.
Messenger response windows
Messenger has platform rules about when a business may message a person, and they're enforced by Facebook rather than by Freshdesk.
The short version: after a customer messages you, there is a limited window in which you can reply freely. Once it closes, unprompted messaging is restricted to specific approved categories with their own requirements. The exact durations and the approved message types have changed several times, so check the current Meta platform documentation rather than trusting any figure you read in an article.
The practical consequence matters more than the specifics. A Messenger conversation your team leaves for two days may no longer be answerable in that channel at all. Give social its own SLA, tighter than email, and its own group so nobody assumes the standard queue rules apply.
Fitting it into the rest of the queue
Social tickets look different from email tickets, and your reporting should reflect that.
If you're running Instagram, WhatsApp or X alongside this, the shared patterns are in the WhatsApp and social guide, and the channel-mix question is covered in omnichannel.
Frequently asked questions
How do you connect a Facebook Page to Freshdesk?
Add it as a Freshdesk social channel and authorise with a Page admin account. Connect Facebook Page to Freshdesk this way and the Freshdesk Messenger integration arrives with it, covering private messages as well as comments.
What can the Freshdesk Facebook integration pull in?
Comments on your Page posts, visitor posts depending on configuration, and Messenger conversations. Agent replies post back as the Page. A Page admin has to authorise the connection.
Do all comments become tickets?
Only if you configure it that way, and you should not. Filter to questions and complaints, and use automation to close or tag the rest, or one popular post will flood the queue.
How long do I have to reply on Messenger?
Meta enforces a limited response window after a customer messages you, with restricted categories afterwards. The durations have changed more than once, so check the current Meta platform documentation.
Should we delete negative comments?
Rarely. Remove abuse and illegal content. Answer complaints publicly and briefly, then move to a private channel. Deleting criticism tends to create a bigger problem than the criticism did.
Why did the Facebook channel stop working?
Usually an expired or revoked Page token, or an admin permission change. Re-authorise the connection first, then check whether the Page role that authorised it still exists.
Public comment plus private message
The same customer often contacts you twice on two channels. Ticket Merger finds the pair and merges it before two agents answer differently.
Start free trial14-day free trial. No credit card required.