Resolve an unassigned event ticket at the support desk
An “unassigned” label does not by itself tell staff whether a ticket can be scanned. The organizer’s claim setting and current ticket state control the next step. Use the issuer’s support view and an authorized request; keep the gate decision separate from filling in a name.
Boletolibre editorial team
Published
1. Find the exact ticket
Download the unassigned-ticket desk card (Markdown, English)
At the support desk, locate the event edition, order and individual ticket using the issuer’s approved search or scan method. Confirm the ticket belongs to that order, is still active, and has not already been checked in. Check who may assign it under the event’s support process. Do not assign it merely because someone presents a screenshot or a buyer name.
2. Use the supported claim route
run.events documents opening an Unassigned ticket in its Support Desk, then either configuring the attendee manually or inviting the assignee to personalize it. Ticketstripe uses a different claim flow: with Required claiming, an unclaimed bundled ticket has no scannable barcode until claimed; with Optional claiming, it may already have a barcode. Follow the actual ticket and provider setting rather than treating every unassigned ticket as blocked or ready.[1][2][3]
3. Check the result before admission
After the supported action, reopen the ticket or order. Verify the assigned or claimed state, current holder field where used, and the credential and check-in status that the gate will see. If the expected record is missing or the guest cannot complete the claim, route the case to the named exception owner. Record the outcome without copying ticket codes or personal details into a loose desk log.
Sources and further reading
- Support desk - Handling unassigned ticketsrun.events · Accessed
- How to help attendees claim tickets at eventsTicketstripe · Accessed
- Claim-Your-Ticket optionsTicketstripe · Accessed