Zendesk's Own Public Roadmap Gap
No. Zendesk does not publish a public roadmap showing what it's building next or when. A customer asked for exactly that on Zendesk's own community forum back in 2020, a Zendesk employee replied by pointing to existing release announcements rather than committing to a dated roadmap, and the thread was still active with people asking "is this live yet" in 2024. Six years on, there's still no roadmap page.
The second half of the question matters more if you run Zendesk yourself. Is there a native way inside Zendesk to build that same view for your own product, so a customer who requested something can see "here's what shipped because you asked"? Also no. Zendesk's feedback tooling can collect a request and change its status, but nothing in the product wires that status to the engineering work that actually resolves it. The gap Zendesk's customers complain about is the same gap you inherit if you try to run your own roadmap-style loop on top of it.
“we need SSO before rollout”
“any update on single sign-on?”
“SSO came up twice on this call”
Linear issue, quotes attached
insight report in NotionThe community has been asking since 2020
The request itself is plain. Give admins a public list of planned features, roughly when they're coming, and some sense of priority, so they can plan around Zendesk's own roadmap instead of guessing. The thread has 41 upvotes and eleven replies, which is a modest number for a community with thousands of open ideas, but the replies make the case on their own: people naming features that were marked "planned" for years without shipping, and a 2024 comment asking whether anything had changed since the original 2020 post.
Zendesk's response wasn't a refusal, it was a redirect: check the beta program pages and the periodic "what's new" write-ups instead of expecting a dated roadmap. Those surfaces tell you what already shipped or what's in limited beta right now. Neither one tells you what's coming in six months, which is the actual thing a roadmap is supposed to answer.
Zendesk's own feedback board shows the same shape
Zendesk runs a public product-feedback forum where customers submit ideas and vote, and it's a legitimate implementation of the pattern: thousands of live requests, filterable by product area, sorted by votes or recency. Each idea is marked Feedback submitted, Under review, Accepted, Parked, Existing functionality, Early access, or Delivered, depending on where Zendesk's own team says it stands.
That status field is the closest thing Zendesk offers to "here's what shipped because you asked." Here's what it actually does, and what it doesn't. It tells you Zendesk's stance on an idea. It does not tell you when Delivered will happen, because there's no date attached to any status, and there's no roadmap tying a batch of Accepted ideas to a release. An idea can sit at Accepted for years with no visible change, which is exactly the complaint running through the roadmap thread above.
What Trevor built at Cubby, and where it stopped closing the loop
Cubby sells yard-management software to independent self-storage operators, gate codes, unit locks, billing. Trevor Naidu has spent three years building out its support function, currently a team of sixty. Eight months ago, three facility owners asked, separately, for a way to auto-text a renter when their unit was approaching its lien date instead of relying on a paper notice mailed to whatever address was on file. Trevor had turned on the product-feedback topic in Cubby's own Zendesk Gather instance the year before, so he posted the idea there and let it collect votes from the customers who'd asked.
Engineering picked it up six weeks later. Trevor set the Gather post's status to Planned, one of only four statuses Zendesk's own documentation defines for a Gather post (Planned, Not planned, Completed, and Answered). The feature shipped in a release two months after that. Engineering closed the Linear issue, deployed the change, and moved to the next thing on the board. Nobody told Gather. The post sat marked Planned for another five weeks until one of the original three facility owners replied to ask about it directly.
Facility owner, in the Gather thread: "You marked this Planned back in March. Is it live now? I don't want to keep telling renters we're 'working on it' if it already shipped."
Trevor had to go check Linear himself, confirm the issue was closed, and flip the Gather status to Completed by hand, the status Zendesk's docs use for a shipped idea. Nothing in Gather watches Linear or GitHub for him. The status field is exactly as current as the last person who remembered to edit it, and on a board with dozens of live ideas, remembering to edit it is the part that slips.
Where Gather's status field stops helping
Be specific about the limit, because it isn't a bug, it's the shape of the tool:
- Status is a manual field, not a synced one. Nothing connects a Gather idea's status to the Linear issue or GitHub PR that resolves it, so "Planned" and "Completed" reflect whoever last remembered to click, not the actual ship date.
- There's no requester list to notify. Even a status flip only updates the public thread. It doesn't message the specific people who asked across other channels, a support ticket, a sales call, a Slack message, because Gather only knows about the people who happened to post in Gather itself.
- Zendesk doesn't solve this for its own roadmap either. The community thread above is the same complaint from the other direction: a status or beta label with no date and no tracker link, six years running.
Below a couple dozen live ideas, a person checking the tracker weekly and updating statuses by hand is a real, workable system. Past that, the manual reconciliation grows with volume and starts slipping exactly the way it did for Trevor.
Where Modem closes part of this gap
Start with what this doesn't fix. Trevor's problem was a Gather post going stale, and Modem doesn't read Gather or any other public community board directly, so a request that stays a community post sits outside what Modem can close automatically. If that's the exact shape of your problem, public ideas specifically going stale, Modem isn't the fix for that half.
What it does fix is the same failure mode in the place it shows up most for a support team, not the public board, but the support tickets sitting underneath it. Modem's Zendesk integration reads tickets and conversations, dedupes mentions of the same request into one counted topic, and keeps every person who asked attached to it regardless of which channel they used, a ticket, a Slack thread, a sales call. That topic links to the Linear issue or GitHub PR that resolves it, so when engineering closes the issue, Modem knows immediately, without a status field someone has to remember to flip. Every requester on the topic gets told the feature shipped in one pass. If the three facility owners had emailed support instead of posting in Gather, this is the version of Trevor's story that doesn't end with a customer asking "is this live yet" five weeks late.
Modem is the product we build, so read that fit claim knowing where our interest sits. The fuller comparison of what a public feedback board can and can't do on its own is in Zendesk's native ideas board as a feedback backlog, and the general mechanics of turning support tickets into tracked roadmap items are covered in how to turn support tickets into roadmap items.
What to change in Gather this week
If you're running a Gather-style board today, add one recurring step. Whenever a Linear issue or GitHub PR tied to a Planned idea closes, that's the trigger to flip the status and reply to the thread the same day, not whenever someone happens to ask. It won't scale past a few dozen live ideas, but it closes the exact gap that left Trevor's customer wondering whether "Planned" still meant anything five weeks after it shipped.
