Ticketing Research Report

Transcription

1 Ticketing Research Report

2 CONTENTS 1. Background Research outline Participants 5 2. Current venue websites Current purchase path products Web integrations Updates to purchase paths Events Key features for a web ticketing product Most important features Ticketing functionality Fundraising functionality General functionality Products Best/worst features of existing products Considerations for a new web ticketing product General Ticketing Membership Development Summary of requirements WE ARE AD LTD All rights reserved, no part of this document may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of We are AD Ltd. In accordance with our normal practice, we must state that this document is for the use only of the recipient. None of its content may be disclosed to parties other than the recipient without the prior written permission of We are AD Ltd. Such disclosure will only be made on the basis that the contents are not passed to persons other than those specified in the consent. In addition, neither the whole nor any part of this report, nor any reference thereto may be included in any document, circular or statement without our prior written approval of the form and context in which it will appear. CONSULTATION In the event of the recipient of this document receiving a request under the Freedom of Information Act which encompasses any information held by them which was provided to them by We are AD Ltd. in connection with this confidential response, the recipient is expected forthwith to notify AD Ltd. of the request and allow AD Ltd. not less than ten working days in which to make representations. 2

3 BACKGROUND AD has worked in the arts and culture sector for over a decade, delivering streamlined online ticketing through a number of integrated solutions. In this time, we ve committed time and resource into understanding sector challenges and developing a white-label web ticketing product for the arts and culture community. In 2015, we commissioned Silver Sea Consulting to conduct a piece of research to better understand how this product could be developed further with the user/administrator in mind from the outset. This research will allow AD to build on its experience from the first phase of the AD Tessitura Bridge product with the collective knowledge and ideas of the ticketing and CRM community. 3

4 1.1 RESEARCH OUTLINE The research consisted of two main phases: Quantitative: An online questionnaire with 20 different online booking system users from venues across the UK and Ireland. Qualitative: A workshop at the Young Vic in London with 10 participants from London-based venues, AD and other suppliers. 4

5 1.2 PARTICIPANTS The following table summarises the participants of each research phase: ORGANISATION Abbey Theatre AD AD Almeida Theatre Barbican Centre Birmingham Hippodrome Birmingham Hippodrome Kings Place Music Foundation London Philharmonic Orchestra JOB TITLE Database Systems Manager Web Developer Account Director Director of Marketing & Communications IT Business Systems Manager Database Manager Application Specialist Head of Visitor Services Digital Projects Director National Theatre Box Office & CRM Systems Manager Nottingham Lakeside Arts Head of Audience Development & Marketing Philharmonia Orchestra Realex Payments Roundhouse Trust Royal Court Theatre Developer Corporate Sales Manager Business Systems Analyst Head of Marketing and Sales Royal Northern College of Music Marketing and Customer Services Data Officer Sage Gateshead Southbank Centre Spektrix The Old Vic The Old Vic Theatre Royal Newcastle Theatre Royal Plymouth Ticketing Network East Midlands Wales Millennium Centre Young Vic Web Systems Co-ordinator Ticketing Operations Manager UX Designer DBA Senior Marketing Executive Director of Operations Systems Analyst Project Manager Database Manager Box Office and Sales Manager 5

6 CURRENT VENUE WEBSITES The venue survey contained a series of questions to provide context and to help us understand the existing web & ticketing products that were being used by our sample. 6

7 2.1 CURRENT PURCHASE PATH PRODUCTS A small majority of respondents were using a tailor-made purchase path product, with the remainder using an out of the box solution. The two key out of the box solutions being used were: BlocksOffice (used by 4 respondents) TNEW (used by 3 respondents) However, almost all users of these products had to make customisations in order for them to serve their venue s requirements. Is your current purchase path an out of the box solution or a custom product? 40% 60% Custom 60% Out of the box 40% 7

8 Did you have to customise the product at all? 13% 40% 60% 87% No 13% Yes 87% EXAMPLE CUSTOMISATIONS INCLUDED: We have a lot of bespoke things that needed to be added to the product, like fee-free tickets. Roundhouse (BlocksOffice) We had to configure our Tessitura installation to work inside this boxed product. Birmingham Hippodrome (TNEW) 8

