Recent searches
No recent searches
Facebook Channel: Thumbs up icon from PM shows up as "See shared link"
Posted Mar 22, 2019
Hey there
Currently, when a customer sends the "thumbs up" in a PM on Facebook which ends up as a ticket, the thumb is being attached as an image, and not just shown directly in the ticket.
Atm. the channel can read emojis and shows these just fine in the ticket, but not the thumb up.
Is this something that's in the plans for a fix?
Screen below for exemplification:
With #helpsome regards,
Simon Blouner
Zendesk Consultant @ helphouse.io
3
7
7 comments
Vishnupriya Varadarajan
Hey Simon Blouner,
Currently we import any sticker in Facebook PMs as links. If the thumbs-up was a sticker instead of an emoji , it would show up as a link.
Hope this helps :)
0
Simon Boe
Hey @Vishnupriya
it clarifies what and why it's acting this.
But I don't see why it would not just be sent as an image in the ticket - like when setting an image in a regular email, which shows up in the comment in zendesk.
0
Nicole Saunders
Thanks, Simon. The team that manages our Facebook integration is looking into this.
0
Schuyler Weinberg
Has there been any updates here? Now it looks like it just says "Facebook User Name" sent a message instead of a link or the image at all. It makes the team feel like there's a missed message not going through.
0
Steeve
Hey @...

Facing the same problem, when an user is sending the "blue thumb" on Facebook Messenger we received it as: "User Name" sent a message. Do we have any solution ?
0
Luke Bradshaw
Hi there,
My agents also face this issue, which is rather annoying as it just requires more environment hopping, to confirm a message has not been missed, as suggested by other customers here
In ZD:

In FB messenger:
0
Ryan Gabriel
Also checking in to see if there's any movement on solving for this - we're having issues with the same lack of functionality.
0