Hi everyone,
Hope you're all well.
Please forgive this question from a relative newcomer to TNEW, but our organisation is currently looking at how to upsell merchandise items through the TNEW platform (we're on Tessitura v15 and TNEW v7). These 'events' are setup in isolation but we want to link them to relevant performances through the purchase path. I'm wondering whether, for example, this path can flag to users who buy a concert ticket that a programme book is also available as a way to encourage sales for the latter. We'd like this to be as seamless as possible, ideally 'popping up' a purchase option for the user or navigating them to a merchandise page based on the ticket(s) purchased.
I thought this was possible in TNEW but struggling to discover how within 'native' functionality, so would love to hear from fellow TNEW users who are currently doing this
Many thanks in advance and best wishes,
Martin Perks
Box Office Systems Co-ordinator
Cheltenham Festivals (UK)
Hi Martin,
We use message only pricing rules to do this on TNEW currently (same versions as you). We add a link to the content in the message that takes the purchaser to the next performance containing the add on. It has the normal pricing rules issue of only firing once per session but to help get around this we have the link open in a new page so at least the purchaser can move back & forth if they wish to.
There is a standard TNEW customization for add on's currently, but it's being moved into standard functionality in v16 (I'm not sure if it's there now or in the 'next phase' of the road map from memory).
Jo
Hi Jo,
Thank you so much for this - I've been experimenting with it in our Test environment and works very nicely
Appreciate your coming back to me on this, and best regards,
Martin
For certain items that are directly associated with specific productions (in our case parking and dining reservations) we offer a link in TNEW's "Additional Cart Content". This doesn't jump out in quite the same way as the messaging rules, and can be a lot of work to set up, but it is persistent, doesn't count against your Pricing Rule limits (supposedly the system starts getting laggy at more than 100 concurrent rules), and we find particularly helpful when we want to present things per performance for a package sale.
Thanks for this Gawain, much appreciated. I'll explore this as an option alongside Jo Bramley's suggestion above. Thank you both so much for your input!
Nice tip Gawain Lavers! We have a few perfs that use a lot of messaging rules & this content might work better for them....I'm sure we could make them pop with a little HTML!