Your customers
Announcements
CatchLoop sends your customers one kind of news: the request they asked for has shipped. It goes out when you publish a changelog entry, and at no other moment.
Publishing an entry
- Write a changelog entry in the dashboard: a title and what changed.
- Link the requests it delivers.
- Before you publish, the editor shows how many people will be emailed. That number is the list the send uses, so what you read is what goes out.
- Publish. The linked requests move to Shipped, the entry appears on your portal's changelog, and the emails leave.
A request that reached Shipped by hand, with no published entry linking it, shows as "Shipped, not announced" in the dashboard: nobody has been told yet.
Who is emailed
The followers of the linked requests. A customer follows a request when they posted it, voted for it or commented on it; there is no separate subscribe button. From that list, CatchLoop leaves out anyone who:
- muted that request from their My requests page;
- turned off all emails from your portal, or unsubscribed from a previous announcement.
Each person gets one email per entry, however many of its requests they follow, and publishing never sends the same entry to anyone twice. Every email carries a link to My requests and a one-click unsubscribe link.
Settings > Emails has a switch, "Email your users automatically". Off, publishing still moves the requests to Shipped and updates the portal, and nobody is emailed. Leaving it on is the point of the product.
What never sends an email
- Changing a status, in the dashboard or through the MCP server, including to Not planned.
- A new request, a vote or a comment.
- Importing a list.
The only other email a customer receives from your portal is the sign-in link they asked for.