How do you Extend Tessitura today?

Andrew,

Here is a quintet of real life examples:

1. We created a custom representation of Fundraising data that we call Projections. This is still under development but in general it treats Contributions and Solicitations as if they were the same kind of thing. The data in T_Contributions represents realized contribution and Solicitations are un-realized Contributions that we hope to get. This was done to match a long time methodology established by Sr. Management prior to the implementation of Tessitura. This allows us to manage the conversion of solicitations into contributions. This representation of the data also handles indirect contributions that are credited to donors not just the contributions that are given on a particular account. There is no place in Tessitura to get this holistic view of a given constituents current donations and a sense of our fundraisings staff expectations for near term donations in the time frame tomorrow to 18 months from now. We are also working on a similar set of data for finance that represents Contribution Transactions and Payment schedules as if they are the same time. Realized Contribution Monies and Expected Contribution Monies on a constituent by constituent bases. This will be displayed as a SSRS report. These data views are already being used in a large number of spreadsheets around the organization using data queries in MS Excel.

2. We created a series of views and stored procedures to remove duplicate addresses from the system, export, and then re-import NCOA change of address data. This was created because the USPS mandated this data review and there was no standard process provided by the Tessitura Network to take these steps. We are looking at the standard method provided by the Tessitura Network but have not implemented at this time.

3. We created a custom constituent screen using InfoMaker to hold detailed about changes in Fundraising Campaign goals over time. This was put in the constituent custom screen because (at the time created) there was no other place in Tessitura to put this information. This screen manipulates the data stored in T_Campaign.goal_amt and really has nothing to do with individual constituents. This custom screen allows us to maintain a history of the ebb and flow of fundraising goals over the year.

4. We created a custom subscription history screen that allows us to show subscriptions despite the fact that the tickets are actual sold as single tickets (with a special group of price types) in Tessitura. Subscriptions are sold in this way because at the time of implementation the Subscription model in Tessitura could not handle the types of subscriptions we were accustomed to selling. The web site has also been developed with this method of Subscriptions in mind. Numerous reports have also been developed to support this type of subscriptions. One of the reasons we have not moved to T-Stats is that the data model that comes with T-Stats does not know how to handle subscriptions sold in this way.

5 We have created a custom web page used to monitor the status of our web site and Tessitura infrastructure. This way page is monitored by our Alerting System so we know when there are technical problems with our Tessitura System.

Here at BAM there are hundreds of other customizations we have made to the system.

--Tom

Andrew,

Here are a few examples from City Opera:

1. Custom Screen designed to hold specific data for a specific moves management system recommended to us by an outside consultant.  Basically the screen worked in conjunction with a solicitation record but contained more data (e.g. high, medium, low anticipated amounts, access, affinity etc.).  It also contained some information from a wealth screening we did.

2. Customization to the header - to display the first line or so of text from a specific research note type we call "AAA".  This could be anything super important that everyone in the company should be aware of when dealing with the constituent. 

3. A Constituent report - accessed from within a specific constituent's record - (CONSITUENTS-CONSTITUENT REPORT) that gives detailed ticket information about that one constituent for the current season only.

Dale

Greetings!

At The National Ballet of Canada we have done quite a bit of customization.  We have custom screens for sponsorship, major gifts, endowment...  Also ustom headers and reports. 

But if I had to pick the one "biggie", it would have to be tax receipts and e-receipts.  As we work under very strict Canadian tax guidelines, we have had to create entire processes to issue tax receipts.  Features include:

- the ability to issue one tax receipt at the end of the calendar year to donors who make monthly payments (as opposed to issuing 12 receipts, one each month, as we did every year until this year!)

-electronic receipts that conform to all the Canadian legal requirements.

For all that know our dear tax laws, not an easy task to accomplish!

Cheers

Selga

A few examples:

1) Contributions module - custom data line to enter Gala Auction item, either purchased or donated.  This is especially beneficial in following up with item donors in following years for another, possibly larger item/service donation.

