Hello - I would like to inquire on how your organizations are handling flaging sold out events for your Web Sales Channel.
Currently we run a stored procedure that will update an event with a performance status of SOLD OUT and at the production season level we also maintain a content type of Production Season Status that we also update to Sold out.
Question: When you update and event with a SOLD-OUT is your organization currently also updating the end date on the Web MOS to the sold out date in order to make sure the Web-API does not return on_sale_in = Y
Bob
We typically manage our web display based on ticket availability, which is obviously a different thing to being sold out. We're also generally vague in the verbiage on our site, (i.e. "tickets are not currently available"). This covers us if tickets might be available under a different web MOS or if there are holds we might in the future release (thus putting the performance back on sale). One thing we have done is created a way for users to add themselves to a notification list in the event that show with no current availability has been very popular. Then if we expect to release a number of holds, we will email the notification list first to alert them to the new availability.