Setting up your Twitter channel

Fastpath: Admin > Channels > Twitter

All Zendesk Suite and Zendesk Support customers can add at least one Twitter account so that public messages, such as public mentions, public replies to your Tweets, and public likes to Tweets, become tickets. Your agents will be able to see and respond to these tickets from the Support interface, just like any other ticket.

Additionally, Zendesk Suite customers can add multiple Twitter accounts and they can receive public messages and private messages (Twitter direct messages) from those accounts.

Zendesk Support plans	One Twitter handle with public messages only. Private messages are not supported.
Zendesk Suite plans	Up to 5 Twitter handles with public and private messages. Note: This applies to some legacy customers as well. See Adding Twitter accounts to Support for details.

You must be an administrator to add a Twitter account to Support.

This article includes these sections:

• How the Twitter channels works
• Adding Twitter accounts to Support
• Editing Twitter account settings
• Removing Twitter accounts from Support
• Appending ticket links to outgoing tweets
• Managing Twitter tickets with business rules
• Understanding why your Twitter account might be deauthorized

How the Twitter channels works

Zendesk Support monitors Twitter accounts and converts tweets to tickets as needed. All tweet activity between agents and Twitter users is added as ticket comments. Using the Twitter channel, you can do the following:

• Convert a tweet into a ticket and respond to the user with a tweet, or move the conversation to email
• Bulk convert multiple tweets into tickets in one step
• Convert tweets to tickets outside of Zendesk Support by liking a tweet in twitter.com and many other Twitter clients
• Automatically capture public mentions and direct messages as tickets
• Append ticket links to outgoing tweets
• Select which of your accounts agents are allowed to use when sending outgoing tweets
• Monitor and take action on Twitter activity using business rules

Only administrators have access to the incoming tweets. However, once they have been converted to tickets, all agents have access to Twitter tickets, unless you have restricted agent access to certain types of tickets.

Once a tweet becomes a ticket, it behaves just like any other ticket in Zendesk Support, except that you have the option of replying back to the Twitter user with a public tweet or moving the conversation to email.

You can control if and how incoming tweets become tickets. The approach you take might be based on your overall Twitter traffic or the number of agents you have available. Here are several scenarios for managing incoming tweets:

• Likes. Convert tweets outside of Zendesk Support by liking them in your Twitter client. This approach allows you to manually choose tweets to convert before they ever reach Zendesk Support.
• Mentions and direct messages. Automatically create tickets from public tweets that contain your Twitter account handle or from direct messages. Sometimes, tickets that are not support requests and that don't need follow-up are created. You can manage these out of your ticket queue by manually solving and closing or deleting them. Group direct messages are not supported and do not create tickets.
• Triggers. Use one or more triggers to monitor new support requests that originate from your Twitter channel. You can use the trigger condition Ticket Channel, which has the following three Twitter sources: Twitter, Twitter DM (direct message), and Twitter Like. The advantage to this approach is that you have much more control over the creation and management of Twitter-based tickets. See Managing Twitter tickets with business rules below.

Note the following limits:

• It can take up to 15 minutes for a ticket to be created from a tweet.
• Each Twitter ticket has a limit of 5,000 comments. After reaching the limit, Zendesk stops importing new tweets as comments on the ticket.

If you are looking for information about how agents work with Twitter-generated tickets, see Managing tickets from Twitter.

Adding Twitter accounts to Support

Note: If you are a Suite customer, you must install social messaging before you can set up Twitter (see Installing and setting up social messaging).

You can add a Twitter account to your Zendesk account so that Tweets become tickets, and your agents can see and respond to these tickets, just like any other ticket.

The number of Twitter handles and the type of messaging supported by your account depends on your plan type.

Zendesk Support plans	One Twitter handle with public messages only. Private messages are not supported.
Zendesk Suite plans	Up to 5 Twitter handles with public and private messages. This also applies to the following legacy customers: Support customers as of January 31, 2020 with an existing Twitter setup Support customers with the legacy Social Messaging add-on Legacy Support Suite customers

