Order Acknowledgment with old data

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

Parents
  • Hi Richard!

    While I've never experienced the same issue with order acknowledgements not updating in a timely fashion (aka immediately), I am very familiar with your parking pass problem. Do you use TNEW? If you do, I would recommend setting up a Multiple Price Type/Message Only pricing rule. Then, if anyone adds any package price type but only 1 parking price type "seat," a pop up in the cart can remind them they need a parking pass for each performance and link them back to the page to buy more parking if they wish. As John noted, patrons looooove not reading instructions, but a friendly pop-up reminder goes a long way.

    Best,
    Darryl

Reply
  • Hi Richard!

    While I've never experienced the same issue with order acknowledgements not updating in a timely fashion (aka immediately), I am very familiar with your parking pass problem. Do you use TNEW? If you do, I would recommend setting up a Multiple Price Type/Message Only pricing rule. Then, if anyone adds any package price type but only 1 parking price type "seat," a pop up in the cart can remind them they need a parking pass for each performance and link them back to the page to buy more parking if they wish. As John noted, patrons looooove not reading instructions, but a friendly pop-up reminder goes a long way.

    Best,
    Darryl

Children
No Data