> ## Documentation Index
> Fetch the complete documentation index at: https://docs.recepai.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Event Inquiries

> People asking about a dinner, a wedding, a group — guests you do not have yet.

**Event Inquiries** holds the enquiries your AI staff capture from people who are **not staying with you**. Somebody asking about a table for twelve, a wedding, a company dinner.

They have no room and no stay. That is what makes them different from a [guest request](/front-desk/requests/active): this is a sale you have not made yet.

***

## What is on the screen

A table of enquiries, with a count of how many you have in the header:

| Column       |                                                |
| ------------ | ---------------------------------------------- |
| **Name**     | Who is asking                                  |
| **Contact**  | Phone and email                                |
| **Inquiry**  | What they are asking about, and its type       |
| **Source**   | Where it came from, including *Added by staff* |
| **Status**   | *New*, *Contacted*, *Confirmed*, *Closed*      |
| **Received** | When it came in                                |

Filters cover the type, the channel, the date and the status.

Opening one gives you the rest: **the date and time they want**, the **party size**, who it is **assigned to**, **the guest's own note**, and your team's **internal notes** — which the person asking never sees.

***

## What you do here

<Steps>
  <Step title="Work New first">
    An enquiry nobody has answered is a booking somebody else is taking.
  </Step>

  <Step title="Move the status as you go">
    **Update status** offers the steps that make sense from where it is now — Contacted once you have replied, Confirmed when it is agreed, Closed when it is not going ahead.
  </Step>

  <Step title="Write down what was agreed">
    An internal note is where "they want the terrace, confirmed by phone, deposit on arrival" lives. The status alone will not remind anybody of that in three weeks.
  </Step>

  <Step title="Add one yourself">
    **Add Inquiry** records an enquiry that arrived some other way — at the desk, over the phone — so it is worked like the rest instead of living on paper.
  </Step>

  <Step title="Archive it when it is finished">
    Confirmed and delivered, or closed. **Archive** clears it from this list.
  </Step>
</Steps>

<Warning>
  **Nobody is chased automatically.** This is a list, not an automation. An enquiry left on *New* stays on *New* — the follow-up is yours.
</Warning>

***

## What happens next

Changing a status or adding a note is recorded on the enquiry. Archived ones move to [Archived Inquiries](/front-desk/event-inquiries/archived).

**Nothing here books a room.** An enquiry that turns into a stay is booked the way any other booking is made; this list is where the conversation that led to it is kept.