> 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/glossary/glossary/email/suppliers-emails/rfq-emails/event-invitation-email-rfq.md).

# Event invitation email (RFQ)

When a buyer invites you to a request for quote event, you'll receive an email with an event and line item summary and a link to respond.

{% hint style="info" %}
**Note:** You can change your email preferences from [Notification settings (suppliers).](/buyers/getting-started-as-a-buyer/notifications-buyers/notification-settings-buyers.md)
{% endhint %}

<figure><img src="https://1813608463-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXSi8dxrnMaQPYuaoiJWp%2Fuploads%2FZLbCMEfBN2o0r6pQgQgT%2Fimage.png?alt=media&amp;token=578bacb6-e00f-4da3-b2f2-cef46d0ac8ea" alt="" width="375"><figcaption></figcaption></figure>

### Email subject <a href="#emailsubject" id="emailsubject"></a>

The email subject will be:

* (Buyer company name) - Request for Quote #------\
  example: *AM Productions - Request for Quote #820214*

### Email content <a href="#emailcontent" id="emailcontent"></a>

The email includes:

* Event title
* Summary of line items\
  (Description, Manufacturer, Manufacturer part #, Internal part #, Quantity)
* Any notes from the buyer
* Link to respond
* Link to send a message to the buyer
* Link to decline the event
* Event details\
  (close date and time, event ID, shipping address, preferred delivery date)


---

# 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/glossary/glossary/email/suppliers-emails/rfq-emails/event-invitation-email-rfq.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.