9 2.2 WEB INTEGRATIONS Almost all of our sample s ticketing systems were fully integrated with their websites. These integrations are almost exclusively via APIs, with the exception of the Royal Court s website; as a Spektrix user, they instead use Spektrix s standard web service. Is your ticketing system fully integrated with your web presence? 5% 5% 90% Yes 90% No 5% Don t know 5% 9

10 2.3 UPDATES TO PURCHASE PATHS During which year did you last update your purchase path? Don't know 5% 2010 or earlier 10% % % 15% % 2.4 EVENTS Everyone surveyed was either selling, or wanted to sell, tickets for performances via their website. There was also a very strong interest in selling tickets for free events or private events. What type of events do you sell tickets for, or would like to sell tickets for, via your website? Performances 100% Free events 84% Private Events 42% Exhibitions 21% Other 16% 10

11 KEY FEATURES FOR A WEB TICKETING PRODUCT 11

12 3. 1 MOST IMPORTANT FEATURES We asked our sample to list the three most important features of a web ticketing product; below is a word cloud illustrating their responses. The larger the word, the more frequently it was mentioned. Simplicity and ease of use were particularly likely to be mentioned as the most important features for an effective ticketing solution, both from the perspective of the administrator and the customer. next pages search money volumes channels logicalupdate getting presented selection customization upset upselling integrations page easy change rules integrations experience user information intuitive proofing make simplicitynavigate speed navigationuse checkout sell purchase ofice customer wrong flexibility efficiency cleans shows seat pricing quickly party went understand box set simple account house third control data via log online sales work design path actually select value ons phone etc multibuys ability integrity large payment responsive providers selling something messages sale ease unified offers button get add product sorry price cross costs relevant including future development next interface flexibility/editable secure published changes friendly event clear content/text performance syos reliability tickets 12

13 3.2 TICKETING FUNCTIONALITY In addition to the unprompted, openended responses above, we asked our respondents to rate how important a series of different pieces of functionality were to them, from essential to not important. 95% RATED SELECT YOUR OWN SEAT AS THE MOST IMPORTANT FEATURE Based on their responses, select your own seat was cited as the most important feature, with 95% of our sample rating this as essential. Dynamic discounting, the opportunity to crosssell similar events and functionality for packages or series discounts were also considered important to our group. Please rate how important each of the following peices of ticketing functionality is to you: Essential Important Neutral Not Important 13

14 3.3 FUNDRAISING FUNCTIONALITY From a fundraising perspective, the most important features are the ability to make donations as well as purchase new memberships and gift memberships. 90% STATED THAT DONATIONS WERE AN ESSENTIAL PIECE OF FUNCTIONALITY Please rate how important each of the following pieces of fundraising functionality is to you: Essential Important Neutral Not Important Donations 90% 10% Membership Sign-Up Purchases 80% 15% 5% Gift membership purchases 75% 15% 5% 5% Membership renewals 65% 30% 5% Ability to set up direct debits 30% 40% 25% 5% Booking for private Development events 10% 65% 25% 14

15 3.4 GENERAL FUNCTIONALITY Whilst not seen to be as essential as functionality as select your own seat (SYOS) or donations, other general functionality that was important to our respondents included 3D secure, QAS/ postcode lookup and priority booking. RATED 3D SECURE AS AN 70% ESSENTIAL FEATURE Please rate how important each of the following pieces of general functionality is to you: Essential Important Neutral Not Important 15

16 Web product research report for We are AD 3.5 PRODUCTS There was also an appetite to cross-sell merchandise during the purchase path. Please rate how important it is to you to be able to sell each of the following products: Essential Important Neutral Not Important 3.6 BEST/WORST FEATURES OF EXISTING WEB PRODUCTS When asked for their favourite features of their existing web products, the group were particularly likely to mention select your own seat functionality across multiple platforms and flexible seat maps. The least performant/worst features mentioned were a general lack of flexibility/control and the absence of responsive design for those who don t currently have this functionality. 16

