Need the Tessitura family insight regarding who is doing what in terms of requiring Registration/Log-in for online purchasing. Or, allowing for Anonymous/Guest buying.
One key concern is if we don't require Log-in, we will end up with duplicate records in Tessitura. Are you experiencing this? How do you handle?
The problem with Log-in is that our Constituents frequently do not remember their password(s) and that can create an endless loop to find? Do you have a solution? Are you getting resistance to Log-in?
Our goal is to be able to understand the full purchasing dynamics of each of our Constituents. Ultimately to pre-service, post-service, up-sell and cross-sell.
Curious to hear from you via Tess or directly (eweisser@92y.org). Thanks for your insight.
Elizabeth
_____________________________
Elizabeth Weisser Director of CRM 92nd Street Y | 1395 Lexington Avenue | New York, NY 10128 | P: 212.415.5596 | http://www.92Y.org
Hi Elizabeth,
For our two websites we don't require login until time of check out. This allows the user to see seating info and add to cart.
I think if you go the route of not requiring a user to login , you would have to auto create a login based on the user's information. This login the user would not know or use. This route I think would create a lot of duplicate records that would have to be merged.
Jon
I wonder if it's possible to simply check out with your generic web user, but require a new address be put in each time. The address could then be added and immediately inactivated in the web user account, but would remain attached to the order.
Either way, you'll end up with lots of contact data that you can't use for marketing, but I assume that's the point of doing anonymous check out.
For an anonymous sale, you can still capture name and address for shipping since that is unique to the order. You would just have a ton of address and email records in that generic account.
For tracking purposes, you could also create either a CSI or write to a local table all of the captured patron info and either leave it there or if you have the staff resources, you could manually create new accounts and make sure that there are not duplicates, or try creating an automagic process.