Oh Those Messy Sources!

Hi everyone!

Our souces are, in a word, messy! Ticketing struggles to find them. I'm pushing to standardize with formal naming conventions.  I've yet to find one that works across all departments.

We frequently have 12+ promo codes running simultaneously for a single production (across many) and track with fine detail between subs and single tickets.

Has anyone come up with a spectacular format you would be willing to share? Perhaps there's documentation I've missed?

I'm considering a seperate Excel document though it seems counterintuitive!

Many thanks for sharing!

Michelle

 

 

 

 

 

  • Although I never got time to finish it I had started working on a Custom Screen in Perfroamnce Information to pull through all the information for that perormance that Box Office need on a single screen.

    This was to include offers and promo codes - sql for that is here

    select
           appeal_name=a.description,
           s.source_name,
           o.source_no,
           w.promo_code,
           o.terms,
           price_type=pt.description,
           o.start_dt,
           o.end_dt

    from t_mos_offers o (NOLOCK)
    join t_perf p (NOLOCK) on o.perf_no=p.perf_no
    join tr_price_type pt (NOLOCK) on o.price_type=pt.id
    join tr_mos m (NOLOCK) on o.mos=m.id
    left join tr_web_source_no w (NOLOCK) on o.source_no=w.source_no
    join tx_appeal_media_type s (NOLOCK) on o.source_no=s.source_no
    join t_appeal a (NOLOCK) on s.appeal_no=a.appeal_no
    where o.perf_no=@perf_no
    order by o.start_dt desc, o.end_dt

    This never happened only because I got caught up in the web project and didn;t have time. 

    The alternative that was used was that we got Confluence and Jira from Atlassian (free for non-profits) and used Confluence as an Intranet for Box Office and Jira as a way of processing the requests for new offers.

    Mark

  • Michelle,

    We created a custom table in Tessitura to track that is then linked to a report on our intranet. Our reps can enter the source code quoted by a patron to find all the details - price type to use, keyword for searching perfs, rules for redemption, contact name if any questions, start and end dates etc. It's worked quite well for us. Whoever sets up the promo, enters the info into the custom table. We have a promo create form that marketing fills out with all the necessary information and normally we just copy and paste the info from the form into the table.

     

  • Hi Michelle,

    We have an Excel doc that we save within Tessitura that lists all the offers and promos. It's basically a chart that lists each concert, with all offers built into that concert. Similar to what Michele is describing above - for each promo we list the keyword, mode of sale, valid dates, valid price levels, any restrictions, etc. Reps use Ctrl+F to jump to either a specific concert or to a promo code that the patron has quoted. Our Marketing department, too, fills out an Offer Request form and then we, in Ticketing, build it in Tessitura and upate the doc.
    Reps can access this document by clicking the Help icon, entering a keyword (something like "special" or "offers") and then double clicking on the document. We set this up using the TR_HELP_DOCUMENT_CUSTOM System Table.

  • We have several means of getting the information for a source code... it's all meant to be crossed referenced, and duplicated information so that our staff can easily access it anywhere they feel comfortable with.

     

    • We map the source number to a promo word in TR_WEB_SOURCE_NO.  That way when staff are in an order they can do a search for the word and get the corresponding source number.
    • Thanks to Joel Ambrose in Pittsburgh we got a "Production Info" custom tab that allows our staff to double click the production in the product catalog and get information on that particular production - including the promotion code and the pricing structure for that code - along with the promo word mapping with the source number.
    • We have sharepoint services and have created a promotion request form (for marketing, education, and development to request codes to be created). This can be seen by the entire company so they can glance at it to find out when a code was requested, what it entails, how it was set up, and when it was deployed. It also has a status update area so anyone can see what stage of creation this request is in.