PatronManager Help

On-Demand Feature: More control over custom Ticket Order fields (June 2016)

Updated on

Use this link to share with your colleagues:

On-Demand Feature: More control over custom Ticket Order fields (June 2016): https://help.pm.leapevent.tech/a/550628

This article is old!  Wouldn't you rather read something... fresher?

There may be outdated information or suggestions in this article that made sense at the time of the release, but no longer.  For the most up-to-date information about this topic, use a keyword in the search bar above.  If you're looking for more current release notes, you can find those here.

We've updated the types of custom Ticket Order fields that can be set up, so you can control who sees what with more precision than ever.

You've had the ability for a while to create custom Ticket Order fields to capture or display extra information, and now you'll be able to fine-tune whether those fields should be public (visible on your Public Ticketing Site and confirmation emails), private (visible only to the box office), or "invisible" (hidden in both places and only used for things like reporting or printing).

This is a feature that the Client Support team can help you set up on a case-by-case basis.

Here's how you might use the three levels of visibility for custom Ticket Order fields:

1. Public: Visible on your Public Ticketing Site and confirmation emails

Let's say you want your patrons to be able to define a "Will Call Name" when buying tickets, so that the name of the person picking up the tickets can be different from the person who is paying for the tickets. We'd create a custom field for that, and it would be displayed and used on your online Public Ticketing Site, visible to everyone, plus included in the confirmation a patron receives when making a purchase:

1. Public: Visible on your Public Ticketing Site and confirmation emails

2. Private: Only visible to box office staff

In this example, you might want your box office staff to be able to record administrative notes on the Ticket Order for the Front of House staff -- notes that don't need to be visible to your patrons on the confirmation email or entered by them when they're buying tickets online. The field for those notes would appear on the Quick Order Form screen and be available in reporting, but not the patron-facing places:

2. Private: Only visible to box office staff

3. "Invisible":  Used only by the PatronManager system (for use in reporting, ticket printing, etc.)

There are some custom fields on the Ticket Order that our Client Administration team might help you create when you need custom information on your printed tickets or reports, but that you wouldn't need to see on the actual Ticket Order screen.

In this example, your organization might have a special "Header Address" field that prints the Contact's address on the Header Card even if the Delivery Method isn't Ship. That field needs to exist in PatronManager so that the ticket's header card can print correctly, but your box office staff probably doesn't need to see it (and your patrons definitely don't).

3. "Invisible":  Used only by the PatronManager system (for use in reporting, ticket printing, etc.)

To get started, reach out to us via the PatronManager Help tab!

Click the "Support Request" button in the Help tab, and use the following templates to request a new Ticket Order field or make edits to your existing fields:

New Custom Ticket Order Field

Name of field:

What the field should do:

What visibility the field should have (private, public, or invisible):

----------------------------------------------------------------

Existing Custom Ticket Order Field

Name of field:

What visibility the field should have (private, public, or invisible):

To get started, reach out to us via the PatronManager Help tab!

Next up, CRM Snapshots

Keep on keeping on to learn about what's new with CRM Snapshots.

Next up, CRM Snapshots
Previous Article Gift Certificates, continued: Card Types, Pricing, Reporting, and more (June 2016)
Next Article CRM Snapshot Enhancements (June 2016)
Still Need Help? Continue to the Client Community