Adding CSIs across multiple performances in a Package

Hey everyone,

First, a little background on why I'm asking. Our theatre uses CSIs primarily to notify house management about patrons with mobility issues. We are currently seating our 2019 season (we operate on a calendar year), and are adding in CSIs for patrons that have these issues. My team is going through and adding seat number and the nature of the patron need manually to each of the 6 performances included in our season. When we attempt to add in a CSI to a Package, the CSI then shows up when we run a CSI report for ANY performance. Our inability to just make note of the patrons needs and seats for the whole season at once essentially increases the amount of information we need to enter in by about 600% 

So my question: is this Pack-based CSI showing up on every order because we are entering the information incorrectly or because we are pulling the information incorrectly? Or is it even possible to add a CSI across multiple performances in a package so that the same CSI does not show up in performances NOT associated with that package?

Boy, I hope that made sense. All help is welcome, let me know if there's any more info I can give to help solve this. Thank you all!

Parents
  • Former Member
    Former Member $organization

    So controversial opinion but CSIs are not the appropriate place for mobility issues.

    We are confronting the same issue and I think this info will be put in order custom fields (which can be configured from the front end).

    If Beryl uses a wheelchair that is information pertinent to Beryl.  But more it is information pertinent to the ticket sales (seat A20 uses a wheelchair).

    For example, what if Tanya buys Beryl's ticket? We want to record that Beryl uses a wheelchair but Tanya does not always require wheelchair access.

    This is order-level info, not CSI level.

    The downside is that you need to re-enter the info each year for Beryl. The upside is that if it is an order custom field you do not have to enter it every performance.

Reply
  • Former Member
    Former Member $organization

    So controversial opinion but CSIs are not the appropriate place for mobility issues.

    We are confronting the same issue and I think this info will be put in order custom fields (which can be configured from the front end).

    If Beryl uses a wheelchair that is information pertinent to Beryl.  But more it is information pertinent to the ticket sales (seat A20 uses a wheelchair).

    For example, what if Tanya buys Beryl's ticket? We want to record that Beryl uses a wheelchair but Tanya does not always require wheelchair access.

    This is order-level info, not CSI level.

    The downside is that you need to re-enter the info each year for Beryl. The upside is that if it is an order custom field you do not have to enter it every performance.

Children