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

# Events and guests

> Run an offsite or a conference as one event with one approval, see who arrives when, ask for a room block, and book for guests who don't have a TripMazer account.

## Events

An event is an offsite or a conference run through the desk as one thing: a place, dates, a budget and the people going. It's on **Events**, for travel admins to set up and for everyone they invite.

### Set one up

1. A travel admin chooses **New event** and gives it a name, the city and venue, the first and last day, and, if you like, a **Budget for everyone's travel** and an **Up to, a person** cap. Add a cost centre or project, and choose **Who approves it**.
2. **Invite** colleagues and guests.
3. Choose **Send for approval**. With no other approver, **Approve and tell people** approves it at once.

Invited colleagues hear about it by email and in their chats once it's sent for approval, and again when it's approved. On WhatsApp, Telegram and in Slack the invitation has **Coming** and **Not coming** buttons, and they can also reply "coming" or "not coming".

### In chat

Anyone invited can handle the event with Mazer in any chat: the app, WhatsApp, Telegram or a Slack message to Mazer AI.

* Ask what you're invited to: *"What events am I invited to?"*
* Say whether you're coming: *"Count me in for the Goa offsite"* or *"I can't make it"*.
* Ask for your travel: *"Book my flights for the offsite, I'm leaving from Bengaluru."* Mazer finds options for the event's city and dates, and says which ones its approval covers. Pick one and it's approved at once; your travel admin books it as usual.

### One approval for everyone's travel

Once the event is approved, each person who's coming books their own travel on **Book**: the event's link fills in the city and dates. A trip is approved with the event, with no one else to ask, when:

* it arrives no more than two days before the event starts, and leaves on its last day or up to two days after;
* it's within the cap a person, or, if the event has no cap, inside the traveller's policy;
* the event's budget has room for it.

Anything else goes through your usual approvals. Changing an approved event's dates, or raising its budget or cap, sends it back for approval.

### Who's coming and arrivals

The event shows who's coming, who hasn't answered and who isn't coming, with each person's trip. **Arrivals** lists the coming flights by day, with the time each one lands, so whoever meets people at the venue knows who to expect when.

### Room blocks

For ten rooms or more, a travel admin can **Ask for a room block**: one request to the supplier's group desk, with the dates, the number of rooms and the most a room a night, instead of booking room by room. The group desk replies by email with what it can hold and the price.

## Guests

A guest is someone you book for who doesn't have a TripMazer account: a candidate, a client or a speaker. Travel admins and colleagues who book for others add them from **Book** (**For: Add a guest…**) or an event's **Invite**, with:

* their name, as on their ID;
* their email and phone, where their tickets go;
* their date of birth, gender and nationality, when an airline needs them.

A guest travels under the policy of the colleague who books for them, and their trip is listed under that colleague with the guest's name. On the **Overview** and **Reports**, the trip is counted under the guest, marked "(guest)", in the booking colleague's team. Their tickets and hotel voucher go to the guest's email, and to the colleague who booked. When the guest's phone number is on the desk, each one also reaches them on WhatsApp, with the PDF attached and the name of the colleague to ask about changes. Passport details aren't kept on the desk; they're given at booking, for the airline only.

A guest's trip earns no savings reward, for the guest or for the colleague who booked it.

Guests aren't counted on the Team plan, which counts employees who travel. See [Plans and billing](https://docs.tripmazer.com/teams/plans-and-billing.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.