Tips: Cancellation Strategy (Exchange/Donation/Refund Processing and Messaging)

Starting a thread dedicated to a topic we're all likely to be devoting a lot of time to.

Shall we also try using the Tags feature within it? Then folks can use it as a filter to narrow posts to one or the other. #CancellationProcessing and/or #CancellationMessaging 

I'm thinking brilliant strategies (or hacks) or a place for questions that have you stumped.

To start, it off...

1) Cancellation email notice with web form with options about which route customer wants, exchange/donation/credit/refund. Easy for them; head start for your team.

2) If you are tokenized/don't save credit cards, pointedly call out somewhere in that messaging that your organization will calling to request the credit card number in order to process the refund.

Parents
  • How are people handling rescheduled concerts?  Are you keeping them setup as normal and then just changing the date in the system, so that ticket holders can keep their current tickets, or are you creating new events and exchanging ticket holders into the new event?  I'm not sure what the best way to handle it is (and see the pros and cons of each way)

    Thanks!!

  • Hi Kari and everyone! I am curious what you are considering in terms of Tessitura configuration and financial information as you reschedule your performances. We'd love to know more so we can help develop some guidance. What is your finance department asking you to do when you move a performance to a new season or fiscal year? What is your marketing department or others asking in terms how your new season looks? 

    Thanks!

    -Michael Flaherty-Wilcox

  • Hi Michael!

    After reviewing the business continuity resources, this is what our organization has decided to do:

    • Change date of current concert that has been postponed to the new date
      • change all associated dates (price types, web, MOS, etc)
      • Patrons get to retain seats and no need to re-issue tickets.
    • Update GLs in pricing layer to reflect next fiscal year, so that all purchases from here on out post to the correct GL
    • Finance will do a mass journal entry in accounting software (we use Great Plains) to account for movement of revenue from current FY to next FY.
      • I will run Performance Transaction Detail for each affected concert to get constituents, GLs, and total revenue to be adjusted.
    • I also created a new season that we can use to report out on rescheduled concerts.  I named it 20-21 Rescheduled FY20 and added it to next fiscal year.

    Unfortunately, this type of configuration will only work for one-night only concerts.  It is possible that we will attempt to reschedule some of our subscription shows, which have two performances, into just one rescheduled performance.  Two performances means two sets of subscribers, which will guarantee seat overlap, and I'm not exactly sure how that is going to work, or the best way to handle that.

Reply
  • Hi Michael!

    After reviewing the business continuity resources, this is what our organization has decided to do:

    • Change date of current concert that has been postponed to the new date
      • change all associated dates (price types, web, MOS, etc)
      • Patrons get to retain seats and no need to re-issue tickets.
    • Update GLs in pricing layer to reflect next fiscal year, so that all purchases from here on out post to the correct GL
    • Finance will do a mass journal entry in accounting software (we use Great Plains) to account for movement of revenue from current FY to next FY.
      • I will run Performance Transaction Detail for each affected concert to get constituents, GLs, and total revenue to be adjusted.
    • I also created a new season that we can use to report out on rescheduled concerts.  I named it 20-21 Rescheduled FY20 and added it to next fiscal year.

    Unfortunately, this type of configuration will only work for one-night only concerts.  It is possible that we will attempt to reschedule some of our subscription shows, which have two performances, into just one rescheduled performance.  Two performances means two sets of subscribers, which will guarantee seat overlap, and I'm not exactly sure how that is going to work, or the best way to handle that.

Children
No Data