Ticketure Onboarding

00:00: This video demonstrates how to navigate and understand the Ticketure Backend CMS,

00:04: highlighting key menu items and system

00:07: functionalities. It provides an overview of managing events, customers, reporting, and

00:12: configuration options within the platform.

00:17: A Ticketure Backend CMS or Content Management System is a space where your teams will

00:22: configure events, manage customers, do

00:24: reporting, several of those things. So

00:26: today we're going to navigate through the backend CMS so that you can see what the

00:31: menu items are and where things will be. Starting

00:39: If you are an organization that has multiple sellers or multiple locations, in this

00:44: example, you see an Austin location, a Charlotte location, and a New Orleans

00:49: location.

00:52: When you log in, you might land on this screen, which is your dashboard showing the

00:55: sellers, your global settings, and going into search in Kibana.

01:00: If you are an organization with just one seller, which is most of our organizations,

01:04: then when you first log in, you will be navigated directly into your actual seller.

01:11: So what is the difference between seller and portal? A seller is a bucket, a space

01:15: where you can configure events, manage your customers, and do reporting specific to

01:20: the events in this space.

01:23: The portal is the backbone of the system.

01:26: Many settings in the portal affect every seller and influence how things work on

01:31: the web and your POS.

01:34: And there's also a lot of API and automated reporting opportunities in that portal

01:38: area.

01:40: So

01:41: Starting here in our seller location,

01:45: you see that we navigated immediately to our orders tab. The orders tab displays

01:50: the most recent nine to ten orders in a listing.

01:54: You can also search for any order by typing into your search box up here.

01:58: This is a text field search box.

02:01: So you can type in any number of things that might be associated with a customer or

02:05: an order,

02:07: including their order number,

02:08: their customer information,

02:11: their email address.

02:14: You can also search by the last four digits of a credit card here.

02:18: But keep in mind that this is a text field, and therefore it doesn't know necessarily

02:22: that you are looking for a credit card. And because of that, if the credit card ends

02:26: in, say, 4242,

02:29: it might bring up an address or a phone number that may also have that associated

02:33: with it.

02:35: But a pretty powerful search functionality here on this page.

02:40: You can also see that we have showing orders.

02:42: These are paid orders where tickets have been issued.

02:46: Then we can navigate to our held carts area.

02:49: This is any sort of held tickets or orders, maybe for group sales where you have

02:53: created a cart for them and they will pay over time or pay later.

02:56: You can also create orders directly from this screen.

02:59: Most of the time, organizations,

03:03: Group sales and membership teams will navigate and manage orders and customers from

03:07: the CMS rather than using our frontline POS app.

03:12: Moving on down to the next menu,

03:13: you have your events area.

03:14: This is where you will configure and manage your events.

03:17: As you can see,

03:18: there are a number of search features and a create event button.

03:23: All the big pieces of

03:24: this will be covered in more detail in future trainings.

03:29: You also have your customers tab.

03:31: This tab is where you can search for and manage your customers or organization

03:35: accounts.

03:38: Here, you will also be able to see if somebody is a member, what membership level

03:43: they are, and what their membership status is.

03:47: If you sell gift cards in the gift card menu, you will be able to identify and

03:51: search for gift cards by number or by person.

03:55: You can see balances and the associated purchaser in this area.

03:59: This reports tab is our basic standard Ticketure reports.

04:03: Here you can see that we have them broken into three tabs: your sales reports, your

04:08: redemption reports, and your financial reports.

04:12: In here, you can do a basic search by transaction date, filter by events, and change

04:17: your dates.

04:17: With all of these reports, you can also export them as a CSV.

04:22: Moving down, our next menu item is cash boxes.

04:25: This is a way to assign physical names to your cash boxes or cash bags so that you

04:30: can keep an accounting of cash throughout your day.

04:33: If you are not using cash, then you don't need this space.

04:36: But if you are taking cash, you will need to set up cash boxes to sell and utilize

04:40: that payment method through your POS.

04:42: The next menu down is checkout rules. This

04:44: also houses our message rules. These are rules

04:49: And promotions that you might set up for your events.

04:51: So your cart rules might be things like you have to have an adult in your cart to

04:56: have a child ticket in your cart.

04:59: Codes paired with rules are discounts. You have a code for 50% off, and then you

05:05: create a cart rule that designates what items are available for that 50% off

05:09: promotion.

05:11: And then the last one here is your message rules.

05:13: These are messages that can be configured to show online to your e-commerce guests

05:17: based on rules.

05:18: Based on the day of the week they choose, based on how many tickets they have in

05:22: their cart.

05:22: Lots of options for configuring different messages to your guests online.

05:28: And then the last thing here in your seller area is the seller configuration space.

05:32: A couple of these are items that only live in your seller, which I am going to go

05:36: through first.

05:36: Then there are a few items that you will also see in both your seller area and in

05:41: your portal settings.

05:44: So starting off at the top, we have our CSR app. This is the feature that controls

05:48: your use of your POS device.

05:52: As you can see here, there are checkboxes for scan, search, sell, and attendee list.

05:57: If you are an organization that doesn't sell on-site, maybe you send everyone to e-commerce

06:01: instead of selling on-site, but you do scan, you want to search for orders, you do

06:06: want to see your attendee list, then you would want to check those boxes.

06:11: Of course, if you are selling on site, you would also want to enable that box.

06:17: Here you also have a space to add a header image for your printed receipts and any

06:20: sort of header copy.

06:21: So this might be all sales are final terms and conditions or an upsell to

06:26: membership, something like that.

06:27: So a nice little text space for that.

