Patron Accessibility Requests & Tessitura Customizations

Hello everyone! We are in the process of making our procedures for patrons placing accessibility requests when purchasing tickets more equitable, but we are struggling to find a solution that checks all the boxes without having to pay for multiple special customizations. Is anyone currently accommodating accessibility requests without a Tessitura customization that does not include too many extra steps for the patron, such as calling or emailing the Box Office in addition to their ticket purchase online? I would love to hear what your processes are for patrons placing accessibility requests either way. Thank you for your insight! 

Parents
  • Hi Heather,

    I did a run through your purchase pathway and I do like your payment page checkout form.  I also agree with you that having a CSI for every order is cumbersome. 

    Alternatively having a form at the performance level is great but also creates that CSI regardless of data input.  Also you can't have that data capture form for SYOS or subscriptions.

    Something that might help with filtering CSI reports - if you put this query below into a new dynamic list (open the show query button in criteria) and then run your Customer Service Issue Tracking report off that list it should filter out only the people who have checked a box, and not everyone in that's been through your payment path.  You can use the same logic to pick up any specific CSI answer.  Let me know if you want to talk through it.

    select distinct customer_no 
    from T_CUST_ACTIVITY WITH (NOLOCK)
    where  notes like '%Remain in wheelchair for duration of performance%'
    or  notes like '%Transfer from wheelchair for duration of performance%'
    or  notes like '%Require assisted listening device%'
    or  notes like '%Other (please specify below)%'

    I agree that equality isn't equity and anything we can do to level the playing field and remove barriers is worth doing.

    Cheers,

    H

Reply
  • Hi Heather,

    I did a run through your purchase pathway and I do like your payment page checkout form.  I also agree with you that having a CSI for every order is cumbersome. 

    Alternatively having a form at the performance level is great but also creates that CSI regardless of data input.  Also you can't have that data capture form for SYOS or subscriptions.

    Something that might help with filtering CSI reports - if you put this query below into a new dynamic list (open the show query button in criteria) and then run your Customer Service Issue Tracking report off that list it should filter out only the people who have checked a box, and not everyone in that's been through your payment path.  You can use the same logic to pick up any specific CSI answer.  Let me know if you want to talk through it.

    select distinct customer_no 
    from T_CUST_ACTIVITY WITH (NOLOCK)
    where  notes like '%Remain in wheelchair for duration of performance%'
    or  notes like '%Transfer from wheelchair for duration of performance%'
    or  notes like '%Require assisted listening device%'
    or  notes like '%Other (please specify below)%'

    I agree that equality isn't equity and anything we can do to level the playing field and remove barriers is worth doing.

    Cheers,

    H

Children
No Data