Collecting feedback is the part everybody solves. Forms, shared inboxes, a channel in Slack: the reports arrive. What usually fails is everything after that, because the report and the work live in different systems and nobody ever goes back to tell the person who wrote in.
The Planner.day widget is built around closing that gap rather than opening it.
How it works
Add one script tag to your product. Your users get a report button that does not ask them to create an account, sign in, or leave the page they are on.
Submissions do not land on your board. They land in a triage queue, which is the part that matters: an inbox of raw reports on the board is just a different mess. In triage you approve a submission, which creates a task, or merge it into an existing task when three people have reported the same thing.
What closes the loop
When that task is marked done, every linked reporter is emailed automatically. That includes everyone whose duplicate was merged in, which is the case most tools quietly drop.
Each submission carries a short reference in the format PD-XXXXXXXX, and that reference appears
in the subject line of every email about it. Your user can find the thread in their own inbox, and
your support team can quote it back.
What you can do with the same data
Feature requests can be published to a public roadmap with anonymous voting, shown both inside the widget and on a standalone page. It is the same submission data, published, rather than a second tool kept in sync with the first.
Workflow rules can also fire on intake events, so a submission matching a condition can create a task in a specific list, set a priority, or notify a particular person over email, Slack or Google Chat. That is covered under workflow automation.