Ticket Orders are now attached to Accounts as well as Contacts, just like Donations are:

When you view an Account record, you'll see related lists with all the ticket orders purchased by Contacts in that Account.

Now you can report on Ticket Orders at the household level in addition to specific contacts. This change is retroactive, so you'll see this on all existing ticket orders, not just new ones.

There are two new fields on the Ticketable Event page: "'Sold Out' message" and "'No longer on sale' message." You can use these fields to specify custom text to display on your website when those conditions occur -- that is, when tickets for an event are sold out, or not on sale anymore.

(If you leave those fields blank, current behavior will remain the same -- sold out event instances, or those whose Sale End Date has past, will simply not appear on the list.)

The Patron Data Qualifier (PDQ!) is now a little smarter about finding potential contact and account matches. Here's an example.

The best match will always appear at the top of the list...

...but as you can see from the arrows above, we've loosened the criteria to look for name matches and address matches independently.

One more thing: we now look for potential Individual Account matches, not just Households. You can automatically convert the Individual to a Household right from this screen:

We've changed the way we build venues to give you more control over what your patrons see when they're picking seats. In the venue below, we used to have to build Sections Three, Four, and Five as separate sections each on their own screen, but now you can choose to group sections together so they all appear at once while still having their own names and labels.

We can't rebuild your venue for events that are already on sale, or for events that are part of subscription packages that have already been sold, but if this appeals to you just let us know and we can rebuild your venue for next season, or for upcoming standalone events. (Contact us by clicking the red button in the lefthand sidebar!)

First, all donations that come in as part of a ticket order now have their own record type:

This will make reporting easier, and also make it clear on the record that the patron's credit card has already been charged.

Second, for ALL credit card donations, we've made some changes to the workflow of credit card donation processing. (This is a change that anyone who uses this feature will definitely notice!)

When you're creating the donation record for a credit card donation, you should set the Stage as "Not Posted" instead of "Posted." Why? Because the card hasn't been processed yet, and you haven't actually collected the money -- i.e. it isn't actually "posted" yet. If you make a mistake, you'll see this error:

Just fill out the rest of the donation details and click Save as usual. Then click the Process Credit Card Transaction button and fill out the card info the same way you do now. When the credit card is processed successfully, we'll automatically change the Stage to "Posted" for you, and your new credit card donation will appear in reports and dashboards properly.

Just a name change! You won't see the "Supreme Queries" tab anymore -- look for "CRM Snapshots" instead.

We've been quietly adding to the library of training materials here in the PatronManager Help tab.

If you have questions about selling tickets, or if you have new staff members just getting started with PatronManager, this is a great place to start. You can browse through the lessons or just search for keywords at the top. We'll keep you updated as we add more lessons over the next several months.

As always, please let us know if you have questions or comments -- you can contact the PatronManager Client Administration team by clicking the red "Submit a Support Request" button in the PatronManager Help tab.

Thanks!