17 CONSIDERATIONS FOR A NEW WEB TICKETING PRODUCT During the workshop we explored some of the key issues that arose from responses to our survey in more depth with the participants. 17

18 4.1 GENERAL At present, our group felt they spent too much time duplicating information across multiple systems. Unanimously, the group stated that they currently spend far too much time constantly checking and matching multiple systems; one example was having to enter things like ticket prices into a text field for the website, when this information is already held in Tessitura. As with the survey results, it was reiterated that an easy customer journey and simple administration were key. Our website is so shit, that you have so many clicks just to see anything or do anything we just think we should keep it as simple as possible. Another central requirement highlighted was flexibility; this is mentioned below in relation to production pages, but in a more general sense people wanted the opportunity to make tweaks and changes without being beholden to a web development company. I ideally would like to put everything in Tessitura once, teach the website where to pull it from, and then it goes into the various places on the website it needs to go to. Anonymous 3 Anonymous 1 You need to determine the parent place for information Artifax, Tessitura or straight onto your CMS. Anonymous 2 18

19 4.2 TICKETING PRODUCTION PAGES During the workshop we conducted an exercise to create an ideal world production page; the images below illustrate firstly a list of what information these pages should contain, and then an example of how this could be laid out. The most important feature for these production pages was flexibility; our participants wanted the freedom to prioritise different elements based on their importance (e.g. sometimes the cast for a production is a key selling point and sometimes it s not, therefore this should appear above the image). This was particularly important for multi-art-form venues, where you might require several different production page templates per art-form. Other features that were suggested included: Dynamic confirmation pages so that relevant information such as consent forms could be shown on completion of a booking, or on dynamic confirmation s. Availability indicators, e.g. number of tickets remaining when below a specified threshold. For those entering via the homepage, there was also an interest in skipping directly to the purchase path, bypassing the production page entirely (for people who already know they wanted to attend). As an aside, a few organisations have been discussing developing a common set of schemas for structured data markup on web pages for the arts sector, to improve SEO for these pages. 19

20 UPSELLING/CROSS-SELLING There are various add-ons that our group would like to be able to sell once tickets to an event have been added to their basket: Carparks Merchandise Programmes Restaurant bookings Interval drinks Related talks itunes/digital downloads They were also interested in the potential to cross-sell other events based on the customer s previous purchase history, website behaviour or what s in their basket. Finally, the new rules allowing a user to amend an order with extra purchases up to 15% of the original order value without the need to complete the checkout process again sparked a lot of interest, and was discussed as an extra opportunity to sell add-ons, such as programmes or merchandise without disrupting the ticket purchase journey. DYNAMIC DISCOUNTING As the bulk of our group were Tessitura users, there was an assumption that the pricing rules engine in v12.5 would be expected to carry out most of their dynamic pricing activity or pricing-based messaging, rather than relying on their web product. However, this was based on the assumption that the new engine delivered everything that it promised, and those building new websites at the moment wanted a back-up solution should it not meet their requirements once released. In the interim, there was some frustration from those relying on their web product to automatically calculate discounts such as multi-buys. The pricing rules are quite restrictive in BlocksOffice, just because it s not that dynamic and there aren t that many options. For me, the important thing is making sure that the messaging is correct and that you can enter the messaging at whichever point you wish. SOUTHBANK CENTRE It s a balance between making them very aware of (the potential discount), and not forcing it. PHILHARMONIA There was also an interest in seat based messaging, which can be challenging to do in Tessitura. We have it, but it s something we struggle with because of seat types not changing from performance to performance [we want] to be able to control seat attributes or seat information more fluidly. NATIONAL THEATRE When working with offers/promos, the sample participants also stated that they wanted the opportunity to very specifically offer a discount on a restricted range of seats, so that they could strategically dress the house without relying on external partners, such as Time Out. To be able to go you can have this seat for that much... to be quite specific, so that you can properly dress a house SOUTHBANK CENTRE At the more advanced end of the spectrum, there was a suggestion that there could be very sophisticated segment-based pricing which changed dynamically based on campaigns or cookies. 20

