To make sure your Tessitura system syncs properly with crowdEngage, we need you to set up a few items in Tessitura:

IP Whitelisting

Permissions

Stored Procedure

Information

Writeback

IP Whitelisting

Please allow API access from the following IP addresses:

52.213.219.109

18.200.36.114

Permissions

You will need to create a new API user. In Tessitura Securities, go to Maintain Users and then to New. Create a new user for the Crowd Engage API. This user must be of the type API, you must set a secure password. If you use Control Groups, make sure to assign this user the relevant one. Make a note of the User ID, unencrypted password for later.

Next, you must assign a User Group to the User. If you need to create a new one, go to Maintain Groups and select New. If you use Divisions or Organizations  make sure to select the ones you want Crowd Engage to view data from.

Finally, go to services and assign the below services to the API user group.

We will need View access to the following resources:

• CRM/Constituents
• TXN/ProductionSeasons
• TXN/Performances
• TXN/Performances
• TXN/Orders
• TXN/Facilities
• TXN/Productions
• TXN/Titles
• AccessControl/EventControl
• ReferenceData/Theaters
• ReferenceData/PerformanceStatuses
• ReferenceData/SubLineItemStatuses
• ReferenceData/Sections
• TXN/InventoryWebContents

We will need View, Edit and Add  access to the following resources:

• TXN/Orders
• Custom/Execute
• TXN/ProductionSeasons/Search

Stored procedure

You will need to add the following stored procedures in SSMS:

CREATE PROCEDURE [dbo].[LP_CE_UPDATED_ORDERS]

(@start_dt datetime = null, @end_dt datetime = null)

as

SELECT order_no FROM T_ORDER

WHERE last_update_dt BETWEEN @start_dt AND @end_dt

GO

CREATE PROCEDURE [dbo].[LP_AS_SUBLINE_ITEMS]

(@start_dt datetime = null, @end_dt datetime = null)

as

SELECT order_no FROM T_ORDER

WHERE last_update_dt BETWEEN @start_dt AND @end_dt

GO

Please register the stored procedure in the TR_LOCAL_PROCEDURE System/Reference Table and make sure that the permissions are added to the Procedure to allow are set up for the stored procedure to allow Tessitura to execute it:

We will mostly only ever use this in 1 minute intervals. Once it is installed, please could you let me know the procedure name (normally LP_CE_UPDATED_ORDERS) and ID from TR_LOCAL_PROCEDURE and ensure our user has access to execute it?

We need the correct information as per below:

• Tessitura base URL

• UserID and unencrypted password (our system will encrypt this automatically)

• User group ID

• Location name

• Stored procedure name
  
  

• After we have confirmed your Ticketing system is set up we will need you to send over a CSV file that includes the order IDs for every booking for a future performance. This is to make sure all your customers are accounted for when sending out the messaging. 

• We will need to set up a unique subdomain that will link to crowdEngage. - We would usually recommend something like visit.exampletheatre.co.uk - Once you have chosen this we will send instructions to get it set up

• If you wish to use email we will also need to set up a sender domain. This is usually something like mail.exampletheatre.co.uk - again we will send instructions for your web team to set this up

• (UK/EU Only) For your SMS messages we also need a sender name. This can be a maximum of 11 characters including spaces so could be something like Example - this can take a while to register so it would be good to choose this one as soon as possible so it's ready when you go live. You can have two sender names if you'd like one for each venue.

• If you are using the pre-ordering function and you don’t already have one, you would need to set up a stripe account at http://www.stripe.com it’s then really easy to link this to your crowdEngage account to receive payments.

• We will also need the API key from your epos system if it is one that we integrate with. We can send over specific instructions depending on the system you use. If you are using the system manually you don’t need anything, we will let you know how this all works.

Once we've got the ticketing system linked up correctly and your subdomain is registered, we can run a training session for your team.. After training we would suggest running some test events and making sure that your team is comfortable with the whole process before going live. We will be on hand to help at each stage of testing and to customise the process depending on the needs of your organisation.

Tessitura Writeback

If you would like shared tickets to write back to your Tessitura system (e.g - one customers shares a ticket to another customer but you want to capture who has attended) we would need the following information to create these records:

• ID from TR_ORIGINAL_SOURCE for constituent record 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

• ID from Ticketing Setup > Mode of Sale for the Mode of Sale to use when writing back Recipients from CrowdEngage

• ID from of the Source to use when writing back Recipients from CrowdEngage. This is found in Campaigns > Appeals > Sources:
  
  
  

• ID from Campaigns > References > Payment Methods or the Payment Method to use when writing back Recipients from 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