06:31: Jumping down under the configuration tab.

06:34: This is where you can identify what this seller's membership event ID is.

06:40: That helps with e-commerce to direct people to your primary membership event for this

06:44: seller.

06:47: Then you also have your checkout donation ticket group ID.

06:51: This enables the donation at checkout functionality.

06:55: which we will go through in future training sessions on donations.

06:58: Moving down to sales points.

07:01: The idea with sales points is to help identify the physical location of your POS

07:05: devices while your staff is using them.

07:07: The way I like to explain this is, maybe you have a north entrance

07:12: and a south entrance,

07:13: and someone logging in for the day is also going to be working at that north

07:17: entrance. When they log into the POS device, they're able to select that north entrance.

07:22: With that,

07:23: you're able to not only track that staff member's movements throughout the day,

07:27: what they have sold, what if they refunded, etc., but also what location they were at

07:32: during that day. The last thing here on this menu is price libraries.

07:36: This is Ticketer's dynamic pricing tool. Here you can create schedules and dynamic

07:41: pricing for your events.

07:43: So the two items that I skipped, email templates and seller fees,

07:49: these are the two items that exist both here in your seller space as well as in your

07:53: portal space.

07:54: So we'll talk about those in depth in both areas.

07:58: Here in your seller space,

07:59: email templates can be configured for a number of things.

08:05: If you sell memberships, donations, gift cards, or gift of membership,

08:09: all of those are additional email templates

08:12: configured here at your seller level.

08:15: The email template configuration trainings will be later in our course.

08:22: You can have multiple templates here, as well as some standard ones at your portal

08:26: level.

08:27: Right now, you can have up to 100 email templates in this listing.

08:31: After that, you'll want to archive or use logic within them to configure additional

08:36: ones.

08:36: You'll learn more about that in our email training.

08:42: Then you have seller fees.

08:44: In Ticketer, you have the opportunity to create different fee sets to apply to your tickets.

08:48: tickets.

08:49: We'll talk more about how those get applied and configured later.

08:56: Here in your seller,

08:56: you can add any number of additional fee sets that you might need for your price

09:01: configurations.

09:05: Here at the bottom of our screen, you will see a gear icon.

09:09: This takes us into our portal settings, which I will do here in a moment.

09:12: The next one over is a systems issues alert.

09:15: This would be any issue or concern you might have in your system.

09:19: For instance, maybe we set up an automated email report for you and for some reason

09:24: that email failed. This would give you a report or notification that those items

09:29: were failing

09:30: so we could help you or you can fix those issues. When you log in, you would also see

09:35: a pop-up on your screen with any systems issues you might have.

09:39: The next item over is to access Kibana. Kibana is our integrated third party data

09:44: analysis tool,

09:45: so we'll get into those trainings later.

09:48: You also have search here.

09:50: This is a high level search that allows you to search between customers, search

09:54: between sellers, and search all sites and all the orders.

10:01: You then have the help menu.

10:02: This takes you into the Ticketure support hub where you can access any support tickets

10:07: you

10:07: have submitted and also access all of our knowledge base support articles. The

10:11: last item here is your log out button. This

10:14: will log you out. The

10:15: last thing to notice here is, as you can see, there are little drop downs and little

10:20: carets. If you're working on a small screen, one

10:23: thing I like to identify here is this little toggle so you can have a wider view.

10:27: You'll

10:27: see a lot of those throughout the system.

10:33: All right, moving into our portal

10:35: settings. As I mentioned, there are some things here that are going to be part of your seller.

10:39: I'm going to jump to those first since we just spoke about them.

10:42: The first one is email templates.

10:44: We do have a couple of standard default templates here at your portal level.

10:48: These can all be configured with conditional logic.

10:51: You could just use these email templates and not have additional ones.

10:55: But if you have any special events or things like membership donation, then we will

10:59: want to have additional email templates at that seller level. Here,

11:03: you're going to see your standard ticket order.

11:05: This is for any orders purchased. You have your cart, sometimes referred to as the

11:10: invoice.

11:10: This is associated with those held carts so that you can send an invoice for payment.

11:14: The

11:15: last one here is your password reset. This

11:17: is for your members logging in or for your customers logging in through the my account

11:22: portal.

11:24: Down a little bit,

11:24: we also see that the fees area is going to be your default fee set.

11:31: As I mentioned, we can set a number of fee sets so that you can be granular with how

11:35: you apply fees to your event configuration.

11:41: This one here at the portal

11:42: level is going to be your default.

11:46: If you do not add a fee set, or if you want to just zero dollar, or maybe you have a

11:50: specific sales tax that has to be applied to all of your orders,

11:54: then you can utilize this fee set here.

11:58: All right, jumping back up,

11:59: there are a number of things in your portal settings that you as the client have

12:02: full control to edit, change, and manage.

12:04: So I'm going to go through those items first.

12:08: Along with those, there are a few things at your portal level that the Ticketure team

12:12: needs to configure for you. So

12:13: I'll go through those items second.

12:17: Starting off here at the top with what the client can configure on their own is

12:21: custom content.

12:23: In this custom content menu, you'll find many language items that control your

12:27: e-commerce system.

12:30: Ticketer has many default language items within your e-commerce flow, such as what a

12:34: button says. As you can see, this is ad.

12:38: Button language,

12:41: page header language,

12:43: and a lot of membership language throughout this space. It's a long list of options

12:47: for you to change.

12:49: As we go through implementation, we will help identify areas where you might want to

12:53: make changes.

12:55: Two things I like to point out here.

12:58: The first is your footer.

13:00: Your e-commerce

13:01: footer has a space for you to configure what you want there.

