> For the complete documentation index, see [llms.txt](https://docs.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmarkit.com/buyers/events/communicate-with-suppliers/supplier-clarifications.md).
# Supplier Clarifications
Once you open an event, you can send a clarification to all of the suppliers on an event. The clarification can be a message or attachment with clarifying details about the opened events. This is an easy way to contact all suppliers invited to an event.
### Send a supplier clarification
{% stepper %}
{% step %}
In the Supplier clarifications area, click **Add new**. The Supplier clarifications window displays.
{% endstep %}
{% step %}
Enter your message. If needed, click the **Attach** :paperclip: button to attach a file.
{% endstep %}
{% step %}
Click **Add clarification**. All suppliers will receive an update. Clarification display on the suppliers' event pages.
{% endstep %}
{% endstepper %}
### View supplier clarification history
From **Supplier Clarifications** area , you can view a history of past clarifications you've sent for the event. Each clarification is date and time-stamped with the user.
---
# 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.fairmarkit.com/buyers/events/communicate-with-suppliers/supplier-clarifications.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.
