You said, we did: publishing actions after a poll
Record up to three commitments after reading results, publish them to the people who answered, post them to Slack, and carry them onto the next wave of a pulse series.
On this page
People answer a second pulse when the first one visibly did something. The Actions card is the smallest version of that: three commitments, a status each, and a button that puts them in front of the people who answered.
An anonymous poll that only collects is half a loop. Respondents cannot be thanked by name and cannot be told individually what changed, so the reply has to be public and collective. InviziPoll gives every poll an Actions card for exactly that.
Recording actions
Open a published poll and find the Actions card on the results tab. You can add up to three actions, each with:
| Field | Limit |
|---|---|
| Title | 120 characters |
| Detail (optional) | 500 characters |
| Status | Planned, In progress, or Done |
Save as often as you like. Nothing is visible to anyone else until you publish.
The card is available to the poll's owner on any published poll, whether or not results have unlocked yet. There is no response threshold on actions because they contain no respondent data, and "we heard you, results are still coming" is a legitimate thing to say early.
Publishing to respondents
Publish to respondents makes the actions public. The card then tells you exactly where they will appear, which depends on the poll:
- The poll's own link, once it closes. Someone who opens the closed poll sees the actions instead of a dead end.
- The public results page, if you enabled public results for the poll.
- The next wave's response page, if the poll is a wave in a recurring pulse series. Respondents see a short Last wave, you said, we did strip above the questions.
Each of those surfaces shows the heading You said, we did, your titles and details, and the status of each. They also carry one sentence that matters: Nothing anyone wrote is included. Actions are your words about what the organisation will do; no verbatim, count, or chart travels with them.
Editing after publish keeps the actions published, so you can move an item from Planned to Done without republishing. Clearing every action takes the block down everywhere.
Posting an update to Slack
If the poll was announced in a Slack channel, or it belongs to a series with an announcement channel, the card also offers Post update to Slack. It posts a message with the poll title and the published actions to that channel, and includes the public results link when public results are on.
The button appears only when a channel exists and only after the actions are published, so a draft can never reach a channel by accident. See Slack integration for connecting a workspace.
Actions across a series
On a series' trend page, each wave shows the actions that were published for it, so a colleague reading the trend can see what was promised alongside what moved. Actions from the previous wave are what the next wave's respondents see when they open the new poll.
What actions are, and are not
Actions are plaintext, like a poll title. They are meant to be broadcast, so encrypting them would only break the Slack post and the next-wave strip. That is the opposite of how responses are handled, and it is deliberate: responses are what people said, actions are what you chose to say back.
This is not a project tracker. There are no owners, due dates, or reminders. Three commitments and a status is the part respondents actually see and the part that moves the next response rate.
If you drafted a summary with on-device AI summaries, Add to action plan prefills a row for you to edit. It does not save or publish anything on its own.