> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/quality-managers/complaint-application/tracking-and-monitoring-complaints/complaint-reminder.md).

# Complaint Reminder

Keep tasks on track with timely complaint reminders.

Use the **Complaint Reminder** module to monitor pending complaints and send timely notifications to responsible users, ensuring follow-through on assigned tasks.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

***

## Managing Pending Incidents

Follow the steps below to monitor pending complaints and send timely notifications to responsible users.

{% stepper %}
{% step %}

### Filtering Incidents

Use the **filter row** below the column headers to find specific complaints or narrow the results displayed in the grid.

Commonly used filters include:

* **Status:** Filter complaints by their current stage in the workflow.
* **Complaint ID:** Filter complaints by unique identifier.
* **Complaint Name:** Filter complaints by keywords in the title.
* **Date Reported:** Filter complaints by the date and time they were reported.

{% hint style="success" %}

#### Tips for Filtering

Filtering options vary depending on the column’s data type.

* **Text Search:** Type directly in the filter field to quickly find matching values.
* **Dropdown:** Select a value from the dropdown (e.g., true or false).
* **Advanced Filtering:** Use the **magnifying glass** ( <i class="fa-magnifying-glass">:magnifying-glass:</i> ) icon to apply conditions (e.g., equals, contains, or range-based filters).&#x20;
* **Date/Time Filtering:** Use the **calendar** ( <i class="fa-calendar">:calendar:</i> ) icon to select specific values.

If the filter field is not editable or no controls are available, the column cannot be filtered.
{% endhint %}

***

{% endstep %}

{% step %}

### Sending Reminders

Follow these steps to notify users about complaints requiring action:

* **Select Reports**
  * In the grid, check the **Select** box next to each complaint you want to send a reminder for.
  * Click **Save Changes** or click outside the grid to save your selections.
    * To cancel, click **Discard Changes**.
* **Send Reminders**
  * Click **Send Email Reminder** to notify the responsible users.
    * A confirmation message will appear above the grid once reminders have been sent.
    * Each reminder is sent to the assigned reviewer of the selected complaint and includes:
      * Key details about the complaint
      * A reminder of the due date (whether upcoming or overdue)

{% hint style="warning" %}
If a complaint no longer has an associated task, the system will block the reminder and display an informational message to prevent outdated or invalid notifications.
{% endhint %}

***

{% endstep %}
{% endstepper %}

***

## See Also

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>How to Export Grid Data</strong></td><td>Export grid contents to an Excel file.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2F8EURtbR8olEYsY7knlFB%2FIMS-V16-NAV-Library-Icons-106.png?alt=media&amp;token=7664c54c-4826-48e4-8ca0-d042582c2f2d">IMS-V16-NAV-Library-Icons-106.png</a></td><td><a href="/interfacing-help-files/end-users/exploring-apps/working-with-forms/working-with-grids.md#exporting-data-to-excel">Working with Grids</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://interfacing.gitbook.io/interfacing-help-files/quality-managers/complaint-application/tracking-and-monitoring-complaints/complaint-reminder.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.