> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/support/how-to-reach-us/managed-phishing.md).

# Managed Phishing

If you have the Managed Phishing service, you can alert us of suspected phishing attempts by clicking the official **Expel Phishing** button or by using custom email forwarding. 

{% hint style="warning" %}
Supported providers for the button include Microsoft 365 or Google Workspace; limited support is available for Microsoft Exchange Server.
{% endhint %}

## Use the Phishing Button

To set up the button, go to [Organization Settings > My Organizations](https://workbench.expel.io/settings/organizations/), scroll down to the **Phishing** tab, and begin the setup process. The button will then appear in your [email program](#user-content-fn-1)[^1] and you can use it to report potential phishing attempts.

{% hint style="info" %}
For full setup instructions, see [Phishing Submission Button Setup](/more-features/expel-managed-phishing/setup-guides/phishing-submission-button-setup.md).
{% endhint %}

## Use Custom Email Forwarding

Managed Phishing customers can also send suspected emails to us as an EML attachment by using a custom email forwarding destination.

To view your custom email forwarding destination, go to [Organization Settings > My Organizations](https://workbench.expel.io/settings/organizations/), scroll down to the **Phishing** tab, and look for the **Destination Address**.

[^1]: Only Microsoft 365 and Google Workspace are fully supported.


---

# 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://docs.expel.io/support/how-to-reach-us/managed-phishing.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.