Mark a request as shipped and Chattering tells the people who asked for it — in the conversation where they asked. No mailing list, no export.
Anyone who left only an email address gets an email instead.
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 at /portal, 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.
- Click the request to open it, then change the status to Shipped.
- A panel slides open. Write a short note — one or two sentences — describing what you shipped. This note goes into each notification and becomes the seed for the changelog draft.
- Click Notify customers. Chattering sends the message immediately.
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 — whether they came through the chat widget, the feedback portal, or sent in an email — gets a reply in the same place they originally asked. Someone who upvoted the request in your public portal gets a portal notification. Someone who mentioned the feature in a support conversation gets a message in that exact thread.
If Chattering has only an email address for them (because they never opened a chat), they get a plain-text email with your note and a link back to the portal to see the full changelog entry.
Notifications go out immediately when you click Notify customers. There is no queue, no scheduled batch, and no delay.
The changelog entry
After you notify customers, Chattering offers to draft a changelog entry. 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, add screenshots if you like, and publish when it is ready.
Once published:
- It appears on your public portal at
/portal - 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, set it to Shipped, write "CSV export is live — find it under Settings → Export", and click Notify customers. Every one of those 34 people gets that message delivered wherever they originally asked: some in old chat threads, some via a portal notification, a handful by 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? A short note is strongly recommended but not required. Without one, Chattering sends a generic shipped message. A specific note — even one sentence — gets a noticeably better response.
What if a customer asked in multiple conversations? Chattering deduplicates by contact. Each person receives one notification regardless of how many times they raised the request.
Can I ship a request without notifying anyone? Yes — change the status to Shipped and close the panel without clicking Notify customers. The status updates on the board and in the portal but no messages go out. Useful when you want to log completion without interrupting people.
Can I customize the message per customer? Not at the moment. The same note goes to everyone on the request. For a more personal touch, follow up individually from the conversation view after the bulk notification goes out.