13:03: This is in custom content.

13:05: The other is the terms and conditions language.

13:07: As you can see, I'm typing keywords in our search. We have terms and conditions

13:12: options here, which help control that language at checkout.

13:18: And we'll go into more detail on that in a future training.

13:22: Jumping down,

13:23: you also have staff management.

13:24: This is where you can configure your staff permission groups.

13:28: These are the permissions that your staff members can have throughout the system, as

13:32: well as adding your staff members.

13:35: Your Stripe accounts will get configured in your production environment.

13:38: So how do you know if you're in your production environment versus your test

13:42: environment?

13:44: You can see that at the top in your URL.

13:47: As you can see here, we are using Ticketure test in that URL.

13:51: You might also see something that says D1 ticks.

13:54: We have a couple of different servers, so it depends on which server you're in.

14:00: In your testing accounts, you will be connected to the Ticketure test Stripe account,

14:04: account.

14:05: which allows us to make test purchases using a dummy payment method.

14:10: You will configure your Stripe account directly in your production or live

14:14: environment.

14:16: And we do have a future training coming up on that.

14:19: Moving down into payments,

14:20: this is a combination of something

14:22: Ticketure needs to configure for you,

14:24: and something you can also configure.

14:28: Here we have a number of default payment methods already in the system.

14:32: Ticketure calls these gateways.

14:33: As you

14:35: learn the system, you'll see the word gateway, which means the payment method. To add

14:40: a gateway, you need to submit a support ticket or work with your implementation team

14:43: to add your payment methods. You can

14:47: edit any GL code or accounting code associated with those payment methods.

14:53: To do that,

14:53: you can hit the three dots on the right-hand side, hit edit, and then type in that accounting

14:58: code here.

15:01: As I mentioned, adding more payment methods is something your team would need to

15:05: help with.

15:08: Some examples might be a PO if you're dealing with schools or purchase orders, stock

15:13: transfer for donations or memberships.

15:17: You might have various outside payment methods that you handle,

15:21: and you need to complete an order in the TicketJuris system identifying

15:24: those orders paid with something other than a credit card or gift card.

15:29: Moving down into channels. Channels is where something was sold. Here we have the

15:34: CMS, which is what we're looking at

15:35: now. You have your kiosk, your POS, and web.

15:39: Each of these, adding channels is something that Ticketure would do for you, but you can

15:43: edit the cart timer associated with those channels.

15:47: For instance, with the web, it defaults to a 15-minute timer.

15:52: This means a person can put something in their cart, and there will be a timer

15:55: countdown of 15 minutes that notifies them their cart might be released.

16:00: After 15 minutes, those tickets will be released back into the inventory.

16:04: You can edit the timer for each channel by clicking on the three dots, hitting edit,

16:09: and making adjustments within this duration and the units.

16:14: All

16:14: right, moving on down into our seller space.

16:18: As I mentioned, if you're an organization with multiple locations, or you have

16:22: partnerships with other organizations that you manage ticketing for, that is the

16:27: opportunity to have multiple sellers.

16:30: You are working under the same umbrella,

16:33: but you have separate buckets of configuration creation items within what we call a

16:38: tenant within that primary space.

16:42: Most of you will likely only ever use one seller, but you have the opportunity to

16:46: create additional sellers in this space.

16:50: You also have the ability to edit and add metadata to the sellers.

16:55: You'll have a training coming up with more information on those items.

17:01: Venues are configured here in your portal settings. Just click the Create Venue

17:06: button.

17:07: We have a training coming up that goes into detail on creating venues.

17:13: The next menu item down is Assets Upload.

17:16: What this does is it allows you to upload images into your system so that you can

17:20: generate a URL for those images and utilize that within some HTML configuration

17:27: throughout your system, in description spaces, etc.

17:33: We'll talk about that in a future training.

17:37: Those are the primary menu items where you as the client will be able to manage

17:41: configuration.

17:44: Going down again, that's custom content, email templates, staff management, Stripe

17:50: in your production environment,

17:51: payment accounting codes,

17:54: basic default fees, your channel cart timers, your sellers and seller

17:58: configuration, your venues, and your assets upload.

18:03: So now what are the items that Ticketure must configure for you?

18:09: The first item here is your membership programs.

18:13: In Ticketure, we have to configure your membership programs and your membership events

18:17: for you.

18:18: There are many backbone connections that need to be in place for memberships to

18:22: function properly.

18:23: So we will do those configurations for you.

18:27: There's a lot of training videos coming up on membership so that you can understand

18:31: how all of that works.

18:33: And also note that there are a lot of things within the membership event build that

18:37: you can control, such as images and descriptions.

18:42: You can also change pricing.

18:43: If today you have a certain price and down the road you want to increase or

18:47: decrease that price, you have full control over those pieces.

18:51: Automated tasks is going to be the space where automated tasks are configured, such

18:55: as webhooks or the Salesforce API connections.

19:00: There are also automated reports that will be configured here, as well as auto

19:04: renew for memberships.

19:07: All of those items are things that the Ticketure team will configure for you with your

19:10: assistance.

19:12: In this configuration menu, there are many items. This is one of the major backbone

19:17: areas of the system where various configurations can be updated to affect your

19:21: system's functionality.

19:22: You, as a client, have some control over these configuration items.

19:26: If you see either the three dots or the Add button, it means you can configure and

19:32: change that item.

19:34: If you see it is configured but only a View button is available, you cannot edit it

19:38: and would need to contact Ticketure to make changes.

19:44: The last one

19:45: here is your API applications.

19:49: Any API integration with Ticketure will be housed in this section.

