Continuing the Discussion, TLCC Denver: Tracking accessibility needs effectively. Tips and tricks?

Hi everyone, This is a continuation of a community discussion that happened during TLCC Denver. What came out of the initial discussion is that there are many different ways to record and track accessibility needs that all have their ups and downs, but not one of them seemed to fully track the necessary information in a manner that didn't require a lot of "legwork". There was a lot of interest in this topic so I would like to broaden the discussion a little bit more.

How do you track accessibility needs/requests in tessitura for your venue? Do you use CSI's, price types, special requests? Is it reportable? Does it require a customer service agent to call to record the need?

In an ideal world, how would you like Tessitura to record accessibility needs? What features would be most useful and how would they function? How impactful would these ideal features be for your company, what resources would they save?

Parents
  • Hi Crystal, 

    We use CSIs and would love to have form fields on SYOS and packages in TNEW to be able for us to help more.  That way we could allow patrons input to do a variety of things like update attributes or and add order notes.  At this stage there is a customer service component.  Previously I've worked at orgs that have used allocations for signed performances etc which is a little less labour intensive/inaccessible.

    Some additional accessibility however (like visual guide of the route and plans of the foyer etc) can be available without additional box-office labour and maybe a little in the preshow email from Marketing.

  • Thank you for your response! 

Reply Children
No Data