2) Customized header for Box Office users with email address field.  In our efforts to update our database this field can hold more than the address - if the field is empty there is a "Please ask for email address"message .  If the E-Market Restriction field is flipped to No E-Marketing, this will say "Refused".  If an email sent to the constituent through TMS hardbounces the message changes to "Hardbounce- ask for Email Address"

3) Performance Sales Summary and Package Sales Report customized to count all seats in a subscription order as paid, even when only a partial payment has been made on the order.  We accept a couple of different payment plans for subscription purchases and there is an assumption that the constituent will fulfill the commitment, so we want our reporting to reflect this commitment level. 

Hi Andrew

A few examples:

1. Custom screen based on the Activities screen that allows for a drop down of performances, eligibility reason etc. This is to record people invited to our Corporate Bar before the performance. It has a report that will show people who have certain attributes along with people manually entered into this screen, to avoid needing to repeatedly enter details for people who are always entitled to entry.

2. Custom header to show the last time the data protection questions were asked. This has a rolling date behind it and therefore the date will change from blue (within range) to red (out of range) when the question was asked more than 15 months ago. This allows the Box Office staff to quickly identify when the DP question needs to be asked again.

3. A nightly job that adds the Groups constituency to anyone who has booked a group, and replaces the constituency with the Lapsed Group constituency for anyone that has not booked in the last 3 years. This allows the Groups team to direct mail people.

 

Thanks

Siobhan

1.         We have a number of Custom Screens and a suite of reports that were built for us for when we implemented Tessitura. Chuck wrote all of them I believe.

They all centre around our Members (Private Seat holders) and how we deal with their seats in relation to the seats within the Promoter manifest. We have two different sales report one that runs and looks at all the External seats and sales on them (which are on the Promoters manifest) and another which looks at all the Internal seats and all the sales on them (Private Seat holders). The Promoter only ever gets the External sales report as they cannot see any sales that have happened on privately owned seats until after the show has matured and a buyout has run. The buyout report then looks at the sales on the External and Internal and if we have sold a Members seats we 'buy' one ticket from the promoters manifest at the next base price down.It's all very complicated to explain, but we also have a custom screen in each Member's record that shows their seats for each applicable show and whether they have been resold or bought out and the dividend returned to each Member.

All of our reports have been customised so that we can run sales data either with or without the Members seats (depending on who we are giving the information to)

 

2. This is not unique to our venue, but to all UK venues - we have our own Custom Data Protection screen that pull the data protection that we are required to ask our customers.

Caryl

Hi Andrew, we have a few customised bits and pieces:

 

·         A custom screen on the productions tab to include some extra marketing information and a link to the promoters constituent record

·         A custom screen on the performance tab for the Artifax Event number, this link allows us to reconcile with our finance system

·         A custom screen on the performance tab which the ticketing department use to input limits on the number of tickets that can be sold at a specific price type

o   There is a custom scheduled procedure which end dates the price type once this limit has been reached

·         Like the rest of the UK we have a custom data protection screen

·         A custom screen which stores the information on our names seats; plaque name, row, seat, date etc

·         We have lots of custom reports and utilities, a few examples:

o   Sales reports which break down events by genre

o   Simplified sales reports for promoters

o   Data output reports for membership card mailings

o   Close batch report

o   Cleanup connection report

o   Do not merge report (puts records in a custom table so that they are not flagged as dupes)

o   Yield management report (highlights price types areas with less than a user defined percentage of seats available)

 

Gary

1.    SalesWatch

Scenario

We needed a utility that delivered live sales figures from Tessitura for all productions to various stakeholders within the organisation whether they had a log in (or the inclination to log in) to Tessitura or not. The figures must incorporate sales made by external ticket agencies where relevant and the productions presented to each user must respect the security context within Tessitura. Existing sales reports placed too heavy a toll on the system especially when being run concurrently by a large number of users in the context of a busy onsale day. Our solution had to be fast, place little load on the database and be accessible enough for the senior executive to use without the need to log in to Tessitura.

 

Solution