19:57: So this is something that you as a client don't really need to worry about

19:59: configuring. You're going to work with the Ticketure team to accommodate that.

20:04: Great.

20:06: Now I'm going to navigate into Kibana.

20:10: If we click into that Kibana space here, you'll notice that our Elastic Search

20:14: is loading. Within

20:16: here, you can see all of our standard visualizations.

20:19: The visualizations are like reports.

20:23: Each of these is prebuilt in your system.

20:27: From here, you can navigate into additional pieces of Kibana. You can go into

20:30: dashboards, which we will heavily utilize and discuss in our reporting training.

20:36: This is the opportunity to put several different visualizations or reports onto one

20:41: dashboard so that you can see them all in one space.

20:46: You can also create maps.

20:47: So this would be like a heat map,

20:49: trying to see where all of your customers'

20:51: zip codes are.

20:55: And then you also have Discover here.

20:57: What Discover does is it gives you a much higher-level reporting tool that can have a

21:02: lot of really intricate ins and outs.

21:07: We do have team members on the Ticketure team who can help you with any of these types

21:11: of custom reports in the Discover space.

21:21: The video covers Ticketure CMS navigation, seller and portal differences, order

21:25: management, event setup, customer

21:28: handling, reporting, payment gateways, and system configuration features.

00:00: This video demonstrates how to create and manage venues within your portal,

00:03: emphasizing the importance of venue setup before adding events. It covers required fields,

00:08: digital wallet integration, and reserved seating map submission to streamline

00:13: event management.

00:15: This video is going to show you how to create and manage your venues.

00:19: Please note that you must have a venue created first before you can create and add

00:24: any events in your system. To navigate to your venue space, go to your portal

00:28: configurations. You need portal admin level permissions to add and change venues.

00:33: If you are within your seller, click the gear icon in the lower left-hand column.

00:37: If you are in your dashboard, you will see the venues option under your global

00:41: settings.

00:42: I'm going to click on that. In our venue space, we currently have no venues.

00:46: I'm going to click create venue. Since I am located in New Orleans,

00:51: I will use our great City Park as an example. We're going to call this New Orleans

00:57: City Park

01:03: That's going to be the name of our venue.

01:04: Note that all of these spaces with a red asterisk are required for creating a venue.

01:10: Several of these will come into your digital wallet.

01:14: So that's the Apple and Google wallet,

01:16: the ability to add those tickets and passes to your digital mobile phone.

01:25: The things that will appear in those digital wallets are the venue name, the venue

01:29: address, the email, the phone number, and the website.

01:35: The image and the description are internal for your space.

01:40: The latitude and longitude are required for use of Google and Apple digital wallets.

01:46: And then, of course, the country and the time zone will help drive those past

01:50: reminders that you would get on your phone,

01:51: just like if you have an airline ticket, it gives you that reminder.

01:56: That's what these things over here are for.

02:00: I'm going to go ahead and add our address for City Park. Note that if you want to

02:04: pull in a venue name or a venue address to your email confirmations, the way those

02:08: pull in will be directly related to how they are typed in here.

02:14: For instance, if I have a one-line address, and I pull that into any email template,

02:18: it will pull it in as a one-line address.

02:22: If I want that to be formatted as a two-line address here in this venue space, you

02:27: will need to create that line break.

02:30: All right, I'm going to say that we are in the United States and that the time zone

02:34: is America Chicago.

02:37: There we go.

02:37: Latitude and longitude.

02:39: One thing I like to do for latitude and longitude is go to Google Maps and find what

02:43: I'm looking for. Here,

02:44: I'm going to look for City Park New Orleans address.

02:47: I'll click on Maps. You'll see it brings up City Park.

02:50: I'll right-click on that. The

02:51: top number here

02:52: is your latitude and longitude. If you click on that, it copies it.

02:57: Then what I usually do is paste that into a text file so I can easily copy and

03:01: paste each one.

03:03: The first number is the latitude.

03:05: As you see, we're going to type that in with the full number.

03:08: The system will tell us we need to shrink that down to the nearest valid value.

03:12: It will give you the top and bottom range of that.

03:14: I'm going to use that first range.

03:19: Now I'm going to paste our longitude here, and it will do the same thing.

03:22: So I'm going to copy this first number and add that in.

03:25: So now we have our latitude and longitude for City Park. These other items that you

03:29: see here, phone, email address,

03:33: website,

03:33: those are all things that will appear on the backside of the digital wallet.

03:37: As you can see, phone and website are not necessarily required, but they are good to

03:41: have. An email address is required. The Apple and Google systems require you to have

03:46: some method for your guests to contact you for customer service.

03:50: That email address is required here.

03:53: As you can see, the description is not required.

03:55: The venue is not required.

03:57: These are internal pieces just to make navigating for your staff a little easier.

04:03: I'm going to go ahead and save that venue.

04:05: Now you can see we have that venue here.

04:07: If I had added an image, you would see that right there.

04:11: Let's say I have an event where I want to add a reserved seating map.

04:14: Maybe it's a gala or something like that.

04:17: With that, there is a process where you can submit your seated map to the Ticketure

04:21: team.

04:24: We will then add that map as an image.

04:29: When you come back into your venue here, you will see that seated map down here.

04:36: We can have multiple maps for each venue.

04:40: If you need assistance with a reserved seating event, please reach out to your

04:44: Ticketure team at support@Ticketure.com.

04:52: We'll be able to assist you with adding that map.

04:56: Now that I have my venue created, I can proceed with creating events from that

05:00: venue.

05:03: We'll go into event configuration in more detail in the next couple of videos.

