- Existing Facebook Messenger integrations are Facebook integrations that were set up in your Support admin settings and that have the private messaging setting (Include private messages) enabled.
- Existing Twitter DM integrations are Twitter integrations that were set up in your Support admin settings and that have the private messaging setting (Capture incoming direct messages as tickets) enabled.
This migration applies to Facebook Messenger and Twitter DM channels. To migrate WhatsApp, LINE, and Sunshine Conversations channels, see Migrating social messaging channels to Zendesk Agent Workspace.
This article includes these sections:
- About migrating Facebook Messenger and Twitter DM channels to the Zendesk Agent Workspace
- Understanding how migrations changes the Facebook Messenger and Twitter DM experience
- Disabling Facebook Messenger and Twitter DM in your Support admin settings
- Closing Facebook Messenger and Twitter DM tickets
- Adjusting your Facebook and Twitter DM business rules and views
Related articles:
About migrating Facebook Messenger and Twitter DM channels to the Zendesk Agent Workspace
If you already have an existing Facebook Messenger and Twitter DM integrations and you want to use Facebook Messenger and Twitter DM in the Zendesk Agent Workspace instead, you can manually migrate your Facebook Messenger and Twitter DM settings. However, there is no automatic migration or migration wizard to assist you with this process. Keep in mind that some of the required tasks are completed from your Support admin settings and others are performed from Admin Center.
You can migrate Facebook Messenger, or Twitter DM, or both.
You need to do the following, in this order:
- If you haven't already, enable the Zendesk Agent Workspace.
- Disable Facebook Messenger and/or Twitter DM in your Support admin settings as described below.
- Close your Facebook Messenger and/or Twitter DM tickets as described below.
- Add your Facebook Messenger and/or Twitter DM channels to the Zendesk Agent Workspace.
- Adjust your Facebook and/or Twitter business rules and views as described below.
- Set up auto-responders for your Facebook and/or Twitter DM channels.
Next steps:
- Make sure that your agents are set up to use the channels (see Getting started for administrators in the Zendesk Agent Workspace).
- Make sure that your agents understand that they will need to periodically merge Facebook end-user profiles and merge Twitter end-user profiles.
Understanding how migrations changes the Facebook Messenger and Twitter DM experience
Integrations for Facebook Messenger and Twitter DM in the Zendesk Agent Workspace are different from Facebook and Twitter integrations that configure in your Support admin settings that have private messaging enabled.
For example, the new integration includes these improvements:
- Attachments, keyboard shortcuts, and emojis are supported.
- Messages are delivered within a few seconds instead of minutes.
- The social messaging notifier is removed. You can use views to see your Facebook Messenger and Twitter DM tickets (instead of using the social messaging notifier).
- You can use the notifications list to manage your Facebook Messenger and Twitter DM conversations in the agent workspace.
The new integration also has some Facebook limitations and some Twitter limitations. We recommend that you review these before you migrate.
Disabling Facebook Messenger and Twitter DM in your Support admin settings
If you are migrating, you need to disable private messaging from your current Facebook and Twitter integrations before you add a Facebook Messenger and Twitter DM channels to the Zendesk Agent Workspace. You do this from your Support admin settings.
Immediately after you disable private messaging, you will not be able to receive or send private messages with Facebook Messenger or Twitter DM until you finish adding the Facebook Messenger and Twitter DM channels to the Zendesk Agent Workspace. We recommend that you plan accordingly to minimize service disruptions and do not delay setting up the new integration.
If, for some reason, you don’t disable private messaging, duplicate tickets are created when a private message from Facebook is received or a Twitter DM is received.
Do not disable your entire Facebook and Twitter integrations or other settings in these integrations since they are still used for public messaging.
To disable your current Facebook Messenger settings
- In Admin Center, click the Channels icon (
) in the sidebar, then select Messaging and social > Facebook Pages. - Open a Facebook page for editing.
- Disable Include private messages, and then click Update page settings.
To disable your current Twitter DM settings
- In Admin Center, click the Channels icon () in the sidebar, then select Messaging and social > Twitter accounts.
- From the Twitter accounts tab, open the channel for editing.
- Disable Capture incoming direct messages as tickets, and then click Update Twitter account.
Closing Facebook Messenger and Twitter DM tickets
If you are migrating, you must close your Facebook Messenger and Twitter DM tickets before you add a Facebook Messenger or Twitter DM channel to the Zendesk Agent Workspace.
To find and close your Facebook Messenger tickets
- If needed, create a view that includes only Facebook Messenger tickets.
The view must include the Channel + Is + Facebook Private Message condition.
Do not include conditions for Facebook Post. Otherwise, Facebook tickets that include only public messages may appear in the list of results. Do not include conditions for Facebook Messenger either (only use this condition after you complete migration).
For more information about creating views, see Creating views to manage ticket workflows.
- Click the Views icon (
) in the sidebar, then select your Facebook Messenger
view from the list. - Create a trigger to close all of the tickets in your Facebook Messenger view.
For information about how to do this, see Solving a ticket and understanding how it is closed and How can I manually close a ticket?.
To find and close your Twitter DM tickets
- If needed, create a view that includes only Twitter DM tickets.
The view must include the Channel + Is + Twitter DM condition.
Do not include conditions for Twitter, Twitter Like. Otherwise, Twitter tickets that include only public messages may appear in the list of results. Do not include conditions for Twitter Direct Message either (only use this condition after you complete migration).
For more information about creating views, see Creating views to manage ticket workflows.
- Click the Views icon () in the sidebar, then select your Twitter DM view
from the list.
- Create a trigger to close all of the tickets in your Twitter DM view.
For information about how to do this, see Solving a ticket and understanding how it is closed and How can I manually close a ticket?.
Adjusting your Facebook and Twitter DM business rules and views
- For Facebook Messenger channels in the Zendesk Agent Workspace, do not use the Facebook Private Message condition in your business rules and views. Use the Facebook Messenger condition for these channels instead.
- For Twitter DM channels in the Zendesk Agent Workspace, do not use the Twitter DM condition in your business rules and views. Use the Twitter Direct Message condition for these channels instead.
To adjust your Facebook and Twitter DM business rules and views
- Find all of your automations, triggers, and views that include conditions for
Facebook Private Message or Twitter DM.
For example, you may have a trigger that includes a condition statement that reads Channel + Is + Facebook Private Message.
Or, you may have a trigger that includes a condition statement that reads Channel + Is + Twitter DM.
- Change each instance of Facebook Private Message to Facebook Messenger.
- Change each instance of Twitter DM to Twitter Direct Message.
- Save your changes.
0 Comments
Please sign in to leave a comment.