Hey there Tessi Hive Mind!
I'm wondering if anyone has figured out a way to make the Special Request "sticky" to that constituent so that it can go from one order to another if they exchange tickets or purchase additional etc?
We have two venues, one fixed seat and the other GA, so we use our SRs to communicate with Front of House regarding wheelchair seating (pulls and no pulls), special accommodations for patrons who can't do steps, ongoing issues, and the like. We run a custom report that pulls all Special Requests for a performance that we can filter down by SR type. However, we run into the problem that if a customer exchanges tickets and the operator doesn't replicate the SR in the new order (which they would only KNOW if they looked at the original order) then the SR doesn't get carried over.
Is there anything like a Sales Note but like a "Patron Note" that could be placed into a person's account so it would pop up like the Sales Note does whenever an order is placed?
I realize I could probably do this is a Pricing Rule, but I'd rather not have to recreate a Message Only Rule every season for a group of subscribers/patrons.
Thoughts anyone?
Maybe this is more of an upgrade request for the Network...
Thanks!
Joel
Joel,
Have you considered using CSI's (Customer Service Issues)? We use those to track ongoing patron needs like access needs (wheelchairs, vision and hearing issues, etc) and other relevant patron details. Those stick with the patron rather than the order. We pull the Customer Service Issue Tracking report with every will call so that FOH and Box Office know what to expect that evening. We also use a combination of Flex Headers and Constituencies to alert the box office when a CSI needs to be checked for patron during an order. Let me know if you want more details.