05:10: But here, just to give you a quick example, if I click on events and then create

05:14: events,

05:14: the first question I'm asked is what venue I am using for this event.

05:21: So I'm going to go ahead and choose New Orleans City Park.

05:24: Learn to set up venues with required details, integrate digital wallet

05:28: info, submit seating maps, and prepare venues for event creation in your portal

05:33: system.

00:00: This video demonstrates how to set up and configure sellers within the Ticketure platform,

00:04: including managing seller-specific settings and metadata. It covers

00:07: key features such as adding images, setting time zones, and customizing e-commerce URLs

00:13: for multiple sellers.

00:18: This training will navigate through what a seller is, how to configure one, how to

00:22: add your image, and how to affect any of the metadata that might appear or be

00:26: associated with your seller.

00:28: So starting off again, when you log in, if you are a new client or you only have one

00:32: seller associated with your account, you will land within your seller space.

00:36: So as you can see here, we are within the Ticketure demo aquarium seller. If

00:41: you have multiple sellers, then you would instead land here on the dashboard and you

00:45: would be able to select the appropriate seller that you need to access here. So

00:48: again, the difference between portal and seller is portal is that high-level configuration space

00:53: where the changes you make there will affect everything in your system.

00:57: So if

00:57: you are an organization with multiple locations, anything you affect here within those

01:01: global portal settings will affect every seller. They will apply to every seller,

01:06: whereas the things you configure within your seller space only affect that particular seller.

01:11: that particular seller.

01:13: So creating sellers and adding sellers. You can create one here

01:17: if you are on your dashboard; there is a create button directly here.

01:22: Instead, I will navigate into our portal settings to show you where this lives

01:25: within that space.

01:28: From here, I can click on sellers under global settings.

01:32: Now I want to show you how to navigate to this menu if you are a single seller

01:36: organization and you are within your seller.

01:40: Here we are back within our seller and I'm going to click the gear icon for

01:44: settings.

01:47: Then I'm going to scroll down a little and select that sellers menu.

01:51: Those are the two ways you can navigate to the Create Seller and Manage Seller

01:55: space.

01:57: When you're in here, as you can see, we have several sellers that are already set up

02:01: in this demo space.

02:04: You have three buttons over here that allow you to edit that seller or change and

02:08: affect the metadata associated with the seller.

02:12: And then up here, you have a button for creating a seller.

02:15: So what I'm going to do is pop into one of these sellers that's already active to

02:19: show you how it is configured and what pieces are required and important when you

02:23: add a new one.

02:26: Starting off here, we have the seller name.

02:28: One important thing to note about the name is that if you are using Google and Apple

02:32: digital wallets, which allow someone to add their tickets or passes to their mobile

02:36: phone or mobile wallet, this seller name will appear on those digital wallet tickets

02:41: or passes.

02:41: So you want to make sure that this is appropriate for your organization because it

02:45: will be customer facing to some degree.

02:50: You also have the time zone for this seller.

02:53: If you are an organization with multiple locations, each seller can have its own

02:57: specific time zone so that you're working directly

03:02: in accordance with that time zone.

03:04: Then you have your seller image. If you do not have one when you are a new client and

03:08: first start, your seller might look like this without an image.

03:11: The image required in this space needs to be 660 pixels by 660 pixels,

03:18: generally at 72 DPI if you are creating it. You can add that image by clicking the

03:23: button, which will open the option to upload an image in that space.

03:26: The image is required for your digital wallets.

03:31: In your digital wallets, there will be a small logo icon at the top, which pulls from

03:36: your seller image.

03:36: It is very important to have an image here.

03:42: All right, going on this

03:43: side, the first thing you're seeing here is seller

03:45: slug. So what does that mean? This is a piece of the URL that you will see when

03:50: you're navigating your e-commerce. If you are an organization with only one seller,

03:55: then you probably will not see this in your e-commerce link because everything is

03:59: within the same seller space.

04:02: But if you are an organization that has multiple Stripe accounts and multiple

04:05: sellers, then you may need to utilize your seller slug.

04:08: If we look here at an event, this is an event under our demo account for timed entry

04:13: admission.

04:15: As you can see up here at the top, the seller name of aquarium is listed here after

04:19: the primary domain.

04:20: This is your ticketing subdomain,

04:22: whatever you have selected through your implementation. Then this is where that

04:26: seller slug

04:29: is assigned. What

04:29: that does is it allows your guests to navigate within your e-commerce site only

04:34: within that seller. That way, you can keep them all functioning

04:38: and buying within that same seller space without seeing everything else from other

04:42: sellers within your environment.

04:44: And then the last thing here is your default ticket template.

04:47: As we've discussed in previous trainings, you have a portal level email template.

04:50: This is what we generally identify as your default, or as you can see here, use

04:55: portal default.

04:56: That's your default email template.

04:58: But in each seller, you have the opportunity to create additional email templates

05:02: and assign a new default to this seller. For instance,

05:05: if we wanted, I don't see an aquarium one here, but if we wanted to say that the

05:09: virtual template is our standard default for the aquarium seller, then you can save

05:14: that. That way, when you're creating events within that seller space, you can say you're

05:19: using the default because the default is already assigned up here at your seller level.

05:22: seller level.

05:26: From here,

05:26: I can also navigate into metadata.

05:29: As I showed you before, you can click those three dots and click Metadata.

05:33: You can also click that from up here.

05:35: I'm going to do that now.

05:38: As you can see, there's already a number of metadata configured in this space.

05:42: We have several helpful articles that describe different things you can do with

05:46: seller level metadata.

