Skip to main content
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: 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: 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

1

Work New first

An enquiry nobody has answered is a booking somebody else is taking.
2

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.
3

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.
4

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.
5

Archive it when it is finished

Confirmed and delivered, or closed. Archive clears it from this list.
Nobody is chased automatically. This is a list, not an automation. An enquiry left on New stays on New — the follow-up is yours.

​
What happens next

Changing a status or adding a note is recorded on the enquiry. Archived ones move to Archived Inquiries. 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.