Zendesk takes feature requests in the Product feedback space of its community, where each request collects votes and carries a status set by Zendesk's product managers. The community moved to community.zendesk.com in March 2026, and most requests from the old one came with it. Every request on the board was read on 4 October 2026, 7,761 in all, filed from December 2008, with status, votes, replies, views, product area and dates.
477 of them, 6.1 percent, are marked Delivered, and 1,252, or 16.1 percent, Accepted. Votes draw a sharp line: 87.9 percent of requests with four votes are still waiting at Feedback submitted, against 14.3 percent of those with five.
host,id,created,last_activity,status,votes,likes,views,replies,areas
community.zendesk.com,5425,2009-10-22,2024-10-15,Parked,487,0,1005,518,64
community.zendesk.com,7332,2012-06-29,2025-07-15,Delivered,466,0,1210,460,43
community.zendesk.com,22644,2026-10-02,2026-10-02,Feedback submitted,1,0,6,0,66
Download the file, one row per request, compressed with gzip. It is free to copy, quote and use commercially. To cite it, link https://votefirst.app/en/data/zendesk-feature-requests and give the read date, 4 October 2026. Each row names the request's number, which ends its address on the board: the first row above is request 5425. The areas column holds Zendesk's product area numbers: 64 Support, 43 Knowledge, 56 Community, 57 Chat and messaging, 65 Voice, 62 Analytics, 68 Workforce management, 67 Quality assurance, 66 AI, 51 Admin center, 58 Platform and 63 Sell.
How do you submit a feature request to Zendesk?
Sign in to the Zendesk Community and post it in Product feedback, with Create a post or Share product feedback. Zendesk's product feedback guidelines, posted on 31 March 2026, ask for a search first, and an upvote with your own use case on an existing request in place of a new post or a +1. Anyone can browse without signing in. Posting, commenting and voting need an account, and each person gets one vote per request.
The form asks for the problem more than the solution: what the request is and who in your organisation it affects, what problem it would solve, when it last got in the way, how often and at what cost, any workaround, and what the ideal result would look like. Bugs go to Zendesk Customer Support instead.
Zendesk says product managers read and log every post. Not every post gets a reply, a request is no promise of a build, no release dates are given, and status changes aim to follow quarterly roadmap planning. A request with no activity for six months may be archived, staying visible to Zendesk's staff.
What do the statuses on Zendesk's feedback board mean?
| Status | What Zendesk says it means | Requests |
|---|---|---|
| Feedback submitted | New, waiting for review | 5,453 |
| Under review | A product manager is evaluating it | 59 |
| Accepted | Being considered for development, with no promise it will be built | 1,252 |
| Early access | Available to test for a limited group | 2 |
| Parked | Valid, and not a current priority | 492 |
| Existing functionality | Can be done with features that exist | 26 |
| Delivered | Live and available | 477 |
Accepted is the second most common status, and requests stay in it a long time. The median Accepted request is nearly four years old, and 781 of them are more than three years old. The median Parked request is older still, at nearly five years.
What happened to the requests when the community moved?
Zendesk's community used to run inside its own help centre, where feedback posts could be marked Planned, Not planned, Completed or Answered. The newest feedback post there is dated 20 March 2026. That help centre still answers its API, its feedback topics hold 8,853 posts, and its address now redirects to the new community.
7,004 of those 8,853 posts can be found on the new board by title and filing date. Of the 1,849 that cannot, 1,773 had no status and 1,649 were filed between 2021 and 2023. A changed title would also hide a post from that match, so the true number carried over may be higher.
The old statuses mostly became the nearest new ones, and posts that never had one were sorted:
| Old status | Posts found on the new board | What they carry now |
|---|---|---|
| None | 5,656 | 4,382 Feedback submitted, 849 Accepted, 220 Parked, 164 Delivered, 41 other |
| Answered | 696 | 456 Feedback submitted, 120 Accepted, 69 Parked, 43 Delivered, 8 other |
| Planned | 189 | 165 Accepted, 17 Delivered, 7 other |
| Not planned | 215 | 173 Parked, 36 Accepted, 6 other |
| Completed | 248 | 225 Delivered, 23 other |
Most posts that had no status are still waiting, and 1,274 of them now carry another status. Thirty six that once said Not planned are now Accepted, and nine marked Completed are back at Feedback submitted.
Do votes get a Zendesk feature request built?
Five votes make the difference between waiting and an answer. Below five, nine in ten requests are still Feedback submitted. From five up, nine in ten carry some other status.
| Votes | Requests | Delivered | Accepted | Parked | Still Feedback submitted |
|---|---|---|---|---|---|
| 0 | 2,222 | 2.3% | 2.9% | 1.1% | 93.5% |
| 1 | 1,532 | 1.5% | 3.1% | 0.7% | 94.6% |
| 2 to 4 | 1,938 | 2.5% | 5.0% | 1.1% | 91.3% |
| 5 to 9 | 1,134 | 15.2% | 47.0% | 21.8% | 10.6% |
| 10 to 49 | 813 | 18.1% | 55.4% | 19.8% | 4.4% |
| 50 to 99 | 88 | 20.5% | 55.7% | 22.7% | 1.1% |
| 100 or more | 34 | 50.0% | 29.4% | 20.6% | 0.0% |
The step falls exactly between four and five: 87.9 percent of requests with four votes are still Feedback submitted, against 14.3 percent of those with five. It holds for requests filed before the move as well, at 92.7 percent below five and 7.8 percent from five up. Zendesk's guidelines name no number. Past five, Accepted is the most common answer until a hundred votes, and past a hundred, half are Delivered.
Most requests never reach five. The median request has two votes, 28.6 percent have none, 19.7 percent have one, and 12.0 percent have ten or more. The most voted request has 487. Replies are common: the median request has two, and 6.4 percent have none.
How many Zendesk feature requests get delivered?
| Filed in | Requests | Delivered | Accepted | Parked | Still Feedback submitted |
|---|---|---|---|---|---|
| 2008 to 2020 | 648 | 22.1% | 29.6% | 19.8% | 27.8% |
| 2021 | 1,258 | 8.6% | 18.0% | 9.9% | 62.7% |
| 2022 | 1,390 | 8.3% | 16.4% | 6.2% | 68.9% |
| 2023 | 1,181 | 4.3% | 16.5% | 6.1% | 72.7% |
| 2024 | 1,308 | 2.0% | 13.4% | 3.3% | 80.9% |
| 2025 | 1,289 | 1.9% | 13.7% | 2.2% | 81.1% |
| 2026 | 687 | 1.2% | 8.7% | 1.5% | 82.1% |
Requests filed before 2021 are few, 648 of them, and the old help centre held 675 from those years. Most drew support: their median request has 13 votes, and 72.1 percent have five or more, against 22.5 percent of requests filed since. From 2021 on, the share delivered falls with each younger year, and the share still waiting rises from 62.7 to 82.1 percent. The median request still at Feedback submitted is nearly three years old, and 2,560 of them are more than three years old.
Which Zendesk products get the most requests built?
| Product area | Requests | Delivered | Accepted | Parked | Still Feedback submitted |
|---|---|---|---|---|---|
| Support | 3,222 | 6.1% | 18.1% | 6.4% | 68.9% |
| Knowledge | 825 | 5.9% | 16.1% | 5.5% | 71.6% |
| Chat and messaging | 756 | 6.2% | 14.2% | 5.2% | 73.3% |
| Analytics | 704 | 8.5% | 16.8% | 10.8% | 60.9% |
| Admin center | 635 | 7.4% | 17.3% | 3.9% | 69.6% |
| Voice | 428 | 9.8% | 27.8% | 9.8% | 51.2% |
| Platform | 414 | 1.2% | 7.2% | 1.4% | 89.1% |
| AI | 242 | 2.9% | 9.9% | 1.2% | 83.1% |
| Sell | 214 | 4.7% | 0.5% | 7.0% | 87.4% |
| Community | 151 | 8.6% | 2.6% | 22.5% | 66.2% |
| Workforce management | 121 | 0.8% | 14.0% | 0.8% | 84.3% |
| Quality assurance | 66 | 1.5% | 10.6% | 1.5% | 81.8% |
Voice has the most decided board, with nearly half its requests given a status. Platform, which covers apps and integrations, has the least, with 89.1 percent still waiting. Sell, Zendesk's sales CRM, has one Accepted request in 214. Twenty two requests sit in two areas and thirteen in none.
Which Zendesk feature requests have the most votes?
| Request | Votes | Filed | Status |
|---|---|---|---|
| Add an end user as CC through a trigger or automation | 487 | 2009 | Parked |
| Post articles to more than one section | 466 | 2012 | Delivered |
| Add or edit tags on closed tickets | 345 | 2008 | Delivered |
| A customisable dashboard | 264 | 2012 | Parked |
| An internal note as a trigger action | 198 | 2016 | Delivered |
| Categories or subviews for views | 194 | 2021 | Delivered |
| Merging organisations | 191 | 2011 | Delivered |
| Following an article to hear of updates | 185 | 2014 | Accepted |
| Copying help centre articles | 182 | 2015 | Delivered |
| Automatic refresh in views | 177 | 2021 | Delivered |
| Editing closed tickets | 177 | 2019 | Delivered |
Two tie at 177. Eight of the eleven are Delivered, one is Accepted, and two are Parked, among them the most voted request on the board, filed in October 2009, with 518 replies.
How busy is the board since the move?
Quieter than before. From April to September 2026 the new board took 453 requests, about 75 a month, against about 110 a month in the old help centre's feedback topics during 2025. Of the 459 filed since April, 29 are Under review, half of all requests carrying that status, and 44 are Accepted.
How does Zendesk compare with other public trackers?
It answers more than the consumer boards read the same day. 29.7 percent of Zendesk's requests carry a status other than Feedback submitted. Discord's feedback board set a status on 42 of the 70,653 posts filed from 2020 on, and Minecraft's feedback site on 70 of the 130,159 filed in the same years. Zendesk has delivered 6.1 percent, close to the 5.4 percent Autodesk has implemented and the 4.7 percent of Spotify, and well short of Atlassian's tracker, where 17.1 percent of suggestions were built. Intercom's Product Wishlist, on the same community software, has released 2.3 percent of its 3,383 ideas.
What does that mean for your own feature request board?
A vote count can work as a triage line, and on Zendesk's board one does: below five votes a request waits, from five up it nearly always gets an answer. Posters cannot see that line unless the board says so. On VoteFirst, Denied and Completed are columns on the board by default, so the answer sits where voters look. Voting is anonymous by default, and when a release includes a request, every voter who was signed in when they voted is emailed that release.
How was this read, and when does it change?
Each page of the Product feedback listing at community.zendesk.com carries the requests it shows as data. On 4 October 2026 every page was read in the board's default order, 7,761 requests in all. Votes, replies and views are as of the read date, and each status is the one the board showed that day. The read cannot tell when a status was set. The old help centre community was read the same day through the Zendesk Help Center API, 18,024 posts, 8,853 of them in feedback topics, and old and new were matched on title and filing date.
The public file holds one row per request with no titles or authors. The next read is due by 1 January 2027.
14 days, a card at signup, then $9 or $39 a month.