05:48: A couple of things you might see are this completed image.

05:51: This metadata allows you to have an image on your completed order page.

05:55: When a customer completes their purchase, they come to a page that says done. Here's

06:00: your confirmation number. In that space, you can add an image.

06:04: This metadata allows you to do that.

06:08: Additionally, you could change your confirmation page logo.

06:14: You can change an image.

06:15: There's also metadata for your Apple wallet design that you'll utilize seller

06:19: metadata for.

06:20: We have many help articles for that, and those will be linked into your

06:24: implementation plan.

06:25: And if you go into the Ticketure support hub and search for metadata, then you will be

06:29: able to see all the places where metadata is associated.

06:33: Learn to create and manage sellers, configure metadata, and customize settings like

06:38: images and time zones to optimize your Ticketure seller profiles.

00:00: This video demonstrates how to configure event categories within the portal to

00:03: improve event organization and guest navigation.

00:06: It also explains the role of these categories in reporting and e-commerce flow

00:11: management.

00:14: In this video, we are going to explore some of the portal level configurations that

00:18: affect how you configure your events.

00:21: Some of these are things that the Ticketure team has to do for you, and others are things

00:25: that your team can enable and affect.

00:27: So the first thing I'm going to review is what we call event categories.

00:32: When you start creating an event, the first two questions it will ask are what is

00:36: your venue and what is your event category?

00:47: So as you can see here in our basic event setup, there are two categories that are

00:51: automatically populated, events and admission.

00:54: Well, what do these do?

00:57: The primary function for event categories is to group events together by their type

01:01: so that when you go to your e-commerce navigation,

01:06: your guests are able to see them all together in one space.

01:08: So what does that look like?

01:11: If I go into our Ticketure demo account into the aquarium seller, you can see a number

01:15: of buttons up here at the top. These

01:17: are our event categories. So

01:19: if I click on admission, it's going to navigate me to the list of just the admission

01:23: events versus movie or membership, gift cards and donation. So

01:27: your categories can be whatever you want them to be, whatever

01:30: is going to make the most sense to your guests and your customers to navigate

01:34: your sales platform.

01:37: Some suggestions that our organizations have used are special events, tours,

01:42: merchandise, or add-ons. Think about how you might want to group events and sales

01:47: items together

01:47: so it makes it easy for your guests to navigate.

01:53: Along with this, you can also utilize categories in what we call next route.

01:58: We've got a training video about next route that you'll see coming up.

02:04: A simple explanation of what next route does is it can, on e-commerce, move your

02:08: guest from one event to another event or, in this situation with categories, move

02:13: them to a category.

02:18: For instance, if you have admission events and after the admission events you want

02:22: them to see the add-on events, then we could next route them directly to that

02:26: category.

02:29: It would give the listing of all the public facing events that are for add-ons.

02:35: The other way that event categories are utilized in our system is in your Kibana

02:38: reporting.

02:39: So event categories make it really easy to create Kibana reports and to filter

02:44: Kibana reports based on what you're looking for.

02:46: For instance, if you want to report on all of your admission events, instead of

02:50: picking every single event, you can just say, I'm looking at the event category

02:55: admission.

02:57: One thing to note is that you'll hear me say over and over again, especially as we

03:00: go into event configuration, that everything in the TicketJour system is configured

03:04: as a quote unquote event, even things like merchandise or non-dated

03:09: items such as gift cards, memberships, donations.

03:13: In our system, you will notice that they all start out as being configured as what

03:17: we call an event,

03:18: and then from there that configuration informs how it performs, whether it's dated

03:23: timed entry or non-dated such as merchandise.

03:27: So for event categories, those are configured in your portal settings.

03:32: I'm going to go to our gear icon here under configuration.

03:36: So this is what we call portal level configuration.

03:41: Some of these things are items that the Ticketure team has to configure for you.

03:45: If you see the three dots or the add button, that means it's something you can

03:49: configure. But if you don't see those, it means Ticketure must configure it for you.

03:54: Event categories is one of those items that Ticketure must configure. For

03:58: instance, if I go into event categories, you'll see our default predefined categories

04:03: of events and admission.

04:05: I'm going to add a few add-ons, tours, and special events.

04:14: And let's say I have an organization that also sells membership, donations, and gift

04:18: cards.

04:21: Those are three categories that cannot be named anything else at this time.

04:25: So if, for instance, you sell annual passes, but those in Ticketure are

04:29: considered memberships,

04:32: then the category for those still has to be membership because of the way that the

04:36: Ticketure system works and how that ties into everything.

04:40: The other one is donation, so you have donation, and then you also have gift cards.

04:44: Gift cards will have an "s" on the end. If you call yours vouchers or gift vouchers, in

04:50: the Ticketure system that category will have to be gift cards.

04:54: So I'm going to go ahead and save that there.

04:57: All right, now that we have seen our event categories and started to configure

05:00: those,

05:02: in our next video we will explore some items that you as the client have the

05:06: ability to configure in portal settings.

05:11: Those are creating standard lists for event items such as the GL code listing, your

05:15: ticket groups, and your ticket type names.

05:18: Learn how to set up and customize event categories, understand their impact on

05:22: guest navigation, and explore portal-level

05:25: configuration options for better event management.

00:00: This video demonstrates how to configure event-related lists such as GL codes, ticket

00:04: groups, and ticket types to ensure data consistency and streamlined event setup.

00:09: It

00:10: highlights the benefits of using standardized lists to improve accuracy and simplify

00:15: ticket configuration workflows.

00:23: The other items that affect your event configuration are a listing system.

00:28: So we have three primary spaces where you can create a list.

00:31: The first one is your GL codes.

00:33: So as you can see, I typed in GL and we have standard GL codes here.

00:38: If I hit add, you're going to notice that this is just a block of space where you

00:42: can type in different line items.

00:46: And here, once you add a list into your system, it will then change that in your

00:50: event configuration.

00:52: So the three places that we have list items in event configuration are those GL

00:57: codes.

00:59: We also have ticket group names and ticket type names.

01:03: What is a ticket group?

01:05: A ticket group is a group of permissions that control a set of ticket types.

01:10: So for instance, if you have group tickets, like group sales tickets, and you have to

01:15: have a minimum of 15 to get those prices, you would first create a ticket group that

01:19: defines the minimum of 15.

01:23: Then you would add a ticket type for the actual ticket

01:25: price, maybe group adult, group child, et

01:30: cetera. That's how these two things work together.

01:33: The significance of adding a standard list is that it helps with typing. Your teams,

01:38: as they're configuring, have the ability to select from a dropdown rather than typing

01:43: it in and possibly misspelling it

01:45: or, in the case of our accounting codes, typing in a wrong number. This helps with

01:50: data integrity because it will always be the same spelling, the same numbers, and so

01:55: on.

01:56: So let's see this in action.

01:59: When you create an event, we will cover the full event creation in future

02:03: trainings.

02:04: To show you how these lists work,

02:06: I've started with a basic event here.

02:12: You can see that we have our ticket group.

02:17: This line controls the permissions and the rules associated with these ticket types.

02:21: Here, you have general admission as your ticket group and adult as your ticket type.

02:29: If I go in to edit this ticket group, you can see that right now it is just a

02:34: free type space. It does not have a list against it.

02:38: If you use the standard ticket group list, you will have a dropdown here that your

02:43: staff can select from when configuring their ticket groups. This is beneficial to

02:47: avoid any misspelling.

02:51: When you have a list against an item, it is a list field, which means it cannot be

02:55: typed over. If you add many things to this list and then create a new event needing a

03:00: newly named ticket group,

03:01: you should add that name to the list

03:03: first before adding the new ticket group with the new name.

03:07: We also have our ticket types.

03:08: So here you can see that

03:09: this is an adult ticket type for $20.

03:14: If I hit edit on that, you will see that there is no list associated with this

03:18: ticket. I have the ability to just free type that in versus selecting it from a

03:22: list.

03:24: And then as you scroll down, you're going to see your accounting area down here.

03:28: So as you can see, now we have our GL code, with a recognized code and a deferred

03:32: code.

03:33: There is also a project code here.

03:34: What that does is, the way I like to explain it is, let's say you have a donation

03:40: event and there's a primary accounting code or deferred code for that donation

03:44: event,

03:44: but it goes to a specific campaign or a specific appeal. And that project code can

03:49: give you a little more granular reporting opportunity there so that you're able to

03:53: identify exactly where that money is going to go.

03:56: So as you can see here,

03:58: again, we don't have a list against that yet.

04:02: And it allows us to free type into both of those spaces.

04:06: So I'm going to add a few items to our list.

04:10: I'm going back into our portal settings, into configuration.

04:13: The first one I'll start with is our GL code. If I type in GL or standard GL codes,

04:19: it brings up this item right here.

04:20: You should see this add button because you can add, enable, change, and affect all

04:25: through your time with Tickature.

04:29: I'll click add here.

04:30: As you can see, it's just a blank box.

04:32: The way to add your GL codes is one at a time, line by line.

04:38: You can have up to 65 characters in one string.

04:43: And that is important because when you use a GL code list, you have to put the GL

04:47: code and the recognized and the deferred numbers and project codes all in one string

04:52: of numbers and letters.

04:55: The way you format that defines to the system

04:58: what is recognized and what is deferred.

05:01: For instance, with our previous example,

05:05: My recognized GL code was this number:

05:07: 1-245-252. Then I

05:13: had a project code of 320. I separate

05:16: those with a colon. Now I'm

05:18: going to put that 320 right there. That's my

05:22: recognized GL code. Now I

05:27: want to add my deferred GL code. I'll use

05:31: the pipe symbol, the straight up and down line above

05:34: the enter key on your keyboard.

05:37: And then I'm going to put in my deferred number.

05:40: So again, no spaces,

05:41: as you can see here,

05:44: we're using dashes and colons.

05:47: So now with my deferred number, that's 2-245252.

05:56: And again, I'm putting in that project code of 320.

05:58: Now you can see we have a full string of numbers and that pipe symbol that separates

06:04: our recognized versus our deferred.

06:06: Sometimes organizations ask if we could have letters in here, and the answer is

06:10: yes,

06:11: absolutely.

06:12: So let's say this is a membership or a general admission. You could put GA dash, and

06:18: that way you have the recognition at the beginning that these are for your general

06:21: admission tickets. You can include any numbers and letters here

06:25: as long as you keep the format, understanding that the colon separates your primary

06:29: GL from the project code, and the pipe separates your recognized from your deferred

06:34: numbers.

06:39: I'm just going to leave this one in here as well.

06:41: One practice I like to do is adding one at the beginning that says none selected.

06:46: That way, as your teams configure and see this none selected, and you see it in

06:51: reports,

06:51: you know there is a ticket type that might need the proper GL code selected.

06:55: I'm going to save that

06:56: now. Now I'm going to go to my standard ticket type or ticket group name. That is

07:01: the grouping of rules.

07:04: And permissions over a certain set of ticket types.

07:07: We know we want a general admission, maybe we have groups, and maybe we have field

07:12: trips.

