We can write back the sharing of tickets in crowdEngage to Tessitura. This process either creates or locates a constituent record, creates a relationship between the purchaser and the recipient of the tickets and then adds the recipient in the recipient field in the subline item of the ticket that has been shared. Screenshots of all of this are at the end of this document.
If you would like shared tickets to write back to your Tessitura system we need some additional information from you.
Settings for new customers created by crowdEngage
When a customer shares a ticket on crowdEngage, the recipient must fill in some personal details to receive the ticket. We then search Tessitura for the provided email address. If that email address already exists on Tessitura, we use the most recently created constituent record. If it does not exist, we will create a new constituent. In order to do this, we need the following details:
- ID from TR_ORIGINAL_SOURCE for a constituent record created by crowdengage
- ID from TR_PHONE_TYPE for phone numbers in constituent records created by crowdEngage
- ID from TR_ADDRESS_TYPE for addresses in constituent records created by crowdEngage
- ID from TR_ASSOCIATION_TYPE for the Association between the Individual Lead Booker → Guest
- ID from TR_AFFILIATION_TYPE for the Association between the Household/Organisation Lead Booker → Guest
Details to allow us to modify the order
We then need to open the original order and assign the recipient the sublime items of that order. To do this, we need to open a web session, and in order to do that we require the following details:
- An ID from Ticketing Setup > Mode of Sale
- An ID of a Source, found in Campaigns > Appeals > Sources:
- An ID of a Payment Method from Campaigns > References > Payment Methods
Please note, we will not change the Mode of Sale, Source or Payment Method on an order that has been shared, we merely need these details to be able to open and close the web session to make the amends to the order
We also need you to provide the User Group for our API user additional access to your Modes of Sales. Please ensure the User Group has access to all Modes of Sale so that we can load the order. Without this, Tessitura will throw an error in the same way it does in the application if a user tries to open an order made in a Mode of Sale they do not have access to.
Permissions
If you would like to use your Tessitura marketing permissions to influence your crowdEngage sending we need to make a further API call. You do not need any further set up but please advise that you authorise this.
We then need you to tell us the names of the permissions you are using and we will create our rules for sending based on this.
Which numbers/emails you send to
The default in crowdEngage is to send messages to the newest email or mobile phone number on record. This is on the basis that it is likely the newest is the most up to date and likely to reach your customer. If you’d like to change this to look at fields in a different order. Please let us know which fields using their ID numbers.
How the write back appears in Tessitura
The purchaser will have an association added to their record for the person the ticket was shared with:
The recipient will have a record created with the reciprocal association. They will also have the original source determined in your set up:
The order will have the recipient added in the subline item for the shared ticket:
