> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usertick.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Usertick runs surveys on websites, by link, by QR code and by email, and collects every response in one inbox with reports, dashboards and workflows. The REST API lives at https://app.usertick.com/api/public/v1 and uses Bearer API keys or OAuth access tokens; the JavaScript SDK is the @usertick/snippet package on npm.

# Follow up on feedback in the inbox

> Find the responses that need action, give each one an owner, bring in a teammate with an @mention and move it from Open to Planned and Resolved.

You can turn responses into follow-ups that someone owns. When you finish this guide, each response that needs action has an owner, a note with the plan and a status that shows the whole team where it stands.

## Before you start

* Any plan works.
* Reading the inbox requires **View surveys and results**, and assigning, writing notes and changing statuses requires **Manage responses**.
* You can assign only teammates whose role opens the survey.

## Find what needs a follow-up

1. Open **Inbox** and select the **Open** folder, since every response starts as **Open**.
2. Narrow the list with a type folder, such as **Complaints**, which combines with **Open**, or with **Filters**, such as **Score group** or **Urgency**.

![The Open folder of the inbox with the status and Type folders on the left, and the Filters menu with Date and Status set and the Add filter list open](https://mintcdn.com/usertick/b7hHAD5bKMN_XhRp/images/inbox.png?fit=max\&auto=format\&n=b7hHAD5bKMN_XhRp\&q=85\&s=feb3e7b2987df99a6caf7bf63effc738)

Inbox with the Filters menu open

By default, the list shows every response, including the ones with only a score. To keep to written answers, select **Written answers only** under **Has**.

## Give it an owner

1. Select a response to open it in the reading pane.
2. Select **Assign** and choose one or more teammates.

Each teammate you assign receives a notification in the bell and, with the default settings, by email. Assigning a response to yourself notifies nobody.

## Leave a note for the team

In **Leave a note for the team**, write what happens next and type `@` to mention a teammate. The person you mention receives a notification in the bell and, with the default settings, by email. Notes stay under the response, so anyone who opens it later sees the history.

## Move it through the statuses

* Once a fix or reply is planned, set **Planned**, and while someone works on it, set **In progress**. You can change the status with **Status** in the **Details** panel or by typing `/plan` or `/progress` in the note box.
* When the follow-up is done, select **Resolve** above the response, or select **Submit and resolve** to post a note and resolve in one step.
* If a response needs nothing, select **Archive**.

To reply to the person, look under **Respondent** in the **Details** panel, which shows their email when your site identified them. **View contact** opens their contact, and if they typed an email that isn't a contact yet, **Add to contacts** adds it.

## Keep your own list

Under **Views**, **Assigned to me** lists the responses you own, and **Unassigned** lists the ones nobody has picked up. To keep another set of filters, select **New view**, name it and select **Save view**. Every view you save is shared with the whole organization.

## Check that it works

When the owner opens **Views → Assigned to me**, the response appears there. After you resolve it, the response leaves **Open** and appears in the **Resolved** folder.

## Related

* [Inbox](https://docs.usertick.com/results/inbox.md)
* [Assign and discuss](https://docs.usertick.com/results/inbox.md#assign-and-discuss)
* [Change a status](https://docs.usertick.com/results/inbox.md#change-a-status)
* [Notifications](https://docs.usertick.com/workspace/notifications.md)
* [Members and roles](https://docs.usertick.com/workspace/members-and-roles.md#survey-access)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.