> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/human-security/report-button/announcement.md).
# Announcing to your team
Once the Report button is deployed, tell your employees what to expect. The simpler the message, the better the adoption.
## Send an announcement email
Send a short email to everyone on the day of the deployment.
Email template
**Subject:**
A new way to report suspicious emails
**Body:**
Hi everyone,
Starting today, you will see a new **Report to Stoïk** button in your \[Outlook / Gmail] mailbox. This button was added by the IT team as part of our work with **Stoïk**, our cybersecurity partner.
If you receive an email that looks suspicious (an unexpected sender, an urgent request, a strange link, an unusual attachment), the safest thing to do is to click **Report to Stoïk** instead of clicking, replying, or deleting. Stoïk will analyze the email and let you know immediately whether it was a real threat or a training simulation.
Reporting takes one second and is the single most effective way you can help protect our company from cyberattacks. When in doubt, always report.
For more details on how the button works, see [this short guide](https://docs.stoik.io/human-security/report-button/employee-guide).
If you have any questions or do not see the button in your mailbox, let me know.
Thanks,
\[Your name]
## Follow up after two weeks
Adoption drops after a one-shot announcement. Two weeks after the deployment, send a short follow-up with a few numbers, for example how many suspicious emails your team has flagged. Find them in `Human Risk` > `Report`.
---
# 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.stoik.io/human-security/report-button/announcement.md?ask=&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.