- While ticket admin can have all attendee types available on all tickets, many clients apply attendee types as part of a broader strategy. For example, if an event projects as a high demand event (i.e. Chicago Cubs vs St. Louis Cardinals) ticket admin will typically receive more requests than available tickets. Most clients give business development requests precedent over employee use. For clients who place an emphasis on business development, by not offering employee attendee types (excluding employee – host) it helps to drives proper usage for events where business development should take priority while reducing noise.
- For lesser demand events, evaluate allowing tickets to be requested for employee reward & recognition or personal use. There are events because of weather, opponent, location, timing that may not have client/business development demand. By proactively identifying these opportunities clients can optimize inventories. Features like triggers, auto-assign and lottery allow ticket admin to automate some of these processes.
- Implement host to guest ratios. For example, you have a suite with 20 tickets. Configure tickets where 4 tickets are available for employee host and 16 tickets are available for external requests.
- Eliminate +1’s: For high demand event, to maximize opportunities, do not allow employees to bring a guest (i.e. spouse).