You have just dragged a feature request into your "Shipped" column. Did the people who voted for it get an email? This article answers that, and shows you what to send instead.
Moving a ticket does not send anything
Yaplet does not email voters by itself. Moving a request between columns — public or private, "Planned" to "Shipped" or anywhere else — changes what your public roadmap displays and nothing more. No message goes out, to anyone, automatically.
This matters because the widget asks a visitor for their email address before it will accept their first vote. That address is what stops one person voting ten times; it is not a subscription — and the vote box says exactly that. Do not promise your users an automatic update — promise them a roadmap they can check, and send the update yourself.
Reply to the person who asked: the decision email
Every ticket can be replied to by hand, which is the right tool when one customer has been waiting on one thing:
- Open the request from Communications → Tickets → (your feature board).
- In the Actions list, click Send decision.
- Check the Visitor email — Yaplet fills in the address of whoever submitted the ticket, and you can replace it.
- Optionally set a Sender name, and choose the Source email it goes out from.
- Write your message in Decision content and send.
The email opens with the reporter's original answers and puts your message underneath them, under the heading Our Decision, so they can see which request you are answering. Yaplet records what was sent on the ticket, and shows it as Previous decision next time you open the dialog — so you can see whether someone already replied, and resend if you need to.
Limits worth knowing before you plan around it
- It goes to one address. Yaplet fills in the reporter's own address but never the list of people who voted, so a request with forty votes takes forty sends.
- The sender must be verified. The dropdown offers your organisation's verified sending addresses; if you have none, it falls back to
[email protected]. You cannot type an arbitrary From address. - Thirty per hour, per organisation. Past that, sends are refused until the hour rolls on.
- You need the Tickets permission to send one at all.
Telling everyone at once
For a release that a lot of people were waiting on, a one-by-one reply is the wrong shape. Better options, all of which reach more people for less work:
- Keep a public "Shipped" or "Released" column. It is the cheapest signal there is: anyone who checks the roadmap sees their request has moved, and it costs you nothing per person.
- Announce it in your newsletter and link the roadmap page, so voters can see the whole set of changes rather than one line.
- Post it in the widget's news feed, which reaches people while they are actually using the product.
For how the voting itself works and what the email address is used for, see Let visitors upvote feature requests from the widget.