Tix History & Web Login for Renewals

We are concerned with our renewals coming up and where the login vs the subscription package will be going in the migration.

Currently our email addresses and logins are not always tied to a N1/N2 indicator. If the ticket history is staying with the household account, can a patron login on their existing or even create a new login for their individual account and still be able to renew their subscription that is on their household account?

Parents
  • Hi Angela -

    If you stick with the current Tessitura recommendation of processing all orders on the household the SOAP web API (current v10 web methodology) is backwards compatible and will transact online as the household, even if the person logs in with a login assocated with the A1 or A2 account.

    The only thing you'll want to check is if you have custom procedures that return information to the web based on the customer number you'll want to decide if you want the affiliate information returned as well as the household.

    Hope that makes sense,

    Heather
    Seattle Rep 

Reply
  • Hi Angela -

    If you stick with the current Tessitura recommendation of processing all orders on the household the SOAP web API (current v10 web methodology) is backwards compatible and will transact online as the household, even if the person logs in with a login assocated with the A1 or A2 account.

    The only thing you'll want to check is if you have custom procedures that return information to the web based on the customer number you'll want to decide if you want the affiliate information returned as well as the household.

    Hope that makes sense,

    Heather
    Seattle Rep 

Children
No Data