The vendor is required to provide for agency needs through various means including event ticketing, reporting, customer relationship management, marketing, and development/donations.
- Non-profit licensee ticketing needs include the ability to keep ticket prices low and affordable, including service charges related to the sale of these tickets.
- System include:
1. Sales, payment processing, and ticket management
• system must provide payment plans through online and box office customers for new and renewal purchases, including single tickets;
• Ability to manage online, over-the-phone, and in-person ticket sales;
• System must be compatible with the smart payment card technology for both contact and contactless cards.
• This includes EMV standards (Europay, MasterCard, and visa) and mobile payment solutions such as apple pay, google pay, and Samsung pay;
• System has anywhere, anytime access for university staff to the back office from their mobile device;
• System must be PCI DSS (payment card industry data security standard) compliant and meet the industry standards;
• Ability to buy a membership online or at time of ticket purchase, and receive discount offers;
• Ability to create payment types and to use combination of payment types in one order;
• Refund and exchange management;
• Ability to print physical tickets, work with electronic/digital tickets, and create, modify, and maintain customizable ticket templates;
• Ability to have control of ticket design (thermal and print-at-home);
• Ability to have a sales interface with seamless upsells, add-on or recommendations.
• This content must not require vendor support to create or update without coding or html knowledge;
• Ability for walk-up sales to be conducted (data to be entered to ticket print) in less than 15 seconds;
• Ability to create private sales for select group of buyers.
2. Integration, automation, and security
• A fully developed application programming interface (API);
• Ability to allow for core automation of various processes such as analytics, dynamic pricing, scheduling price changes, and automated emails based on buyer behavior;
• Ability to integrate with third-party tools, including the scheduling and booking software, and point-of-sale solution;
• Ability to offer integrated point of sale (POS) tools that will sell miscellaneous items/merchandise to customers at events, allowing development of an understanding of the customer's purchasing needs and history;
• Ability to have real time integration with 3d ticketing partner that does not require importing or exporting data for updating inventory;
• Ability to create, modify, and maintain different levels of user access to the system with the ability to segment users within multiple organizations and to segment user access based on need-to-know;
• Support for university campus wide login integration for user access and management; and
• Ability for university student and staff card integration (for authentication purposes) at any point of sale.
3. Customer management and communication/marketing
• A fully developed, responsive, and robust customer relationship management (CRM) system;
• System must provide integrated email marketing capabilities that track conversions measurable against each customer who makes a purchase;
• Ability to send, track, and report on email campaigns from within the ticketing system;
• Ability to segment customer lists based on certain customer criteria such as zip code, state, or custom fields;
• Ability to support delivery of push notifications to patrons;
• Ability for a centrally managed database that provides for all activity tracking, email reporting, and contact management;
• Ability to support a mobile app with content delivery based on audience segmentation;
• Ability to share a ticket with another customer and track that information back into CRM; and
• Ability for ticket sharing to include creating a patron profile for the shared ticket recipient.
4. User interface, accessibility, and event management
• System must have mobile-responsive ticketing pages;
• System must run on standard pcs (personal computers) using chrome or other common web browsers;
• Ability to provide digital tickets and mobile ticket delivery options, such as apple wallet, google wallet, or mobile app;
• Ability to allow for a searchable online interface where customers can type in keywords;
• Ability to allow for “view from seat/section” and images can be easily uploaded by system administrator;
• Ability to create, modify, and maintain manifests across multiple venues and configurations, including graphical depictions that customers use for purchasing tickets;
• Ability to create, modify, and maintain subscription bundles, memberships, promotions and promotion codes, payment plans, payment types, price charts, ticket types, price zones, price types, hold types, and delivery methods;
• Ability to offer flexible packages, including tickets to multiple events, discounts, merchandise, and other sellable items;
• Ability to create, modify, and maintain websites and microsites with the ability to apply specific branding; and
• System has anywhere, anytime access for university staff to the back office from their mobile device.
- Questions/Inquires Deadline: May 20, 2025