Open Product updates in the desk.
What's new
Write an update — a new feature, an improvement, a fix or an announcement — in Markdown. Save it as a draft, then publish it when it's ready. Published updates appear:
- on your public updates page at
/updates/<your workspace>, newest first; - in an RSS feed at
/updates/<your workspace>/rss.xml; - under What's new on the chat widget's home screen (the latest three). You can keep any update out of the widget.
Ideas
Turn on Public board open (owners) to give customers a page at /ideas/<your workspace>, where they can vote for ideas and suggest new ones. A vote needs an email address, and each email counts once. Suggestions wait under Waiting for approval until your team approves them, so spam never shows.
Your team can add ideas too. From a conversation, open the command palette (Ctrl K) and choose Log a feature request: start a new idea, or add the customer's vote to an existing one.
Give each idea a status: Under consideration, Planned, In progress, Shipped or Not planned. Two ideas that ask for the same thing can be merged, and each voter is still counted once.
Telling voters it shipped
When you publish an update, tick the ideas it ships. Everyone who voted for them gets one email with a link to the update. Marking an idea Shipped by hand sends the same email. Nobody is emailed twice for the same idea.
A simple routine
- Draft updates as you ship them, and publish in batches.
- Review Waiting for approval ideas weekly.
- When you ship something people asked for, tick the ideas on the update so voters hear about it.
This turns feature requests into a reason for customers to come back.
Related guides
Tell customers about a change inside the chat with Engage, reach your contacts by email through campaigns, and answer the people who suggest ideas from the inbox.