‘SalesWatch’. As most target users were already regular users of our intranet site, we built an HTML based report delivery system that executed various custom stored procedures acting on the Tessitura database. These were built especially to deliver critical sales information fast (we anticipated that this would be expected in a browser environment). Users can either look at the sales of a particular production at a performance level (with ‘today’s’ sales highlighted), get a production level summary within a particular season or simply look at a whole day’s sales across all productions (ranked highest to lowest). The information refreshes almost instantly whatever ‘report’ users are looking at and however many users are using this utility. Agency sales are updated automatically once a day. We receive a consistently formatted spreadsheet (via email) from our two major ticket agencies each night. We have an Outlook macro which strips out the figures, places them in a CSV file and then a stored procedure runs later in Tessitura each night which places those figures into the database)

 

2.    Administrating the School group transaction path

Scenario

Our Education department needed help to administrate the typical transaction path for school groups purchasing show tickets. For schools, we accept unpaid reservations for particular events after which we send a confirmation, an invoice, a reminder to pay (for late payers), a receipt…etc. Each stage of the transaction path needed to be recorded somewhere and confirmations / invoices / reminders sent to schools with orders at particular stages.

 

Solution

We use a Tessitura order custom field to allow the Ed dept to set an order’s status to any one of a list of values they maintain in a local table. A snapshot of order statuses is taken every two hours so that we may maintain an historical record of the transaction path per constituent (and this is viewable by the Ed dept via a constituent based custom screen). We then set up a custom report which allows the Ed dept to select a batch of orders that fit the entered parameters for a given List of schools where the order status is, say, ‘Invoiced’. Another parameter allows them to select a suitable document format (e.g. ‘Reminder to Pay’) for that group of schools. And another parameter allows the Ed dept to mass change the order status for all orders that are picked up by the report as it prints to, say, ‘Reminder Sent’.

Regards

David

Please consider the environment before printing this email.
=====This message is intended for the addressee(s) named and may contain confidential information.
If you are not the intended recipient, please delete it and notify the sender.
Views expressed in this email are those of the individual sender and are not necessarily the views of the Sydney Opera House Trust=====

 

Fri 9 November marks the start of Royal & Derngate’s Young America Season. Beyond the Horizon by Eugene O’Neill, arguably the first modern American tragedy, plays until Thu 15 October when it is joined in rep by Spring Storm by Tennessee Williams- a European Premiere and another first for Northampton. To book call the Box Office on 01604 624811 or select your seat online at www.royalandderngate.co.uk

 

The Northampton Theatres Trust LtdRegistered in England and Wales. Company Registration No. 3640915. Registered Office: Royal & Derngate, Guildhall Road, Northampton NN1 1DP

 

We have customized the ticket seller's headers.  They now include icons that easily identify: specific donor ticketing benefits, seat with information, open notification CSI. We also include: multiple On Account MOP values, the need for an e-mail address, both N1 & N2 and complete address. This allows our reps to have all the info they need on the patron without having to memorize membership levels, access the patron record to verify the most common information, which all cuts down on transaction times.

 

We have a custom screen in the constituent record that we use to record demographic information on the schools that participate in our education programs, which is going to be used to pull information for grant applications.

 

Here are a few customizations, hopefully this is what you are looking for.

Custom Package Sales Report:
We do all of our exchanges, donated seats etc. within the original super package order so we have a report that maintains the value of the package before any exchanges, donated seats etc. have happened. This is what we use to report on subscription revenue.

Lead Sheet Extract:
Custom report to pull a single row of data per constituent that details 5 years of subscription packages, last 5 performances attended and last 5 years of donation history. This is also a good report to use in verifying extraction data that deals with similar information.

Auto restrict eAddress:
lp_customer_rank automatically populates the e-market restriction to "restricted" as we have an opt-in policy for email.

Update restrictions report:
Because of our email policy and that constituent import doesn't trigger lp_customer_rank (or at least didn't last I checked) we have a report to change mail phone and e-market restrictions en masse, via a list.

Update MOD report:
Because we do short season subscriptions using the dummy performance technique we need to ensure that when we have exchanged out the dummy performances that the tickets do not print in the batch ticket printing. To do this we use a specific method of delivery. After short seasons have been printed we need to update this MOD to ensure exchanged tickets are being printed so we created a report to do that.