> For the complete documentation index, see [llms.txt](https://doc.keepnetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.keepnetlabs.com/next-generation-product/getting-started/6.-setup-phishing-reporter.md).

# 4. Setup Phishing Reporter

## What is the Phishing Reporter?

Phishing Reporter is an add-in that allows users to easily report a suspicious email to cyber security teams. Quick, comprehensive analysis and response can be provided when used in conjunction with the Incident Responder.

### **There are 2 options:**

* **Integrate the Native Microsoft Reporter Button with Keepnet**
  * Use your existing reporter button whilst capturing who is showing secure reporting behaviour across your phishing simulations

{% content-ref url="/pages/IpXPbgXMopK5ag8sRm70" %}
[Integrate Native Microsoft Phishing Report Button with Keepnet](/next-generation-product/getting-started/6.-setup-phishing-reporter/integrate-native-microsoft-phishing-report-button-with-keepnet.md)
{% endcontent-ref %}

* **Use our highly customisable Keepnet Reporter Button**
  * Customise the language employees see when reporting and set up positive reinforcement messages for employees whilst still being able to redirect reported emails to your SOC team

{% content-ref url="/pages/HQKqzF89vfeF4H4NKBTf" %}
[Deploy Keepnet's Customisable Phishing Report Button](/next-generation-product/getting-started/6.-setup-phishing-reporter/deploy-keepnets-customisable-phishing-report-button.md)
{% endcontent-ref %}

{% hint style="success" %}
We have a [Phishing Reporter Announcement email template](/next-generation-product/platform/phishing-reporter/phishing-reporter-deployment/phishing-reporter-announcement-email-template.md) you can use to share the key benefits and expectations of your employees using this tool.
{% 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 dynamically by asking a question.

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

```
GET https://doc.keepnetlabs.com/next-generation-product/getting-started/6.-setup-phishing-reporter.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 `build a script that syncs our docs to a CMS` 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.