Special Request - tracking as the customer exchanges etc

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

Parents
  • Hi Joel,

    We use flex headers for this - currently we have a wheelchair icon appear on a patron's header if they have a seating request or CSI in an ADA category.  I'm currently in the process of changing this over to use a text field in the flex header to actually show the text of the category so it's easier to identify if their ADA issue is wheelchair non-transfer, needs aisle, sight issues, etc.  You could use similar logic to pull that info into the report you give to FOH.  

    Feel free to reach out to me if you're interested the set-up behind any of that!

    Cheers,

    Sheela

Reply
  • Hi Joel,

    We use flex headers for this - currently we have a wheelchair icon appear on a patron's header if they have a seating request or CSI in an ADA category.  I'm currently in the process of changing this over to use a text field in the flex header to actually show the text of the category so it's easier to identify if their ADA issue is wheelchair non-transfer, needs aisle, sight issues, etc.  You could use similar logic to pull that info into the report you give to FOH.  

    Feel free to reach out to me if you're interested the set-up behind any of that!

    Cheers,

    Sheela

Children
No Data