If you are using Agent Workspace and Twitter private messaging is supported for your account, you need to take an additional step to enable private messages after you add your Twitter account.

To add a Twitter account

1. Click the Admin icon (), then select Channels > Twitter.
2. Select the Twitter accounts tab.
3. Click Add Twitter account.
4. You'll be prompted to log in to Twitter and then authorize Zendesk Support to use your account. Enter your login information and then click Authorize App.

After your account has been authorized, your newly added Twitter account will be listed on the Twitter accounts tab. You'll want to edit the account's settings to control how tweets to this account are handled (see Editing Twitter account settings).

If you are using Agent Workspace, and Twitter private messaging is supported for your account, you need to take an additional step to enable private messaging.

Editing Twitter account settings

After you've added a Twitter account, you'll want to edit the account's settings to control how tweets to this account are handled (see Editing Twitter account settings for descriptions of the settings).

You can choose to automatically convert public mentions and direct messages into tickets (Capture public mentions as tickets and Capture incoming direct messages as tickets). If you enable these, the option to manually convert tweets to tickets will no longer be available for that Twitter account.

By default any responses to a tweet will be from the account the tweet was directed to. You can select a different account from the Reply as drop-down list under the ticket reply box. If you want to automatically respond from one account, you can disable Allow replies via this account when editing your other Twitter accounts (see Editing Twitter account settings).

To edit settings for a Twitter account

1. Click the Admin icon (), then select Channels > Twitter.
2. Select the Twitter accounts tab.
3. Click Edit beside the Twitter account you want to edit.
4. Update settings as needed.

   The settings are described in the following table.

5. Click Update Twitter account.

Setting	Description
Allow replies via this account	This setting allows agents to use this Twitter account when replying to a Twitter ticket. Agents can select the account below the reply box on a Twitter ticket: Replies to tickets from Twitter retain the original inbound format. For example, if the ticket was created from a direct message (DM), then the agents reply from within Zendesk will also be a DM. If the ticket was created from a tweet mentioning your Twitter handle (for example @Zendesk), then the agents reply from within Zendesk will be a reply tweet, threaded to the senders original mention.
Make this the default account	Note: This setting appears in the Support interface when Allow replies via this account is set to yes. Use this Twitter account by default to reply to tickets that were created from tweets to your other Twitter accounts that don’t allow replies. When yes, the Reply as drop-down list shows the name of this Twitter account by default. However, agents can still choose a different reply-enabled Twitter account from the drop-down list, if desired and available. You can only have one default account at a time. Your old default account becomes a non-default account set to no. Bulk updating tickets Setting a default Twitter account can affect bulk ticket updates in a few ways. When a customer replies to a Twitter account that allows replies: If the Twitter account is the default account, agent replies are sent from that account. If a different, separate Twitter account is the default Twitter account, agent replies are sent from the default Twitter account instead of the account that the customer initially replied to. When a customer replies to a Twitter account that doesn't allow replies: If there is a default Twitter account, agent replies are sent from the default Twitter account. If there is no default Twitter account, an error appears in Support because the Twitter account doesn't allow replies. For information about how to bulk update tickets, see Bulk updating tickets.
Capture public mentions as tickets	This automatically converts any public tweet containing your Twitter account handle (for example, @mondocam) to a ticket.
Capture incoming direct messages as tickets	This automatically converts incoming direct messages into tickets so that your customers can contact you privately rather than publicly. Depending on your Twitter settings, you can either receive direct messages from anyone or only from Twitter users you follow. You can reply to anyone who sends you a direct message.
Track Likes	This automatically converts a tweet that you like to a ticket. For example, if you're managing your Twitter stream using twitter.com, you have the option of manually liking the tweet by clicking the heart icon.

Removing Twitter accounts from Support

You can remove a Twitter account from Support by deactivating it or unlinking it. If you deactivate an account, it is inactive in Zendesk Support and you can reactivate it at any time. If you unlink an account, it is removed from Zendesk Support.

