> ## Documentation Index
> Fetch the complete documentation index at: https://partner-help.letsdothis.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Reserved Entries
> Set aside a block of places for a partner or for people you invite, so they can register through a code or link without buying a ticket on the open sale.
Reserved entries let you hold a block of places for specific people and invite them to register, instead of having them buy on the open sale. You group the places together, decide who they're for, and share access by a link or a unique code. This is how you handle charity places, sponsor allocations, comped entries, and ballot winners.
## When to use reserved entries
Reserved entries fit any situation where places go to people outside the normal sale:
* **Partner and charity allocations** — give a charity or corporate sponsor a block of places, and optionally their own dashboard to manage them.
* **Invited or comped entries** — invite named people (VIPs, winners, guests) to register, with or without a discount.
* **Ballot and application outcomes** — allocate places to successful entrants of a draw.
Before you start, decide who manages the group and how people claim their place:
The partner gets their own dashboard to manage their entries, track fill
rates, copy links, and cancel places.
You send out the link and handle any changes or cancellations yourself.
One link anyone can use to claim a place, until the group is full.
Each person gets their own link, tied to their email address.
## Creating a reserved entry group
From your event, go to **Startlist → Entries → Reserved**, then choose **Create Entries**. The form is split into sections; required fields are marked with an asterisk.
Pick **Assign to a partner** or **Fill the entries yourself**, then continue.
If you're assigning the group to a partner, select an existing **Partner** or use **Add new partner** to enter their details. Skip this if you're filling the entries yourself.
Under **Group**, give the group a name and an optional description so partners and recipients know what it's for.
Under **Capacity**, set how many places the group can grant, and whether to reserve them from your event's overall capacity. Reserving from overall capacity keeps your total numbers correct; not reserving adds these places on top.
Under **Tickets**, choose which tickets the group can claim and how many of each. You can set a per-ticket cap within the group's total.
You can include tickets that are closed or off sale on your main
registration path. Reserved entries can grant access to tickets the public
can no longer book — see [Making a ticket reserved-entry
only](#making-a-ticket-reserved-entry-only).
Under **Pricing**, apply a percentage or flat discount to the selected tickets (you can include fees). Use this for charity or comped places, or leave it off for full-price invited entries.
Under **Set ticket dates**, optionally set a start and end window so the group can only claim tickets during a set period.
Under **Invitation restrictions**, optionally restrict claims by email — an exact address, or an "ends with" rule such as a single company domain.
If you assigned the group to a partner, choose under **Partner Settings** whether they can cancel entries, and whether a canceled entry is automatically reallocated as a fresh place.
Save the group. For a shared-link group, a unique link appears with a **Copy** button so you can share it.
## Sharing access and allocating places
How people claim depends on the group type.
**Shared invite link** — share one link, using **Copy invite link** from the group's menu. Anyone with the link can claim a place until the group is full, subject to any invitation restrictions. The link carries the recipient straight into checkout, where the discount (or free place) is applied automatically.
**Individual allocations** — assign places to named people with **Allocate** from the group's menu:
Upload a CSV of recipients. It must include three columns titled exactly **firstName**, **lastName**, and **emailAddress** so each person can be matched.
Email each person their unique link. You can send a test to yourself first to preview it, then track who's booked from your dashboard. To chase everyone who hasn't registered yet, see [Resending invitations in bulk](#resending-invitations-in-bulk).
Each allocation is tied to the recipient's **email address**. When they open
their link, they confirm that email before they can claim — so they need to
use the exact address you uploaded.
For a partner group, you can also **Copy link to Partner dashboard** to let the partner manage their block, and **Send claim email to partner** to email it to them.
## Resending invitations in bulk
People lose invitation emails, or never open them in the first place. Instead of chasing them one at a time, you can email everyone in a group who still hasn't registered in a single action. It's most useful as a reminder in the weeks before your claim window closes, when a group is sitting part-filled.
From the group, choose **Modify → Resend all invites**.
This applies to **every unclaimed entry in the group** — not only the rows you've selected, and not only the people shown on the current page. Before anything is sent, you'll see how many people it covers, for example `Invitation emails will be sent to 42 participants who have not completed their entry.`
This includes people who have never been sent an invitation yet — not only
those you're reminding for a second time. If you've deliberately held some
invitations back, sending in bulk releases them.
Confirm with the send button, which shows the number of invites going out. The invitations are queued and sent shortly afterward, and you'll get a confirmation of how many were queued.
### Who receives an email
Someone is included when they've been allocated a place but haven't finished registering — whether they've never been invited, were invited already, or opened their invitation without completing it.
Entries are left out when the place has already been claimed, or when it's been canceled, revoked, or not yet allocated to anyone. People who have completed their registration won't be emailed again.
If someone claims their place while the send is in progress, they're skipped rather than re-invited — so nobody gets a reminder for an entry they've just used.
### Entries with no email address
An allocation with no email address can't be invited, so it's skipped. You'll see how many were skipped after sending, for example `3 entries were skipped because they have no email address.`
Treat that count as information — you can't add an email address to a place that's already allocated. To get those people invited, cancel the allocation and allocate the place again with their address. If the group is set to reallocate on cancellation, the freed place reappears in the table ready to assign; see [Canceling and reallocating an entry](#canceling-and-reallocating-an-entry).
### When no one is waiting
If everyone in the group has already registered, there's nobody to email and the send button is unavailable. That's the expected state for a group that has filled.
### If the send fails
If you see `Error sending invitations`, nothing further is queued — try again. Anyone who already received an invitation in an earlier attempt is safe to resend to; they'll simply get the reminder again.
## What recipients see when claiming
Recipients on a **shared link** go straight to checkout, with the discount already applied, and register as normal.
Recipients on an **individual allocation** first confirm the email address their invitation was sent to. If it matches, they continue to checkout; if it doesn't, they're asked to check they're using the same address from the invitation.
If a place can't be claimed, the recipient sees a **Sold out** screen instead of checkout. The usual reasons are that the group is full, the claim window has closed or the allocation has expired, the email doesn't meet the group's restrictions, or the ticket is no longer available to the group.
If a recipient is stuck, ask them to use the exact email the invitation was
sent to, and check whether the group is full or the claim window has passed. A
**Sold out** screen means the place is no longer available through that link.
## Canceling and reallocating an entry
When you cancel an allocated entry, you can choose whether to email the participant about it. If the group reallocates on cancellation, a replacement place appears in the table for you to assign to someone else, so a freed-up place isn't wasted.
## Making a ticket reserved-entry only
A common setup is to give reserved entries access to a ticket the public can't book. The cleanest way is to take that ticket **off sale on the main registration path** — set its **Available until** date to before your public on-sale (or in the past). The ticket then disappears from the normal flow, but reserved entry recipients can still claim it through their link.
There's also a **Require invitation link** setting on the ticket. It keeps the
ticket **visible** in the normal flow but not bookable without an invitation
link — so participants can see a ticket they can't book, which is often
confusing. In most cases, taking the ticket off sale by its **Available
until** date is the better option.
## Tracking how groups are filling
The Reserved Entries table shows each group's **Total** and **Registered** counts, with a search box and an event occurrence filter. For a fuller view across groups, partners, and events, use the **Reserved Entry Performance** report — see [Reserved Entry Reporting](/docs/reports/reserved-entry-reporting).