russss
commented
4 years ago For the purposes of today I'm just going to push an update out an hour or so before the sale to remove the date. I might just link to the blog post instead.
Open jellybob opened 4 years ago
russss
commented
4 years ago For the purposes of today I'm just going to push an update out an hour or so before the sale to remove the date. I might just link to the blog post instead.
This is currently an unproven hypothesis, but I'm concerned that the rate each batch is going to sell out at will mean for most people all they see is a message saying "Tickets are on sale at [time]", immediately followed by "Tickets are on sale at [later time]". The worst case here is that tickets sell out before the time on the website can be updated, a user starts the checkout process, then gets told tickets are unavailable but the next sale starts a minute ago.
I suspect the majority of people will get what's going on, and that they've just missed the tickets in the current batch, but I am expecting a smaller group to get confused by the situation and either end up contacting us (which then takes effort to resolve), or just being left with a bad impression.
876 went some way to resolving this, but as Russ pointed out adds further complexity to the ticket purchase code, where more complexity really isn't needed. I'm also not sure that it really solves the problem beyond the level of making sure people don't see a message saying tickets will be available at a given time when those tickets have already been sold.
I think the ideal solution here is something that both displays the next sales date, and in the hour or so after tickets have been on sale acknowledges that tickets have been on sale, but the user has missed them. I'll see how much noise is generated this evening, and then take this further if its a significant level.