Tessitura Training Orders vs Ticket History Ticket Reservations

Tessitura Training: Orders vs Ticket History Ticket Reservations Please answer the questions around the room! June 22, 2017 - Week 5

Phase 1: Orders v. s Ticket History Ticketing is one of the primary functions of Tessitura, and there are two main ways to see transaction data for our Constituents.

What are the main differences? FAQs: 1. Ticket History is easier to query for Lists and Extractions • Ticket History • At-A-Glance view • Historical system purchases and Tessitura purchases • Orders • Detailed view • Tessitura purchases only. May 2015 -Present 2. Orders present the same data that you would see in the Ticket Orders screen

Log into Tessitura! Live

Phase 2: Ticket Reservations Ticket orders, Reservations, Member Requests, Camp purchases, ETC!

The Ticket Order Screen has 4 Primary Tabs: • Order Details • Product Catalog • Seat Map • Quicksale • Order History

Where are we in Tessitura?

Tessitura Log Ins. . . why so many? • RAMP FAQs: • Citrix 1. Can we change the length of time before it logs me out? No, or else we’re not PCI Compliant • LIVE • TEST • SSMS (SQL) • Tessitura. Network. com 2. Can we have one log in for all? No, they’re each their own program. However, they do all use your same username. . . yay?

Password Check • Log in to: Citrix • Log in to: Test • Log in to: Live • Log in to Tessitura. Network. com

Constituents - Part 1 • Constituent Types • Constituent Searches

Phase 2: Technical (the philosophical conversation) TNEW vs. Tessitura vs. Wordfly vs. Wordpress (Sydney) Acknowledgements (Krystal) May 25, 2017 - Week 1