21 TICKET AGENTS There was a great deal of frustration amongst all of our participants that they were having to manage their agents ticket allocations in a very manual way. Ideally they wanted the agents to be able to sell directly from the same ticketing system, thus reducing labour and increasing efficiencies. I d love to be able to say: here s your allocation See Tickets and then as they sell through their website it sells the seats that they ve sold onto our system (via a) gateway where their system talks directly to ours. SOUTHBANK CENTRE 21

22 4.3 MEMBERSHIP The group were interested in expanding the current functionality beyond simply selling and renewing memberships. One area of particular interest was selling and renewing memberships via direct debit in a way that would meet industry compliance and standards. Ideally this would integrate directly with account checking software and record the bank details directly into the CRM system. Another area that the participants flagged surrounded the use of promotions and memberships. Currently there is no function in any of the users CRM systems that could accommodate this, which limits their ability to entice new members using discounts. They would be interested in a new web product helping them to deliver upon this. The last task for the group was to define a process in which a customer could purchase a gift membership on a website. There was a lot of discussion regarding how the gift membership fulfilment would work, with the general consensus being that an option to the voucher to its intended recipient would be preferred. Additionally a customisable image for the would be necessary in order to add seasonal information. 22

23 4.4 DEVELOPMENT All of groups wanted the ability to issue tickets to private Development events via their websites, as well as more general private events (e.g. think-ins at Southbank Centre) where an event needs to be book-able by anyone (i.e. not restricted to Members or Donors) but the event can t appear publicly on the venue website. At present, the only workaround is for people to create a Tessitura event but skip the publishing phase of getting this online; alternatively, some people resort to using Eventbrite. This is far from ideal. Beyond the standard fundraising pages the group found it difficult to come up with additional examples. Development campaigns tend to be very bespoke, for example name a pipe, so it needs to be considered on a case by case basis. That being said, it would be preferable to have flexible, customisable donation pages where a simple donation box could be displayed alongside custom content. This flexibility would allow them to scale solutions for themselves and deliver customer-centric online experiences. There was a discussion about private events for corporate sponsors and supporters, however the only example of this working well at present was a completely customised approach by the Old Vic, relying on custom tables with sponsors allocations that could be called on over the course of a year. This area would benefit from further exploration with fundraising experts during the design phase. 23

24 SUMMARY OF REQUIREMENTS 24

25 Below is a summary of the requirements being considered in AD s new web ticketing product, based on the feedback collected during the survey and the workshop: PRODUCTION PAGE Flexibility on the order and appearance of sections, by production Dynamic and customisable Book Now button Priority booking and relevant messaging Related packages Productions which can be configured to only be seen with a specific URL and do not appear in the calendar Configurable performance layout to cover exhibitions and conferences SELECT YOUR OWN SEAT (SYOS) Sections with image overlay Sections should also display availability e.g. Good Availability, Sold Out SYOS designer to alter the appearance of rows and seats View from seat Seat messaging which can be customised by performance to cover access and restricted view Best available seat selection CUSTOMER SPECIFIC SEATING Access booking Seats in allocations available to certain groups Automatic discounts on seats where applicable Members Priority booking Seats in allocations available to certain groups ADDITIONAL ITEMS Restaurant bookings Related merchandise Interval drinks BASKET FUNCTIONALITY Dynamic discounting e.g. buy three events and save 20% Donations PAYMENTS 3D secure with no supplier restriction Tokenisation CONFIRMATIONS Editable confirmations Dynamic confirmations based on basket contents MEMBERSHIPS Configurable membership levels with custom messaging Direct Debit integration with a 3rd party authorisation service, ideally integrated back into the CRM system Gift memberships CUSTOMER ACCOUNT AND REGISTRATION Address lookup which is not restricted to a specific supplier Option to register without an address Gift aid sign up with configurable messaging Interest codes Data protection DONATIONS Donation slider Donation box Customisable donation pages for specific campaigns OTHER FEATURES Built-in waiting room as standard Connection thresholds which can be set by the user Responsive design Delivery methods which can be restricted by performance INTEGRATIONS EPOS systems Artifax Finance systems Additional databases, e.g. image databases. 25

26 Please do get in touch with any questions, we d love to hear from you! THANK YOU +44 (0) [email protected]