Mark a request as shipped and Chattering tells the people who asked for it in the conversation where they asked: a note in their chat, or a reply in their email thread if they asked by email. No mailing list, no export.
Anyone who left only an email address gets an email instead.
On any plan except Free, you can also have a changelog entry drafted from the shipped work, written from the customers' own words and citing the requests it closes. Your changelog is public on your portal page at /portal/s/<your-slug> once you claim a public roadmap address, appears in the widget's News tab, and has a real RSS feed.
How to mark a request as shipped
- Open Feedback in the left rail and find the request you want to close.
- Change its status to Shipped with the status menu on the request.
- Chattering notifies everyone waiting on it straight away, and a "Loop closed" note at the top of the page says how many were told in their chat and how many were emailed.
That's it. You don't need to export a list, paste emails, or touch any other tool.
What customers receive
Each person who asked in a chat gets a reply in the same conversation where they asked. Someone who asked by email gets the same note as a reply in their own email thread, sent from your agent's name. A vote on its own doesn't sign anyone up: someone who tapped Email me when it ships on your public portal, or left an email address when they submitted the request, gets an email.
If Chattering has only an email address for them (because they never opened a chat), they get an email saying the thing they asked for is now live, with a link to the request's page on your portal.
Notifications go out as soon as you choose Shipped. There is no queue, no scheduled batch, and no delay.
The changelog entry
On any plan except Free, click Draft from shipped in Feedback and Chattering drafts a changelog entry from the requests you've marked Shipped. It pulls the language straight from the customer conversations that drove the request — what people said they needed and how they described the problem. You edit the draft and publish when it is ready.
Once published:
- It appears on your public portal at
/portal/s/<your-slug> - It shows in the News tab inside the widget for visitors on your site
- It goes into your changelog RSS feed, so users who follow it with a reader pick it up automatically
The draft often needs only light editing. The customers wrote the brief; Chattering turns it into a changelog entry.
An example
Your team ships a CSV export feature after 34 customers requested it over the past quarter. You open the request and set it to Shipped. The people who asked in a chat get a message in their old chat threads, the ones who asked by email get a reply in their email thread, and the ones who left an email address on your portal get an email. You then publish the changelog entry — Chattering drafted it from the customers' own words — and any visitor browsing the widget the next day sees it in News.
The feature ships once. The communication happens once. Nobody asks "did you send the update?" because they already have it.
Common questions
Do I have to write a notification message? No, and there is nowhere to write one: everyone gets the same short message saying the request they asked for is now live.
What if a customer asked in multiple conversations? Each conversation gets the message once, so someone who raised the request in two separate conversations is told in both.
Can I ship a request without notifying anyone? No. Choosing Shipped notifies everyone waiting on that request straight away.
Can I customize the message per customer? Not at the moment. The same message goes to everyone on the request. For a more personal touch, follow up individually from the conversation view after the bulk notification goes out.