07:14: You can have any number of them.

07:16: I believe the limit is still 65 characters, but you can continue to create your list

07:21: as you need it.

07:23: And now I'm going to add some ticket type names.

07:27: So here we are again with our standard ticket type names.

07:29: I'm going to add adult, 12 plus.

07:35: Then child, 2 to 12 years.

07:40: Then senior, 65 plus.

07:43: Then military ticket

07:45: type. Here

07:46: we are adding these based on how we want them displayed to our guests.

07:49: I'm going to save that now.

07:53: All right, I'm going to go back into our event configuration here.

07:56: As I already had this general admission and this adult selected, if I click the Edit

08:00: button, you will see a dropdown.

08:02: If I had typed something here that didn't match general admission, maybe it was

08:06: just called admission.

08:10: General admission didn't exist in our list.

08:13: When you click edit, you won't see something here because it's not in the list

08:17: anymore.

08:17: You want to make sure that if you create something prior to making a list, you go

08:22: back into those items and select them from the dropdown.

08:25: That way, they are associated with the list you have created.

08:32: So now if I create a new ticket group, you'll see that the first thing that defaults

08:35: to is the first list item in that ticket group list that I just created.

08:39: So it's defaulting to general admission. But if I click this dropdown, you can see

08:44: the other items that I have.

08:45: So here I'm going to say this is groups and I'm not going to go through the rest of

08:49: this because we'll cover that in a future event configuration.

08:52: But you can see that we can now add that through that drop down there.

08:56: So I'm just going to go ahead and hit create ticket group there.

08:59: And then under our ticket group is where you can then add your ticket types.

09:10: And again, we'll go into more detail about this in future videos. But if I select that,

09:14: you'll now see that we have that dropdown for our ticket type names.

09:19: I'm going to say this is a child and we have that dropdown for our GL code. And as you

09:24: can see, it defaults to that first one in the list, which is none selected. That's

09:27: why I like to put that in there. You

09:29: don't have to do that at all. You

09:31: could default the first one to your general admission or a default GL code that you

09:35: have. But

09:35: I like this because it's very obvious that somebody has not selected that during their

09:40: configuration and that they need to go back in and update that. So

09:44: here I'm going to go ahead and select that full string. And

09:47: as you can see, it is that full string. It's

09:49: got that pipe. So

09:50: now we are separating our recognized from our deferred. I'm

09:54: going to create that ticket there. Oh,

09:56: I forgot to put a price. So

09:58: we're going to say our child is $15.

10:04: And now we have our two ticket groups.

10:07: We have our list against our ticket group names, our ticket type names, and our GL

10:12: codes.

10:13: As I mentioned, if you want to add something in the future or change the spelling

10:17: of something, you can simply go back into your settings, your global portal settings

10:21: area here. Click on configuration.

10:26: Type in what you want to change.

10:27: For example, this will be the standard ticket group names.

10:33: As an example, I can show you what this looks like

10:35: if I remove the word general.

10:38: We're changing that to admission.

10:40: I'm going to save that again,

10:43: go back into our event,

10:48: and you'll see here now that there's nothing listed.

10:51: That's because general admission no longer exists in our list, and we need to

10:56: reselect that.

11:02: So now I'm changing that to admission, updating that ticket group, and now we have our

11:06: admission and our groups.

11:09: Learn to create and manage GL code lists, ticket group names, and ticket types,

11:14: enabling dropdown selections that enhance data integrity and ease event

11:18: configuration.

00:00: This video showcases how to navigate and manage fees within the Ticketure CMS.

00:05: You will see how to access fee details and interact with fee entries effectively.

00:09: Click here to open the Portal Level settings where you can manage your Fees Sets.

00:14: Click "Fees" to view the list of fees associated with your orders and transactions.

00:20: The first fee is an outside fee.

00:22: That's going to be a fee on top of the ticket price.

00:25: I like to think about this as like sales tax. Or maybe you have a fee that you want

00:30: to charge for every ticket sold.

00:32: We have the options for a fixed fee or a percentage.

00:35: And you could also have both.

00:37: The inside fee is baked into the ticket price.

00:39: So this is the idea that $20 per ticket is what is shown to the guest but that

00:44: ticket is really $19 and includes a $1 fee. We can report

00:48: on all of these separately as well within the system. And just like outside fees you

00:53: have a choice to use a dollar amount, percentage amount or both.

00:58: You can have an outside fixed and an outside percentage fee and you can have an

01:01: inside fixed and an inside percentage fee but you can't have multiple of the same.

01:07: What does that mean?

01:09: Say instead of a $1 service fee, I have a 3% service fee and 6.5% sales tax, I

01:15: would have to combine that together into a 9.5% percentage fee.

01:20: We have some fee calculation options here at the bottom.The

01:22: first being, do you want the fee based on the discounted value or the face value?

01:28: value?

01:29: Should any fees be set on free tickets or are they free just kind of across the

01:33: board?

01:34: If there's a specific order that you want those fees calculated, the fixed first, the

01:39: percentage first, and vice versa.

01:41: Finally how should it be calculated like a tax or like a gateway charge.

01:46: Keep in mind at the portal level any fee set here would be on all tickets

01:50: either seller all tickets.

01:52: We do have some additional fee options

01:54: we can get really specific on fees

01:56: so we can say certain events don't have fees and certain tickets within events have

02:00: certain fees.

02:02: These fee sets will be covered in another training.

02:06: This video demonstrated how to navigate the Fees sections in Ticketure's CMS, allowing

02:10: you to review individual fee entries efficiently.

02:14: If you have any additional questions please reach out to support support@ticketure.com