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

# Set up dinner event tickets and guest seating

> Sell dinner event places, collect dietary choices, configure optional reserved tables or seats, and prepare guest reminders.

Use **Dinner** for a supper club, banquet, or ticketed meal. It starts with a **Dinner Seat** ticket and a suggested capacity of 40. The name “Dinner Seat” does not enable assigned seating or table selection.

## Template starting point

| Setting | Initial choice |
| - | - |
| Schedule | One day |
| Admission | Paid tickets |
| First offer | Dinner Seat · suggested price 25 in your site’s currency |
| Capacity | 40 |
| Attendees choose a time | Not enabled |

These are editable suggestions, not recommended prices or venue limits. Replace the dates, price, and capacity with your own. See [how onboarding works](./overview#complete-onboarding).

## Choose the onboarding answers

Open **Create Event** in the selected workspace.

1. Select **Dinner**, name the meal, and set the actual start and end.
2. Choose **Paid tickets** for general seating or **Assigned seating** if guests must choose particular seats or tables.
3. Set the real price and guest capacity; use **Continue later** while completing questions and any seating map.

<Note>**Create my event** may publish immediately when the requirements are met. Use **Continue later** to finish setup as a draft. Review any plan or publishing message before sharing the event.</Note>

## Finish the event settings

| Where to go | What to configure |
| - | - |
| **Tickets** | State what the meal ticket includes and set the quantity and per-order limits. |
| **Additional Info** | Add dietary or meal-choice questions using [registration fields](/event-management/additional-information), and collect each guest’s answers when necessary. |
| **Seat Charts and Tickets** | For allocated seating, create/publish a map and attach ticket categories. For selling a whole table, follow [advanced seating layouts](/seating-charts/advanced-layouts). |
| **Venue & Location** | Provide the restaurant or room and the intended arrival time. |
| **Email Communication** | Confirm the booking and include arrival, meal, and contact instructions. |

## Choose the unit you sell

Decide whether checkout sells individual places, a group ticket, or a whole table. Those are different configurations. A dropdown saying “Table of six” is only an answer unless the actual ticket or seating rules reserve six places. Check the unit, seat count, price, and attendee collection together. Dietary answers are information for your team; they do not automatically manage catering inventory.

## Check the attendee experience

* Buy the intended unit in a test flow and check the total number of places and price.
* Verify the correct dietary/meal answer for each guest.
* For reserved seating, confirm the selected table or seat labels in the booking summary.

Review the event’s saved status and [publish/share controls](/event-management/manage-events) when it is ready. Return to [all event types](./overview) to compare starting points.


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