Vote, Reply
A Vote on a Reply was an upvote that community members cast on an individual answer inside Salesforce Chatter Answers, the self-service support community that let customers ask questions and get replies from peers and support agents.
Definition
A Vote on a Reply was an upvote that community members cast on an individual answer inside Salesforce Chatter Answers, the self-service support community that let customers ask questions and get replies from peers and support agents. Each vote signaled that a reply was helpful, and the count nudged stronger answers higher so visitors could find good information faster.
This term is retired. Chatter Answers is no longer supported in Salesforce orgs (it stopped being supported as of the Spring '18 release, and new orgs lost it years earlier). Salesforce now points everyone to Chatter Questions, which uses a single Best Answer designation instead of a running vote tally. If you read "Vote, Reply" in an old runbook, treat it as historical context, not a feature you can switch on today.
How reply voting worked in Chatter Answers, and why it is gone
What Chatter Answers was
Chatter Answers was a self-service and support community feature. It combined the older Answers Q&A engine with Cases, Salesforce Knowledge, and the Chatter feed so customers could solve problems without phoning support. A visitor posted a question to a public zone, other community members and agents replied, and the thread stayed searchable for the next person with the same issue. Voting sat on top of that thread. Community members could vote on the helpfulness of each reply, which gave the community a lightweight way to rank answers by quality rather than just by time posted. The person who asked the question, or a moderator, could also flag one reply as the best answer. Chatter Answers grew out of the Answers feature, which Salesforce stopped offering to new orgs starting with Summer '13. For a stretch, Answers, Chatter Answers, and Chatter Questions all existed side by side, which is why old documentation mixes the three names. Knowing that lineage helps when you inherit a legacy org and find references to votes, replies, zones, and best answers scattered through configuration and reports.
What a vote actually did
A vote on a reply was an upvote, not a star rating or a thumbs-down. Casting one incremented a count attached to that specific reply. Replies with more votes carried a stronger helpfulness signal, so the community could see at a glance which answer most people found useful. This is different from Ideas, where members vote ideas up to show demand for a feature. Reply voting was narrower. It judged one answer to one question, not a backlog of requests. Voting and Best Answer worked together rather than competing. Votes were the crowd signal, gathered from many readers over time, while Best Answer was a single authoritative pick from the asker or a moderator. A thread could have a heavily upvoted reply and a separately marked best answer, and both helped a future visitor triage the thread quickly. The practical value was deflection. Every question a visitor resolved by reading a well-voted reply was a case your agents never had to open. That is the same logic Salesforce still uses today, just expressed through different mechanics in the newer Chatter Questions experience.
When and why it was retired
Salesforce retired Chatter Answers on a staged timeline. Answers stopped being available in new orgs from Summer '13. Chatter Answers itself is no longer supported in all Salesforce orgs as of the Spring '18 release, and the official retirement guidance tells admins to begin transitioning to Chatter Questions as soon as possible. No action was required for customers building new organizations from the Summer '16 release onward, because those orgs were already steered toward the newer feature. The reasoning Salesforce gives is straightforward: the Q&A experience in Chatter Questions is easier to use and improves the experience and service. Maintaining three overlapping Q&A products (Answers, Chatter Answers, Chatter Questions) split engineering effort and confused admins. Consolidating onto one model that lives inside the Chatter feed simplified the offering. For you, the takeaway is that any vote count stored against an old reply is frozen history. You cannot recreate the voting widget, and you should not design new processes around it. If you still run a legacy zone, plan a migration rather than an extension.
What replaced it: Chatter Questions and Best Answer
Chatter Questions is the supported successor. It is a Q&A feature built directly into the Chatter feed, so people ask and answer without leaving the conversation they are already in. It carries full Chatter functionality, including topics, likes, bookmarks, and @mentions, which gives it richer interaction than the old standalone zones. The ranking model changed. Instead of an ongoing reply vote tally, Chatter Questions centers on a single Best Answer. Moderators and the question asker can designate one answer as best. A checkmark appears next to it, and a copy of the best answer is pinned to the top of the answer list so other users spot it immediately. In search and feed views, a question with a chosen best answer shows a green checkmark with the text Best Answer. Likes still exist as a per-post reaction, so the social signal a vote used to carry now lives in the standard Chatter Like. Chatter Questions also adds deflection at the moment of asking. As a user types a question, similar questions and Salesforce Knowledge articles surface in a dropdown so they can self-serve before posting anything new.
Migrating from votes to the new model
If you maintain an org that still references Chatter Answers, treat the move to Chatter Questions as a real project, not a toggle. Start by inventorying where the old feature shows up: zones, the Chatter Answers tab, list views, reports built on the Question and Reply objects, and any automation that watched vote-related fields. Decide what historical content matters. High-value questions with strong answers are worth preserving, and you can recreate them as Chatter Questions or convert the underlying knowledge into Salesforce Knowledge articles for long-term reuse. Set up Question-to-Case so unanswered or escalating questions can become Cases for your agents, which keeps the support loop intact once the old self-service zone is gone. Enable Similar Articles and Similar Questions on the question composer so the deflection that votes used to provide now happens through Knowledge surfacing instead. Communicate the change to community members, because the voting affordance they were used to clicking simply will not be there. Finally, retire the old zones cleanly so no one stumbles onto a dead feature and files a confused case about missing vote buttons.
Reading old data and reports
Even after retirement, traces of reply voting can linger in an org's data and metadata. You may find report types, dashboards, or saved list views that reference vote counts or the Reply and Question objects from the Answers era. None of these will collect new votes, but they can still display historical numbers, which is useful for an audit or a content cleanup. When you encounter a field or column labeled around votes or upvotes on a reply, confirm whether anything reads it before you delete it, since old integrations sometimes touched these fields. If you are documenting the org for a handover, label this area clearly as legacy so the next admin does not waste time trying to switch it back on. The cleaner long-term answer is to migrate the genuinely useful Q&A content into Chatter Questions or Knowledge, then deprecate the stale reports. That way the helpful answers a community once voted up keep serving visitors through a supported feature, instead of sitting in a frozen tab that no one maintains and search engines slowly stop crawling.
Trust & references
Cross-checked against the following references.
- Chatter Answers RetirementSalesforce
- Select a Best Answer for a Question in ChatterSalesforce
Straight from the source - Salesforce's reference material on Vote, Reply.
Hands-on resources to go deeper on Vote, Reply.
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. In Chatter Answers, what does casting a Vote on a Reply do to that reply?
Q2. Which Chatter Answers feature works alongside Reply Vote tallies to flag one definitive answer?
Q3. How does a Vote on a Reply differ from a vote cast in Salesforce Ideas?
Discussion
Loading discussion…