> 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/suppliers/suppliers/events/communicate-with-buyers.md).

# Communicate with buyers

With Fairmarkit, you no longer need to keep track of communications with buyers in your inbox. Throughout the sourcing process, you can quickly and conveniently track all event communication within Fairmarkit. While responding to an event, you can add comments, notes, and files to communicate better with buyers.

### Event comments <a href="#eventcomments" id="eventcomments"></a>

While working on an event, comments allow you to communicate about the event and clarify details with buyers. Comments can include attachments. You'll receive a notification when comments are added to your events. For more information, see [Event comments](/suppliers/suppliers/events/communicate-with-buyers/event-comments.md).

<figure><img src="https://2355290214-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGKTC3T55SVuW5ztzEXd7%2Fuploads%2FMGr4WbNhCnR8zvs3WxGA%2Fcomments_thumb_0_0.png?alt=media&amp;token=bda2b0d5-9164-482e-8b95-eb717f0615f6" alt=""><figcaption></figcaption></figure>

### Notes and files <a href="#notesandfiles" id="notesandfiles"></a>

While responding to events, you can add notes and files on the event level and comments and attachments on the line level to communicate your response better.

#### Events

On the event level, you can add additional information in the following ways:

<figure><img src="https://2355290214-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGKTC3T55SVuW5ztzEXd7%2Fuploads%2FxQpfQXrHtzBRh0YAQffY%2Frfq-response-add-info_thumb_0_0.png?alt=media&amp;token=b2590726-8317-4d25-9f76-f565de2a3612" alt=""><figcaption></figcaption></figure>

* **Notes for buyer**: Add additional information and communication (up to 4,000 characters) about your event response for the buyer.
* **Files**: Click Add Files to attach files to share with the buyer. Files can be up to 100MB, and the File name cannot be longer than 255 characters. See [Attachments](/suppliers/suppliers/events/respond-to-an-event/attachments.md) for more information.

#### Lines

On the line level, click the **more**  button and select the *Add additional info* option to enter the following:

<figure><img src="https://2355290214-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGKTC3T55SVuW5ztzEXd7%2Fuploads%2FWoSSYhBs8pHJ2WHIn888%2Fline-comments-attach_thumb_0_0.png?alt=media&amp;token=976a6f67-2203-43ef-ac15-ea573e624933" alt=""><figcaption></figcaption></figure>

* **Comments**: Enter any comments (up to 1,000 characters) about the line item.
* **Attachments**: Click **Add Files** to add attachments specific to the line item. Multiple attachments can be added. Files can be up to 100MB, and the File name cannot be longer than 255 characters Click the remove  button to delete an attachment. See [Attachments](/suppliers/suppliers/events/respond-to-an-event/attachments.md) for more information.

### Clarifications <a href="#clarifications" id="clarifications"></a>

After a buyer has submitted an event, they can send a clarification. Clarifications can include text and attachments and are date and time-stamped. All clarifications display in the **Clarifications regarding this request area.**

<figure><img src="https://2355290214-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGKTC3T55SVuW5ztzEXd7%2Fuploads%2FeyK0xJDpzT8z73XRlArX%2Fclarifications_thumb_0_0.png?alt=media&amp;token=239553be-2b70-4f7b-9c66-5ec99ec33887" alt=""><figcaption></figcaption></figure>


---

# 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/suppliers/suppliers/events/communicate-with-buyers.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.