To deactivate a Twitter account

1. Click the Admin icon (), then select Channels > Twitter.
2. Select the Twitter accounts tab.
3. Click Deactivate beside the Twitter account you want to deactivate.

   

   The Twitter account is deactivated. It will not turn tweets into tickets and you cannot reply using it. You can reactivate account at any time. 

To unlink a Twitter account

1. Click the Admin icon (), then select Channels > Twitter.
2. Select the Twitter accounts tab.
3. Click Unlink beside the Twitter account you want to remove from your Twitter channel.
4. Click OK to confirm.

   The Twitter account is unlinked.

Appending ticket links to outgoing tweets

Another option for your outgoing Tweets is to append a shortened URL to the ticket you created from the tweet. This allows the Twitter user to access the ticket page in the Web portal via their Twitter account. In other words, remote authentication is used to log in through Twitter to Zendesk Support (end-users must sign in to Zendesk to see the ticket page).

Once a Twitter user has access to the ticket page, they can add a longer comment than they could have in Twitter given the 280 character limit of a tweet. They can also update their user profile (adding their email address for example).

Note: If you started using Zendesk on or after August 21, 2013, this option is not available until you activate your Help Center. See Getting started with Guide.

You have the option of allowing the agent to decide if a shortened or the original URL is used in the response. And, you can choose one of several URL shortening services to use.

To append ticket links to outgoing tweets

1. Click the Admin icon (), then select Channels > Twitter.
2. Select the General settings tab.
3. Enable the ticket links by clicking Yes next to the Append ticket links to outgoing tweets? option.
4. If you want agents to decide when to use shortened URLs, deselect the Always include shortened ticket URL option. It is selected by default.
5. Click Save tab.

Managing twitter tickets with business rules

A number of conditions are available to manage your Twitter tickets using business rules.

Like the other Zendesk Support channels, you can detect a ticket's source using the Ticket Channel condition in automations, reports, triggers, and views. There are three Twitter source types you can use in the Ticket Channel condition: Twitter, Twitter DM (direct message), and Twitter Like.

If, for example, you wanted to create separate views of each of the Twitter source types, you simply choose the Ticket Channel condition and then select the type.

In addition to the Twitter channel source types, you also have three other Twitter conditions that are available in triggers:

• Requester's Twitter followers are...
• Requester's number of tweets is...
• Requester is verified by Twitter

The first two conditions help you to determine how active and potentially influential a Twitter user is, which may influence how you manage their tweets. For example, you might want to set Twitter tickets from more highly visible Twitter users to Urgent so that you respond as quickly as possible. Here's an example of what a trigger like that might look like:

The Requester is verified by Twitter condition is a special type of Twitter account that has had its identity verified by Twitter (by submitting proof of business, for example). Knowing that a Twitter account has been verified may be important to you in determining how to handle Twitter tickets. For more information, see FAQs about Verified Accounts in Twitter help.

And of course, you can also adds tags to your Twitter tickets and use them to manage your Twitter tickets through your workflow.

Understanding why your Twitter account might be deauthorized

Zendesk Support constantly monitors your Twitter accounts for new public mentions and direct messages. If Zendesk Support cannot connect with your Twitter account, it will send an email notification to all admins on your account.

If you receive notification that a Twitter account has become deauthorized, you need to reauthorize the affected Twitter account in Zendesk Support.

To reauthorize your Twitter account

• Click the Admin icon () in the sidebar, then select Channels > Twitter.

Common reasons your Twitter account might become deauthorized include:

• The password on your Twitter account has changed.
• The Twitter account no longer permits Zendesk Support to view its timeline and tweet on its behalf.

  This can happen if the Zendesk Support Twitter app has been removed from your Twitter account’s list of allowed apps.

• Zendesk Support receives a consistent response from Twitter indicating that we are not authorized to access your Twitter account’s content.

  This should only happen due to an error in Twitter’s platform.