Google Talk
Google Talk was Google's instant-messaging product, launched in 2005 and folded into Hangouts before being shut down in 2017.
Definition
Google Talk was Google's instant-messaging product, launched in 2005 and folded into Hangouts before being shut down in 2017. In Salesforce, Google Talk was one of the services you could turn on as part of the Google Apps integration. Once activated, it added a presence indicator and a chat link to the application, letting users see who was online and start an instant-message conversation without leaving Salesforce. The feature is now retired. Salesforce Help states plainly that "Google Talk within Salesforce is no longer available" and points admins to deactivate it.
This page is reference material for a feature that no longer works. If you administer an older org, you may still see a Google Talk node under the Google Apps settings, or training documents that mention it. Activating or reactivating it does nothing useful, because the Google service it depended on no longer exists. The sections below explain what Google Talk in Salesforce did, why it was retired, how to clean it up, and which current tools cover the same online-presence and chat needs.
What Google Talk did inside Salesforce, and what to do now
Where Google Talk fit in the Google Apps integration
Salesforce shipped a built-in integration with Google Apps, the productivity suite that later became Google Workspace. An admin set up the integration in Setup by creating or linking a Google Apps account, entering the registered domain, and naming a Google Apps administrative contact. After that, several Google services appeared in the Google Apps Settings area, ready to be turned on individually. The classic trio was Add Google Docs to Salesforce, Gmail to Salesforce, and Google Talk. Each had its own activate or edit control. Google Talk was the lightweight, real-time piece of the suite. Where Google Docs handled documents and Gmail handled email logging, Google Talk handled live chat and online status. Turning it on did not require a separate AppExchange package; it was part of the native Google Apps feature set in editions that supported it. Users still needed individual Google Apps accounts on the organization's registered business domain, not consumer Gmail addresses, for the service to recognize them. That domain requirement is the same one that governed Gmail and Docs activation.
Presence indicators and click-to-chat
The visible payoff of Google Talk in Salesforce was presence. When the service was active, Salesforce showed an online-status indicator tied to a user's Google Talk account, so you could tell at a glance whether a colleague was available before reaching out. Alongside the indicator, the feature surfaced a chat link that opened a Google Talk conversation window, letting you start an instant message from inside the application. This was a convenience layer rather than a data feature. Nothing about Google Talk wrote records, logged activities, or fed reports. It simply mirrored a user's Google chat presence and gave a one-click path into a chat. Because the status came live from Google's service, it was only as reliable as that service and the user's Google session. If a user was not signed in to Google Talk, or used a personal account that did not match their Salesforce business domain, the indicator showed them offline. Admins typically paired Google Talk with Gmail and Docs so a sales or support team had email, documents, and chat presence in one Google-connected workspace.
Why the feature was retired
Google Talk in Salesforce stopped working because the Google product underneath it went away. Google launched Google Talk in 2005, began steering users to Hangouts around 2013, and fully shut down the original Google Talk service in 2017. Google Chat later became the successor for Workspace customers. Each of those moves changed or removed the chat service that Salesforce was reading presence from. Once Google retired Talk, there was no live status for Salesforce to display and no chat endpoint for the chat link to open. The integration could not be kept alive on the Salesforce side, because the dependency was entirely external. Salesforce responded by retiring the feature and updating its documentation. The Google Apps administration page now tells admins that Google Talk within Salesforce is no longer available and links to deactivation steps. This is a common shape for retirements that hinge on a third party: the partner ends the underlying service, the connector has nothing left to talk to, and the vendor formally withdraws the feature rather than leave a broken control in Setup.
How to deactivate it in an inherited org
If you took over an org that still lists Google Talk, the safe move is to deactivate it and stop relying on any presence it claims to show. In Setup, open the Google Apps area, find the Google Talk service among the Google Apps Settings, and deactivate it from there. Salesforce's own guidance for the retirement is to deactivate the service, so this is the supported path rather than a workaround. Deactivating removes the dead presence indicator and chat link from the user experience, which prevents confusion when colleagues see a status that never updates. While you are in the Google Apps settings, review whether Gmail to Salesforce and Add Google Docs to Salesforce are still appropriate, since those are separate services with their own current or deprecated status. Treat the cleanup as part of normal technical-debt hygiene. Note what you removed, when, and why, so the next admin does not rediscover the same dead feature and waste time trying to make it work. A short internal note listing retired integrations pays for itself the first time someone audits the org.
Current ways to get presence and chat
The need Google Talk served, knowing who is available and starting a quick chat, is now met by other tools. For customer-facing conversations, Salesforce Chat (the web-chat channel formerly called Live Agent) lets service agents handle real-time chats, and agent availability is managed through Omni-Channel presence and routing. For internal collaboration, Slack is the deeply integrated messaging product across Salesforce, and Slack carries its own presence and direct-messaging. Teams that live in Microsoft Teams use that platform's own integrations for similar internal chat. If your real goal is connecting Google Workspace to Salesforce today, the modern path is not a chat-presence widget at all. Einstein Activity Capture connects Gmail and Google Calendar to sync emails and events against Salesforce records. Developers who want chat-style notifications into Google's chat product can build them with webhooks and APIs, as Salesforce's own developer materials describe for Hangouts Chat. The point is to choose the tool that matches your primary messaging platform rather than to revive a retired connector.
A worked example of the cleanup
Picture inheriting a long-running org where users complain that the little online dot next to names is always grey. You open Setup and search Google Apps, and you find the Google Apps Settings with Google Talk still showing as an activated service. First, confirm the symptom: the presence never turns green because the Google Talk service it queried was shut down by Google years ago. Second, check Salesforce Help, which confirms Google Talk within Salesforce is no longer available and tells you to deactivate it. Third, deactivate Google Talk from the Google Apps settings. The grey indicator and the chat link disappear from the interface. Fourth, decide what replaces it. If the team runs on Slack, point them to the Slack integration and its native presence. If they are a service team, set up Salesforce Chat and manage availability through Omni-Channel. Finally, record the change in your runbook. The whole task is small, but skipping the documentation step is how the next person ends up filing a case about a feature that was never coming back.
Reading old Google Talk references safely
Because Google Talk shipped with Salesforce for years, it shows up in old blog posts, community answers, study notes, and even some Trailhead-era material. Treat all of it as historical. The activation steps, screenshots of the presence indicator, and any tips about pairing Google Talk with Chatter describe a feature that no longer functions. The only durable facts worth carrying forward are the timeline and the lesson. Google Talk was the early Google chat product, it gave Salesforce users a presence indicator and a chat link through the Google Apps integration, Google retired the service in 2017, and Salesforce withdrew the feature in turn. If a piece of documentation tells you to activate Google Talk to enable presence, stop and check the current Google Apps help page, which will redirect you to deactivation. This is also a useful pattern to recognize across Salesforce and Google retirements generally: when a partner sunsets an API or service, the Salesforce-side connector tends to fail quietly and then gets formally retired, so old how-to content ages out faster than the org metadata that still references it.
Trust & references
Cross-checked against the following references.
- Google Apps (Salesforce Help)Salesforce
- Use Google Talk in SalesforceSalesforce
Straight from the source - Salesforce's reference material on Google Talk.
- Get Started with Salesforce and Google AppsSalesforce
- Set Up Google Apps in SalesforceSalesforce
Hands-on resources to go deeper on Google Talk.
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. What did the Chatter Plus for Google Apps package add to Salesforce while Google Talk was still alive?
Q2. After Google retired Google Talk, why did the Chatter Plus presence widget fail quietly rather than throw an error?
Q3. A team that once relied on Google Talk presence now wants internal messaging surfaced on Salesforce user records. Which current path fits?
Discussion
Loading discussion…