> For the complete documentation index, see [llms.txt](https://help.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filed.com/reference/support/filed-feedback-program.md).

# Filed feedback program

The Filed Feedback Program is the direct channel for reporting AI tax preparation issues to the Filed tax engineering team. It is separate from general support: the Feedback Program is for issues with how Filed's AI prepared a return, not for account questions or technical problems.

## What the feedback program is for

When Filed's AI produces an incorrect or unexpected result on a return, the Feedback Program is how that information reaches the engineers who improve it. Submissions are reviewed by tax specialists, and improvements made as a result automatically apply to future returns across the platform. Recurring issues reported across multiple firms are tracked and prioritized, so each submission has a broader impact than a single return.

## When to submit feedback

Submit feedback whenever you notice an AI preparation issue that required a manual correction, including:

* A form or box populated with an incorrect value
* Data that was missing and should have flowed through from source documents
* An incorrect calculation or tax treatment
* Unexpected AI behavior that did not match the expected outcome for the return
* Any situation where you had to adjust something manually

If you adjusted it, the team wants to know about it.

## How to submit feedback

The feedback form is accessible from the in-app chat widget.

### Required fields

Every feedback submission requires:

* **Client or return identifier** - the name or ID of the client and return
* **Description of the issue** - what happened and what you expected to happen instead
* **Affected form or box** - the specific form, schedule, or field where the issue appeared
* **Screenshots** - at least one screenshot is required for every submission

Providing as much detail as possible in these fields helps the tax engineering team reproduce the behavior and identify whether the root cause is in document reading, data mapping, or logic.

### Attaching screenshots

Screenshots must be attached after submitting the feedback form.

Screenshots should show:

* The incorrect or missing entry
* The affected form or box
* The expected result, where visible

## What happens after submission

Once submitted, every feedback item follows the same process:

1. The issue is routed automatically to the Filed tax engineering team.
2. Tax specialists review the return behavior and the expected outcome.
3. Engineering evaluates the issue and implements an improvement when applicable.
4. The fix applies to future returns automatically.

Recurring issues reported across firms are tracked and prioritized. When a significant improvement is released as a result of feedback, the Filed team communicates the update.


---

# 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://help.filed.com/reference/support/filed-feedback-program.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.
