Skip to documentation

Triage feedback and follow up

Move feedback through review, add team notes, link issue trackers and email eligible respondents.

Updated Read as Markdown

A feedback inbox becomes useful when the team can distinguish new reports from reviewed work. Use status, labels and notes to record that progress, then follow up when there is an update for the respondent.

Review and organize an event

Open a feedback item from an inbox or feedback view. Review its score, comment and available context before deciding what action it needs. Status choices are New, Reviewing, Planned, Resolved and Archived.

A practical sequence is to move an item to Reviewing while investigating, Planned when work is agreed, and Resolved when the outcome is ready. Archived keeps an item out of active work without describing it as a completed fix. Choose the status that matches what your team has actually done.

Use labels to group related feedback and notes to record investigation details. Where mentions are available in the note editor, mention the relevant teammate instead of placing internal discussion in a respondent-facing message. Your role and permissions determine which changes you can make.

The feedback detail view can save an external tracker reference and URL. This links the feedback to work you already track elsewhere. Entering a URL does not itself create an external issue or synchronize its status.

For a configured workflow that creates GitHub issues from feedback, see the GitHub integration guide. Review that automation's trigger and destination before enabling it.

Send a follow-up email

The Close the Loop action lets an authorized signed-in teammate write a follow-up and choose the respondent email. Review the address and message before sending; a successful send records a note on the feedback item.

The recipient must already appear in the organization's Feedback Page response records. An email address in a widget comment or custom context alone is not enough. This action is intended for following up with recorded respondents, not sending arbitrary outbound email.

A useful message identifies the feedback, explains the change or next step, and provides a relevant link. Updating a feedback status does not automatically send that message; send it through the follow-up action when ready.

Troubleshoot access and delivery

If editing or follow-up controls are unavailable, check the active organization, brand access and feedback permissions. Follow-up requires a user session; an organization API key is not a substitute for the signed-in sender.

If a recipient is rejected, confirm their address is in the organization's form response records and matches the address you entered. For programmatic listing, labels and status changes, use the Feedback API reference.