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

# Email Forwarding

### How it works

To save an email from a customer as a feedback record in ProdCamp you should forward it to a special email address that consists of a product ID that you can find on the "**Products**" page

![](/files/IrGB8UgUjSFeNL0grhkB)

and the "**@forward.prodcamp.com**" part, so it looks like **<ZQYKGRTQN@forward.prodcamp.com>**

All the messages sent to this specific email will be recorded as feedback to the Product with this ID.

{% hint style="info" %}
The only requirement for the forwarded message is: **it must contain** a combination of words "**forwarded**" followed by an email address that it was initially sent from, f.e. "forwarded from <demo@example.com>" or the following block:
{% endhint %}

\---------- Forwarded message --------- \
From: Demo <demo@example.com>\
Date: Thu, 13 Dec 2018 at 17:53\
Subject: Test message\
To: <feedback@bar.com>

Such a block is created automatically when you forward a message from the Gmail interface, so you don't have to worry about it when forwarding messages from inside Gmail. Otherwise, you have to add such a combination manually.


---

# 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.prodcamp.com/feedback-channels/email-forwarding.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.