Disabling Registration Fields in TNEW

Going to play devil's advocate here. I don't think using Short Registration is a good way of signing up people for an email list. I would much rather prefer Wordfly hold onto this information until the user is planning to purchase.

Here's my rundown on ShortReg:

A) It creates a constituent in Tessitura without any meaningful information other than email and possibly a password.

B) It creates a login to said constituent, which can be troublesome since logins are unique and this may fail if the user is in the system and has opted out already, especially if they want to opt back in.

C)Users on the email list may be unaware they have a login as they have only signed up for an email list. One of the most prominent marketing tactics and checkout flows becomes complicated, lost sales and duplicate accounts abound.

D)Tessitura isn't an ESP, it's a CRM, and as such it doesn't handle email specifically well. ESPs treat a single email address as a registered endpoint, a user. Conversely Tessitura can associate multiple user accounts with the same email address as it is just storing contact information. The user account is not guaranteed to be unique to the email.

I know these views may seem a bit unfavorable but it has been my experience that using ShortReg when there is no intent to purchase can cause some serious confusion for patrons; especially with the way Tessitura handles Emails/Logins/Constituents compared to the rest of the Web.

Christopher, when you say you "prefer Wordfly to hold this info" are you able select the Wordfly list as well as your Tess registered list of  "everyone" in order to send out an eblast to everyone? We plan to use Wordfly as well and I was wondering how that synced up, if at all.

Christopher, when you say you "prefer Wordfly to hold this info" are you able select the Wordfly list as well as your Tess registered list of  "everyone" in order to send out an eblast to everyone? We plan to use Wordfly as well and I was wondering how that synced up, if at all.

Unknown said:

Christopher, when you say you "prefer Wordfly to hold this info" are you able select the Wordfly list as well as your Tess registered list of  "everyone" in order to send out an eblast to everyone? We plan to use Wordfly as well and I was wondering how that synced up, if at all.

Tessitura and Wordfly work fairly independently with a loose, albeit powerful, integration; generally speaking the flow we are trying to use is as follows:

• When an email list is created or updated from Tessitura, within Wordfly, an Output Set download from Tessitura is initiated.
• New information is pulled via the output set and overwritten, by email address, in the Wordfly database.
• If an email address already exists in the List the additional information will be dropped; this goes for duplicates in the same list (Wordfly will only hold one record per field, per email address).
• By making sure the Tessitura Lists are loaded first by marketing, then the Wordfly lists, we keep the data as clean and matching as possible. Promotions for Tessitura Constituents should be created and updated (in ideal situations) accordingly. 
• Unsubscribes can be resubscribed (overridden) as they are downloaded from Tessitura, as long as suppressions for the Tessitura email addresses are properly recorded in Tessitura (via local procedure)
• Assuming everything is working as planned Wordfly can handle most ESP tasks like unsubscribes and bounces.

This setup is far from perfect; the major advantage against ShortReg is that a first time buyer won't have a login associated to their account without at least starting the ticket purchase path. The barrier to entry for the email list is also lowered to  aid in initial email signups as well.