Social Handle
A social handle is the username a person uses on a social network, such as a Twitter (now X) @name, stored on an Account, Contact, or Lead record.
Definition
A social handle is the username a person uses on a social network, such as a Twitter (now X) @name, stored on an Account, Contact, or Lead record. In Salesforce it was the link between a CRM record and that person's public social presence, part of the Social Accounts, Contacts, and Leads feature.
This feature is retired. Salesforce shut it down in 2023 after Twitter/X revoked access to the public APIs it depended on, so a social handle field is no longer populated or surfaced by any standard Salesforce social component. The concept survives only as background for older orgs and as context for how Salesforce treats social data today.
How social handles worked, and why the feature was retired
What a social handle actually was
A social handle was a small piece of identity data. It told Salesforce which account on a social network belonged to the person sitting in a given record. For Twitter that meant the @name, for example @salesforce. Earlier versions of the feature also recognized profiles on LinkedIn, Facebook, YouTube, and the now-defunct Klout score. The handle was not free text that you typed and forgot. When you associated a profile, Salesforce searched the social network by name (and by company for LinkedIn), showed you the matching profiles, and let you pick the right one. That choice stored a reference to the social account, and the person's profile photo then appeared as the record photo on the Contact or Lead. So the handle did two jobs at once. It identified the person on the platform, and it gave the CRM record a face. Without a correct handle, none of the social content that the feature promised could load, because Salesforce had nothing to look up.
Live data, never stored in Salesforce
The most important design detail is one that surprised a lot of admins. Salesforce did not import or store any social information behind a handle. It kept only the link to the chosen profile. Every time you opened a record and looked at the social panel, Salesforce reached out to the network in real time and pulled the tweets, the bio, the follower count, and the photo for that session. This had real consequences. The data you saw was always current, because it was fetched fresh, but it also meant the feature lived or died by the network's API. There was no local cache to fall back on. Authentication used OAuth, so a user signed in to their own Twitter or LinkedIn account and saw content through their own access and the target person's privacy settings. Two reps could open the same record and see slightly different things. Nothing about the social profile sat in your Salesforce database as a queryable field, which is exactly why the feature could vanish the moment the API closed.
Who could set it and what they saw
Associating a profile was an edit action, so only users with edit access to the Account, Contact, or Lead could link or change a social handle. Once linked, viewing rights were broader. Other users could open the record and see the social panel, subject to their own social network sign-in and the target account's privacy. Admins turned the whole thing on under Setup, in the Social Accounts and Contacts settings, and chose which networks were available. For orgs created after Spring '12 it was on by default, so many companies had it running without anyone deciding to use it. Individual users then opted in through their personal settings and signed in to the networks they cared about. In practice the value showed up most in social selling and light social customer service. A rep prepping for a call could glance at recent tweets, or a service agent could confirm they were talking to the right person by matching the handle to the case at hand.
The Twitter/X API change that ended it
The feature did not fade away on its own. It was killed by a single external decision. On August 23, 2023, Twitter/X revoked the free public API access that a large set of integrations relied on. Salesforce was one of many affected vendors, alongside roughly thirty AppExchange apps and hundreds of code repositories that touched the same APIs. Because Social Accounts, Contacts, and Leads pulled everything live, removing the API removed the feature's entire reason to exist. By this point the other networks had already dropped out over earlier platform changes, so the connector was effectively Twitter-only when the door closed. Salesforce announced the retirement in its release notes, first as a heads-up that it was being retired and then as a confirmation that it was gone. The component stopped surfacing profiles, social posting through it stopped working, and engagement statistics for previously published posts could no longer be retrieved. Any handle references already stored simply had nothing to resolve to.
What to do with old social handle data
If you support an org that used this feature, the cleanup is usually small. The social profile association no longer drives anything, so there is no live integration to unwind. Profile photos that came from the feature may still appear as stale record images, and any custom fields a team built to copy a handle into a text field are now just static strings. The practical move is to treat leftover handles as plain reference data. Audit Contacts and Leads for fields that mention Twitter, X, or social, and decide whether to keep them for context or clear them. If a workflow, report, or screen still points at the retired social panel, expect it to be empty and remove the reference so users are not confused. None of this is urgent, because nothing is calling an external service anymore. It is more about tidiness and not leaving a dead feature half-wired into your page layouts and automation.
Where social engagement lives now
There is no like-for-like replacement that drops a live social feed onto a standard record the way this feature did. Salesforce instead pointed customers toward partner apps on AppExchange for in-record social display, and toward its dedicated marketing and engagement products for the heavier work. For listening, publishing, and social customer care, that role moved to the Marketing Cloud family, including the Social Studio era tooling, rather than a panel inside the core CRM. The longer arc is that Salesforce stopped trying to graft a single network's profile onto each record and moved toward unified customer profiles. Data Cloud and the broader Customer 360 idea pull identity and behavioral signals from many sources into one resolved view, which is a sturdier model than depending on one platform's free API. So while the social handle as a field is retired, the goal it served, knowing your customer across channels, is now handled by tools built to survive any single network changing its rules.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Social Handle.
Hands-on resources to go deeper on Social Handle.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. Which of the following is a typical example of a Social Handle on a Salesforce contact record?
Q2. What is a Social Handle in the Salesforce Social Accounts and Contacts feature?
Q3. What does linking a Social Handle to a Salesforce record enable for an account team?
Discussion
Loading discussion…