> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/private-panels/screeners/survey-email-not-found-err0005.md).

# Survey Email Not Found (ERR0005)

As a respondent taking a survey, if you see the error **Respondent email was not found when saving (ERR0005)**, here are things that could be causing this.

### Survey is not collecting email

**Scenario**

If your [survey status](/private-panels/screeners/survey-status.md) is set to **Anyone**, you [must collect an email](/private-panels/screeners/public-private-panels-screener-links.md). If you do not collect an email, there is no way for Private Panels to identify the respondent in your Panel.

**Solution**

Ensure your survey has a question that collects the respondent email ([how-to guide](/private-panels/screeners/public-private-panels-screener-links.md)), and uses **two-way sync** to link the value to the Email panel property.

### Disqualify logic before collecting email

**Scenario**

If you have logic set up in your survey, and you **disqualify** a respondent **before** collecting their email, you will get an error.

**Solution**

Move the question collecting the email before any disqualifying questions.

{% hint style="info" %}
**Note:** Private Panels was previously managed outside of Dscout, so you may see a different logo and URL in some places. If you have any questions, contact <support@dscout.com>.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.dscout.com/private-panels/screeners/survey-email-not-found-err0005.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.