Chatter Answers
Chatter Answers is a retired Salesforce Service Cloud feature that combined a Chatter-style feed, the older Answers community feature, and Salesforce Knowledge articles into a single customer self-service surface.
Definition
Chatter Answers is a retired Salesforce Service Cloud feature that combined a Chatter-style feed, the older Answers community feature, and Salesforce Knowledge articles into a single customer self-service surface. Customers asked questions in a public feed, received replies from other community members or support agents, voted on the most helpful response, and could escalate an unresolved question into a Case. It was Salesforce's early attempt at a unified community-plus-support product, and it shipped before Communities (now Experience Cloud) matured into the platform that carries this work today.
Salesforce retired Chatter Answers in the Winter '18 timeframe and pointed customers to Chatter Questions inside Experience Cloud sites as the replacement. Existing orgs could keep using it until their subscription term ended, but no new setup is possible and the data must be migrated. If you read pre-2018 documentation, a partner blog, or older certification material that mentions Chatter Answers, treat it as a legacy name. The modern equivalent spans several products: Experience Cloud for the site, Chatter Questions for the Q&A, Knowledge for articles, Question-to-Case for escalation, and Case Deflection to surface answers before a Case is filed.
How Chatter Answers worked and what carries the work now
What Chatter Answers actually was
Chatter Answers presented a public feed where customers posted questions in plain language. Other customers, support agents, and product experts replied in threaded responses. The person who asked the question, or a moderator, could mark a reply as the best answer so future visitors saw the resolution first. Salesforce Knowledge articles appeared inline, so a customer searching for help often found a published answer without posting anything. When self-service was not enough, an agent or moderator escalated the question into a Service Cloud Case, which preserved the conversation history and routed it through normal support handling. The feature was exposed as a Chatter Answers zone, which administrators configured in Setup and embedded in a Customer Portal, a Force.com site, or an early Community. It leaned on the Question and Reply objects rather than the standard Chatter feed. That separate data model is a big reason the feature was eventually folded into the mainstream Chatter feed, where questions became Feed Items and replies became Feed Comments.
Why Salesforce retired it
Two products ended up solving the same problem. As Communities (now Experience Cloud) matured, it offered a richer site builder, more templates, and tighter Knowledge and Case integration than a Chatter Answers zone could. Maintaining a separate Q&A product on its own Question and Reply objects meant duplicate configuration, duplicate reporting, and a parallel data model that did not share the standard Chatter feed. Salesforce consolidated the strategy onto Chatter Questions, a Feed Item based feature that lives directly in the Chatter feed and inside Experience Cloud sites. The retirement was announced for the Winter '18 release. Orgs already on Chatter Answers could keep using it until their subscription term ended, but the path forward was clear: stand up an Experience Cloud site, enable Chatter Questions, and migrate the old data. Salesforce framed the change as Chatter Answers passing the torch to Chatter Questions, which delivered a simpler experience that fit naturally into the broader Chatter and Experience Cloud surface rather than sitting beside it as a separate zone.
Chatter Questions: the direct replacement
Chatter Questions is the feature Salesforce named as the successor. Instead of a separate zone backed by Question and Reply objects, a question is a standard Feed Item posted in the Chatter feed or in an Experience Cloud site. Members reply in the feed, upvote helpful answers, and an asker or moderator selects a best answer that pins to the top of the thread. Because it rides the normal feed, Chatter Questions inherits the same notifications, mentions, topics, and moderation tools as any other Chatter post, which removes the parallel plumbing Chatter Answers required. Administrators enable it under the site's collaboration features, and optional upvotes and downvotes let the community rank responses. The practical effect for a customer is familiar: ask a question, get answers from peers and agents, see the accepted answer first. The practical effect for an admin is a single feed model to configure, secure, and report on, rather than a second Q&A engine running in parallel. This is the piece you build when someone asks you to recreate the question-and-answer behavior Chatter Answers used to provide.
Experience Cloud templates carry the site
Chatter Answers bundled the site, the Q&A, and the Knowledge browsing into one zone. Modern Salesforce splits that across Experience Cloud templates. The Customer Service template (historically called Napili) is the full self-service site. It bundles Knowledge articles, Chatter Questions, Case management, and Case Deflection into a public or login-based site with far more layout control and branding than a Chatter Answers zone ever offered. For orgs whose self-service is mostly article browsing with the occasional question, the Help Center template is a lighter, more focused option centered on Knowledge. Choosing between them is a real design decision: Customer Service when you need community Q&A and Case logging, Help Center when you mainly need a polished article library. Either way, the site is built in Experience Builder with Lightning components, so you get responsive layouts, theming, and audience targeting that the older zone could not match. When you migrate off Chatter Answers, picking the right template is usually the first architectural step before any data moves.
Escalating a question into a Case
One of the strongest parts of Chatter Answers was that an unresolved question did not disappear into a forum. It could become a Case so support owned it formally. That capability survives as Question-to-Case in Experience Cloud sites. When a community question needs a human owner, a moderator or an agent escalates it into a Case from the feed, and the question stays linked to the Case for context. Administrators enable Question-to-Case in Setup and can let moderators escalate manually, or use Process Builder or Flow to escalate automatically when a question matches certain criteria. This keeps the peer-to-peer feed for quick wins while routing the hard problems into the same queues, assignment rules, and SLAs that govern every other Case. The result is the same outcome Chatter Answers aimed for, a smooth handoff from community discussion to tracked support, but built on the standard Case object and the modern feed rather than on the legacy Question object. If your old design relied on escalation, Question-to-Case is the feature to map it onto.
Knowledge and Case Deflection close the loop
Chatter Answers showed Knowledge articles inline so customers could self-serve before posting. Two modern features cover that ground with more precision. Salesforce Knowledge remains the article repository, and Experience Cloud templates surface those articles in search and on topic pages so a customer often finds the answer without asking anyone. Case Deflection goes further: as a customer types a question or starts to file a Case, it suggests matching Knowledge articles and existing community answers, then records whether the customer proceeded anyway. That deflection signal lets the team measure how much article content is actually preventing Cases, something the original Chatter Answers deflection could only hint at. Together, Knowledge plus Case Deflection plus Chatter Questions reproduce the full self-service loop Chatter Answers tried to deliver in one zone, but each piece is now a dedicated, better-instrumented feature. For an architect, this is the menu to assemble when recreating the experience: Knowledge for content, Case Deflection to reduce volume, Chatter Questions for community Q&A, and Question-to-Case for the handoff.
Migrating off Chatter Answers
Migration is data work plus a site rebuild. Salesforce provided the Salesforce Q&A Migration app to move legacy data into the feed model. Question records convert to Feed Items, Reply records convert to Feed Comments, and Vote records convert to Feed Likes, so the conversation survives in the new structure. There are limits to plan for: a Feed Comment holds only the first 10,000 characters of a longer reply, so very long answers can be truncated. Before running the migration, the org needs the right permissions enabled, including Create Audit Fields so original timestamps and authors are preserved, and the permission to migrate feed content into the community. The broader project means standing up an Experience Cloud Customer Service or Help Center site, enabling Chatter Questions and Question-to-Case, wiring up Knowledge and Case Deflection, then retiring the old Chatter Answers zone. Reports that ran on the Question and Reply objects do not carry over and must be rebuilt against Feed Items. Most orgs completed this transition between 2017 and 2020. If you inherit an org still referencing Chatter Answers, that migration is the cleanup waiting for you.
Trust & references
Cross-checked against the following references.
- Chatter Answers RetirementSalesforce
- Question-to-Case OverviewSalesforce
Straight from the source - Salesforce's reference material on Chatter Answers.
- Enable Chatter Questions in Your Experience Cloud SiteSalesforce
- Chatter Answers RetirementSalesforce
Hands-on resources to go deeper on Chatter Answers.
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 three capabilities did Chatter Answers combine into one self-service surface?
Q2. What drove Salesforce to retire Chatter Answers in Summer 18?
Q3. Which combination is the documented modern replacement for Chatter Answers?
Discussion
Loading discussion…