Hello -
So our subscription renewals are under way but we have a longstanding issue: We sell parking on our website and people often (VERY often) buy one parking pass with their renewal when they need a number that matches the number of shows their subscription has (i.e. a 5 performance package needs 5 parking passes). Right now we have to contact the constituent and they very often say "sure - add 4 more passes".
Our problem is this: When adding 4 more passes to their order, hitting "done", reloading the order and then sending an email acknowledgment, Tessitura's order acknowledgement still generates with the old data. This also happens if we move someone seats in an order. After a "while", the order acknowledgement does eventually pull the correct info but the box office would really like to be on the phone and send the acknowledgment then and there with correct info. I've tried getting folks to (1) done the order and go back in, (2) close their batch, (3) go through the orders tab in the constituent module to send the ack instead of directly in the order but none of that has worked. I'm unsure what is "triggering" to eventually get the ack to pull the correct data.
I've tried tracing the sql calls to see what proc is being pulled but I'm guessing this is an API function now. Is anyone else having this "old data on a new acknowledgement" problem? Box Office really doesn't want to keep a running list of people they need to acknowledge.
Any ideas would be welcome. Thanks!
Richard Jackson
I have never had that issue, but we use custom acknowledgments. I did see another issue in your post which would drive me nuts. Having to call a patron sounds problematic to figure out the parking situation. I would revisit this to streamline the process a bit.
Here is my suggestion... Create a parking season to hold all parking, each new year will get it unique prod season moving forward. Create dummy parking performances (3play, 4play, 5play, 6play, etc., etc.) within its prod season that have a package size keyword that corresponds to a package size keyword that actually live on the package. Somewhere in your renewal path you can ask if they want season parking. Then you can do some sql magic, add the appropriate dummy perf to the order by locating the two keywords the correspond to size. You can review the orders the next day and the sales team can move the money to the real parking perfs as need with out calling the patron.
Travis