Daily Ticket Availability

Last week we had a good conversation with folks at Baker Richards and Pricing Institute (now JCA). At this time T-Stats and therefore the RMA are fairly blind to seat history, It can primarily see the current status of seats. Therefor most of what we were hoping for is currently not possible with these tool. The hot seat index can give you a sence of final duration of hold codes, with the last metric ("I'm not looking at the system right now so I do not have the precise name given to this data.). However, this is not at all a full picture of the implementation of holds on sales over time.

When some other projects are finished we are likely to start looking at seat history in detail ourselves. We are still intrested in any reporting folks are doing regarding hold history, and any descriptive, diagnostic, predictive or prescriptive analysis folks might be doing.

--Tom

On Tue, Oct 7, 2014 at 11:53 PM, Revenue Management Application / Pricing wrote:

Hi Tom, did you make any progress with this?
From: Tom Brown
Sent: 4/24/2014 12:46:59 PM

Has anyone worked out a way to do high level reporting over time on daily ticket availability.

I'm thinking about looking at long term trends on things like Hold Codes...

And want to see how many tickets are available on each day and under each type of hold code or not.

--Tom

Interesting, I am looking at this also. The least problematic approach so far is keeping logs of historic availability reports, then compiling them into a larger document. This is far from ideal, and does not let us look at past years availability trends.

 

When you analysis your older reports what type of analysis do you find useful to do on this data?

--Tom

On Wed, Oct 08, 2014 at 9:23 PM, Nicholas Hudson-Ellis > wrote:


Interesting, I am looking at this also. The least problematic approach so far is keeping logs of historic availability reports, then compiling them into a larger document. This is far from ideal, and does not let us look at past years availability trends.


From: Tom Brown
Sent: 10/8/2014 5:07:07 AM
Last week we had a good conversation with folks at Baker Richards and Pricing Institute (now JCA). At this time T-Stats and therefore the RMA are fairly blind to seat history, It can primarily see the current status of seats. Therefor most of what we were hoping for is currently not possible with these tool. The hot seat index can give you a sence of final duration of hold codes, with the last metric ("I'm not looking at the system right now so I do not have the precise name given to this data.). However, this is not at all a full picture of the implementation of holds on sales over time.

When some other projects are finished we are likely to start looking at seat history in detail ourselves. We are still intrested in any reporting folks are doing regarding hold history, and any descriptive, diagnostic, predictive or prescriptive analysis folks might be doing.

--Tom

On Tue, Oct 7, 2014 at 11:53 PM, Revenue Management Application / Pricing wrote:

Hi Tom, did you make any progress with this?
From: Tom Brown
Sent: 4/24/2014 12:46:59 PM

Has anyone worked out a way to do high level reporting over time on daily ticket availability.

I'm thinking about looking at long term trends on things like Hold Codes...

And want to see how many tickets are available on each day and under each type of hold code or not.

--Tom

So I'm an IT guy and do not monitor these reports daily. Do I understand correctly, you are looking at additional sales that are facilitated or allowed by the releases of holds. Are you intrested in this as a measure of "pent up demand" for a certain type of ticke? If you find that there is a spike around the time of a release. Then what do you do?

--Tom

On Thu, Oct 9, 2014 at 1:12 AM, Revenue Management Application / Pricing wrote:

The main insight is to see when spikes in sales coincide with held seats being released and made available. This is common sense when you are monitoring reports daily, but is harder when looking over a longer period.
From: Tom Brown
Sent: 10/9/2014 2:14:52 AM
When you analysis your older reports what type of analysis do you find useful to do on this data?

--Tom

On Wed, Oct 08, 2014 at 9:23 PM, Nicholas Hudson-Ellis > wrote:


Interesting, I am looking at this also. The least problematic approach so far is keeping logs of historic availability reports, then compiling them into a larger document. This is far from ideal, and does not let us look at past years availability trends.


From: Tom Brown
Sent: 10/8/2014 5:07:07 AM
Last week we had a good conversation with folks at Baker Richards and Pricing Institute (now JCA). At this time T-Stats and therefore the RMA are fairly blind to seat history, It can primarily see the current status of seats. Therefor most of what we were hoping for is currently not possible with these tool. The hot seat index can give you a sence of final duration of hold codes, with the last metric ("I'm not looking at the system right now so I do not have the precise name given to this data.). However, this is not at all a full picture of the implementation of holds on sales over time.

When some other projects are finished we are likely to start looking at seat history in detail ourselves. We are still intrested in any reporting folks are doing regarding hold history, and any descriptive, diagnostic, predictive or prescriptive analysis folks might be doing.

--Tom

On Tue, Oct 7, 2014 at 11:53 PM, Revenue Management Application / Pricing wrote:

Hi Tom, did you make any progress with this?
From: Tom Brown
Sent: 4/24/2014 12:46:59 PM

Has anyone worked out a way to do high level reporting over time on daily ticket availability.

I'm thinking about looking at long term trends on things like Hold Codes...

And want to see how many tickets are available on each day and under each type of hold code or not.

--Tom

We have a custom report that will look across multiple seasons to show how many Holds were released but remained unsold. It provides the release date and time as well as the value of those seats. Also it shows if they were placed in a customer's account but then released it will show which customer and when they were released along with the value.

The intent of the report is to determine if holds are being released with enough time to sell them and how much it is costing us in revenue by them remaining unsold.

The report only looks at the last Hold Code and it only recognizes the top Hold Code not those that may be layered underneath.

I like it because it places a value on the delay of releasing holds and certain high value customers who say they will buy but release the unpaid reservation too late to resell them.

If you'd like to see the report in action shoot me an e-mail!

Nicole

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Nicole Keating
Senior Director, Ticket Services
The Adrienne Arsht Center for the Performing Arts
of Miami-Dade County
1300 Biscayne Blvd.
Miami, FL 33132
ph. (786) 468-2330 fx. (786) 468-2005
www.arshtcenter.org

Pent up demand is one possible factor that we are trying to understand better. Essentially, I am trying to get a 4 P's marketing approach to monitoring the sales cycle, in-season and for post-season reviews:

• Product: type of performance, price reserve inventory
• Price: ticket price/dynamic pricing implementation
• Place: Sales channel/consignments
• Promotion: other marketing tools, e-news blasts, website push etc...

When price reserve availability cannot be charted alongside ticket sales and price history, there is a tendency to attribute all changes in demand to things that can be measured: price changes, and proximity to performance.

I would really like to remove that tendency.