New features, improvements and fixes across the Back Office, WordPress, Salesforce and more.
135 updates in Improvement. Clear
It isn't uncommon to have a large number of tickets to choose from in the Box Office--especially when zoomed in or showing all tickets across all allocations.
Before, agents could easily scroll down a bit using the mouse or touchscreen--but the header at the top of the showtime would also scroll, hiding the ability to hide all allocations, filter tickets, or switch sections.
We made the header portion for that showtime remain visible--so only the tickets themselves will scroll.
The Stripe Reconciliation Report used to show amounts in the Product Totals that were post-discount. This could be confusing since the Discounts were already broken out in their own column--not great from the way accountants view reports.
Used to show the amount here after the discount was applied.
Now, in the Payout Orders table, each item's totals will show amounts before discounts are applied; if you deduct the amounts shown in the Discount column, you can compute the discounted price.
Learn more how to reconcile your payouts here.
Merchandise didn't have GL Codes like the rest of the products in the system. Now, well…they do. Woo!
Trust me, this passes as fun times for accountants.
We have extended the ability for Airtable to update existing event data in Elevent--not just be a source of one-time imported info. Now you can continue to change, update, and manage your events and event data in Airtable without creating duplicate events in Elevent.
As long as the Event Names in Airtable match Elevent, data from Airtable will update the event data in Elevent. Note that this only applies to events, not showtimes on the schedule. Those are still only imported once.
This is an opportunity to rethink what is the most efficient way for you to manage your event data--whether to consider Elevent or Airtable the ultimate source of truth. You'll want to make a firm choice so you don't run the risk of overwriting changes made in Elevent.
To make configuring members-only discounts easier, we've winnowed down the list of memberships to exclude renewals and upgrades. Now you simply need to choose the initial membership tier and any members-only discounts will automatically extend to any renewed or upgraded members.
Some clients have a high number of membership tiers as it is, so this will provide some welcome relief when creating members-only discounts.
You encounter this list when you create or edit a discount campaign, and expand the Membership Restrictions dropdown list.
Learn more about members-only discounts here.
We've released some small improvements to the WordPress Plugin:
We've always offered the option to print pass and package credentials (i.e. badges) as either seamlessly printed badges or labels you could affix to a pre-printed badge. Both contain a scannable barcode.
The label option previously used Code 128 formatted barcodes; those look a little something like this.
We have since updated those labels to print QR codes you're familiar with.
QR Codes scan more quickly and easily from camera-based scanners, like our popular iOS Elevent At The Door app, so we made this the default. There is nothing you need to do to take advantage of this change.
We've updated to the new version of Google Sign-in, where customers can choose to log in with Google instead of creating an Elevent account.
The google sign-in button will look different, and the new version does a better job informing returning customers that it both recognizes them and that they've used Google sign-in to log into Elevent (or your website, if using embedded widgets) in the past.
Rules are one of the areas where it's easy to all mixed up--especially when you use more than one at the same time. They're also one of the tools most easy to miss in the Back Office. Rules can be super powerful, especially in combination with memberships, ticket packages, and private allocations.
We've been doing a lot of work on how rules function and making them easier to manage. Ticket rules, in particular.
On the details page for each showtime, for instance, you'll now see which rule is truly limiting each customer to a max quantity of tickets.
For example, if you have a special, limited ticket, you can set the default ticket max per customer on that ticket to 10 per showtime.
On specific showtimes, you can lower the max number of tickets users can get. Visit any showtime and go to the bottom of the page, where you see when tickets go on and off sale. Change the ticket view to rules.
Here you can clearly see what the default rule is and lower it just for this showtime. The blue highlight will show you which rule is the winner--whichever is the most restrictive.
Also, don't miss the bulk rules tools in the Tools menu.
The power user's guide to ticket rules can be found here.
Advanced topic warning
Since the dawn of Elevent time, both the acquisition of a ticket package and grabbing tickets with it were nested under the same 6 or 7-digit order code. In other words, even though a customer would get a whole ticket package in one transaction and then use that package to get actual tickets in one or more separate transactions, you'd see it all in the Back Office and Box Office in one order.
Like this:
There are definitely some advantages to doing it this way--this made it quite easy to see which ticket package was used to get which tickets.
But there are trade-offs:
After careful consideration, we've decided to change the way ticket package orders are recorded. Now, using a ticket package to get tickets will create new, standalone orders and order codes with each "fulfillment" transaction. Like this:
One user's order history
You won't really notice any new features or UI…yet. But this paves the way for us to explore ways to allow ticket package holders to also buy non-package tickets at the same time or use multiple packages concurrently.
