Hi all,
At National Museums Scotland we're thinking about customer journeys from our main website CMS to TNEW. As part of this conversation, the question about whether to offer guest checkouts or not has been raised. We understand how we can benefit from asking all customers to create an account, but are interested to know whether requiring a log in could be off putting to customers.
One of our objectives for TNEW is to maintain the online booking levels we've had since online booking stopped being required by COVID restrictions, or, failing that, increasing online ticket sales from pre-pandemic levels (which were quite low). Because of these we don't want to put anyone off buying online by forcing a log in.
Is anyone able to share any testing or data they've gathered about this and whether requiring a log in has resulted in lower online sales? This is probably most relevant to museums or other organisations like us that haven't historically had sold out exhibition runs but it will be interesting to hear a range of experiences from the community.
Thanks in advance for your thoughts and apologies if this has already been asked (I did a search but couldn't find anything super recent).
Hannah
Hannah,
I cannot offer anything about sales being reduced by forcing a log in, but what I will say is this. It has long been made known to our Box Office (pre-TNEW) that the logging in/account creation/password reset part of purchasing tickets was the biggest frustration. So much so that, when guest checkout was announced, it was not even a discussion but a given that we would start offering it to patrons. I just ran a search and looked at the past six months; approximately 60% of our logins created were guest checkout logins. And that feels pretty consistent with what I have seen come in as well prior to the last six months. Given that, I can only assume that at least half of our patrons want to just straight up avoid the password/logging in process.
Admittedly, we are a presenting organization. So we might not have the same level of commitment by patrons. They are much more concerned with which artist is coming and wanting to see that particular artist than say someone might be about supporting their local museum, theatre or symphony. So that would naturally translate to commitment to maintaining an active login on the website as well. That said, it is also clearly an indication that, in this password heavy world... at least our patrons, just do not want to deal with it.
Best of luck!
John A. Moskal II
We heavily analyzed this before Guest Checkout was available, using Google Analytics, and creating an account/resetting a password was identified as a very significant hurdle to completing a sale (given the nature of our business as a presenting organization, 90+% of our patrons would have to do one or the other every time they made a purchase, as at best most patrons would only make one order once a year or once every other year). When we enabled Guest Checkout we observed a distinct improvement in conversion rates.
And then we had to turn it off again, because it doesn't play nicely with online transactions that require an active account, such as contributions or streaming events using Gated Digital Content. That's a real frustration for us, but I don't think selective Guest Checkout availability is even on the roadmap.
Hi John, Gawain, and Hannah,
From the TNEW Product Team, I am of course following your stories closely. I am impressed to hear some of these conversion statistics when using Guest Checkout.
Gawain, regarding your comment about not playing nicely with Digital Content and Mobile Tickets, one of the features we are excited to release with v16 will be functionality to permit a user who has only used Guest Checkout in the past to create a password and access their account and purchases. Would that help you to turn the feature back on?
Paul
I think the big sticking point is contributions (but also I guess packages) as they tie back in to ranking-driven MOS changes as well as other customer account driven changes. I haven't tracked Guest Checkout for a while as a result, but we also had difficulty sort out the ramifications of guest checkouts for existing logins, merging guest checkout accounts, etc.