Getting Login info to constituents

We are new to Tessitura and are getting ready to send out an email to all our constituents who were moved over from our old system with their login information so that they can log in through our website.

Does anyone have any verbage/template for this email that they would be willing to share?
Any opinions about whether it's better to do this or to just let them set up a new account on their own and merge accounts later?

 

Parents
  • It’s a bit of a difficult decision because generally ticket buyers are all about updating their login details when buying tickets. Even if you send them an e-mail with their details they will leave it until the time comes to buy some tickets which may leave a big gap! In addition you need to think about PCI with password updates as you can't send them an e-mail stating this is your login and this is your new password. It would be best to have a secure link (token) which takes them back to your website and instructs them to create a new password.

    When we swapped we didn't let them know as we had a version of Password update on our site which would allow them to unlock their account. Our original password update wasn’t PCI compliant and we had to remove it. We then spent the best part of a year unlocking accounts and updating passwords for patrons. When we migrated we set their new passwords as their const ID and after about 4 years you still speak to patrons who are just using their account for the first time since the migration to Tessitura. Thankfully we now have a PCI compliant password update!!!

     

Reply
  • It’s a bit of a difficult decision because generally ticket buyers are all about updating their login details when buying tickets. Even if you send them an e-mail with their details they will leave it until the time comes to buy some tickets which may leave a big gap! In addition you need to think about PCI with password updates as you can't send them an e-mail stating this is your login and this is your new password. It would be best to have a secure link (token) which takes them back to your website and instructs them to create a new password.

    When we swapped we didn't let them know as we had a version of Password update on our site which would allow them to unlock their account. Our original password update wasn’t PCI compliant and we had to remove it. We then spent the best part of a year unlocking accounts and updating passwords for patrons. When we migrated we set their new passwords as their const ID and after about 4 years you still speak to patrons who are just using their account for the first time since the migration to Tessitura. Thankfully we now have a PCI compliant password update!!!

     

Children
No Data