Addressing addresses

As a Consortium a key Address issue for us is the constraints of a single Primary address; the way that it and its Salutation is presented on the General Tab, and how to handle differing views of a single mail purpose in different organisations. It’s a tricky area trying to balance the benefits of sharing within a Consortium against the need to protect and control usage within each org.

 

Mail Purposes is good functionality but we realised early on that we couldn’t use MPs on any ‘shared’ cross-consortium addresses. This is because, for example, what one org considers an Invite address another may not.

Because the Primary Address is exposed to all Consortium users, on any Addresses where these things matter (donors, subscribers, media, other corporate contacts) then orgs often have to create their own control-grouped address types and Salutations, join these two then apply Purposes there.

 

This is a clumsy process often requiring duplicate data entry on every address and Salutation. It also relies on Users understanding the notion of shared and cg’d addresses and where they can and cant apply Purposes. It only requires one accidental application of a Purpose on a shared or primary address to undo any Purposes work on cg’d addresses.

 

End result is that some key areas are working exclusively with cg-d addresses and salutations and have to learn to pretty much ignore the General Tab.

But on the Address tab when combining a Salutation with an Address the result of that combination is never actually viewable (as it is on the General Tab). This is not ideal for operations working with sensitive client info and is constantly a point of confusion for users who don’t use Tess regularly.

 

So kind of backwards story-wise (ie the story is post NextGen)

 

·         Peter the Philanthropy manager at ConsortiumPartner1 is inviting Mr Rich to an opening night event. Mr Rich is a donor. Peter uses the private home address that only he and his team know about. He wants to use this address for all invitation activity and includes a personal salutation “Dear Richie”. He can also see Mr Rich’s business address which Peter considers the ‘primary’ address for other general business purposes. This includes his Organisation and Job Title info and should be the default address for any activity Peter does if he doesn’t specify a purpose for the correspondence. Peter chooses not to view any other addresses, but could add to his view another ‘shared’ address which is the Business PO Box that the Box Office had garnered from a ticketing purchase and which CP1 has made available to the Consortium. CP1 want to use this shared address for all ticketing activity in the future.

 

            In reporting on the Opening Night activity even though Mr Rich was invited at his private address as a Donor, Peter wants to be able to provide his CEO with Mr Rich’s job title and organisation.

 

·         Lesley is the Subscriptions Manager at ConsortiumPartner2. Mr Rich is a subscriber, he uses his personal PO Box for all subs activity from CP2. Lesley considers this Mr Rich’s primary address. It’s the only address she wants to see, she considers it ‘her’ address.

 

·         Matt is a Box Office seller at ConsortiumPartner3. Mr Rich has telephoned CP3 for the first time to buy tickets to a show. He searches for and finds the record CP1 had created with the shared address. Mr Rich actually provides the same home address that CP1 considered ‘private’ to have his tickets mailed. Matt adds this to his address view and indicates that its to be used for all ticketing activity from CP3 in the future. This doesn’t effect CP1’s setting of the shared address as their ‘ticketing’ address.

 

Too easy …

 

peter nelson business analyst

information systems

pnelson@sydneyoperahouse.com

T+61 2 9250 7180  F+61 2 9251 7821 

 

SYDNEY OPERA HOUSE BENNELONG POINT

GPO BOX 4274, SYDNEY NSW 2001, AUSTRALIA

SYDNEYOPERAHOUSE.COM

 

 

 

As we reported in the Next Gen webinar this week, Release One of the Next Gen software will focus on Constituent themes.  We have already asked about Constituent Search and Constituent Relationships.  Today’s question surrounds Postal Addresses (we will ask about email, webpages, phones etc. in a separate thread).

 

Thinking about Postal Addresses in your business, some very BROAD questions: 

 

What are some challenges that you have surrounding addresses today?

Are there trends you are seeing that could impact postal address functionality in the future?

What do you like about Postal Address functionality in existing Tessitura? 

What would you like to see changed/improved about Postal Address functionality?

Any other thoughts about addresses, your business, and Tessitura?

 

(For extra credit: We ultimately take user requirements and express them as “stories”. Feel free to answer this thread however you’d like, but for fun, you could answer in the form of  a “story”.  An example of a story might be: “As a Special Events Director, I need to be able to send Gala Invitations that include very formal addressing (Street rather than St., Boulevard rather than Blvd), even if this isn’t the mailing convention for other aspects of our business.”)

Thanks!

Andrew

You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

Please consider the environment before printing this email.
=====This message is intended for the addressee(s) named and may contain confidential information.
If you are not the intended recipient, please delete it and notify the sender.
Views expressed in this email are those of the individual sender and are not necessarily the views of the Sydney Opera House Trust=====

As a Consortium a key Address issue for us is the constraints of a single Primary address; the way that it and its Salutation is presented on the General Tab, and how to handle differing views of a single mail purpose in different organisations. It’s a tricky area trying to balance the benefits of sharing within a Consortium against the need to protect and control usage within each org.

 

Mail Purposes is good functionality but we realised early on that we couldn’t use MPs on any ‘shared’ cross-consortium addresses. This is because, for example, what one org considers an Invite address another may not.

Because the Primary Address is exposed to all Consortium users, on any Addresses where these things matter (donors, subscribers, media, other corporate contacts) then orgs often have to create their own control-grouped address types and Salutations, join these two then apply Purposes there.

 

This is a clumsy process often requiring duplicate data entry on every address and Salutation. It also relies on Users understanding the notion of shared and cg’d addresses and where they can and cant apply Purposes. It only requires one accidental application of a Purpose on a shared or primary address to undo any Purposes work on cg’d addresses.

 

End result is that some key areas are working exclusively with cg-d addresses and salutations and have to learn to pretty much ignore the General Tab.

But on the Address tab when combining a Salutation with an Address the result of that combination is never actually viewable (as it is on the General Tab). This is not ideal for operations working with sensitive client info and is constantly a point of confusion for users who don’t use Tess regularly.

 

So kind of backwards story-wise (ie the story is post NextGen)

 

·         Peter the Philanthropy manager at ConsortiumPartner1 is inviting Mr Rich to an opening night event. Mr Rich is a donor. Peter uses the private home address that only he and his team know about. He wants to use this address for all invitation activity and includes a personal salutation “Dear Richie”. He can also see Mr Rich’s business address which Peter considers the ‘primary’ address for other general business purposes. This includes his Organisation and Job Title info and should be the default address for any activity Peter does if he doesn’t specify a purpose for the correspondence. Peter chooses not to view any other addresses, but could add to his view another ‘shared’ address which is the Business PO Box that the Box Office had garnered from a ticketing purchase and which CP1 has made available to the Consortium. CP1 want to use this shared address for all ticketing activity in the future.

 

            In reporting on the Opening Night activity even though Mr Rich was invited at his private address as a Donor, Peter wants to be able to provide his CEO with Mr Rich’s job title and organisation.

 

·         Lesley is the Subscriptions Manager at ConsortiumPartner2. Mr Rich is a subscriber, he uses his personal PO Box for all subs activity from CP2. Lesley considers this Mr Rich’s primary address. It’s the only address she wants to see, she considers it ‘her’ address.

 

·         Matt is a Box Office seller at ConsortiumPartner3. Mr Rich has telephoned CP3 for the first time to buy tickets to a show. He searches for and finds the record CP1 had created with the shared address. Mr Rich actually provides the same home address that CP1 considered ‘private’ to have his tickets mailed. Matt adds this to his address view and indicates that its to be used for all ticketing activity from CP3 in the future. This doesn’t effect CP1’s setting of the shared address as their ‘ticketing’ address.

 

Too easy …

 

peter nelson business analyst

information systems

pnelson@sydneyoperahouse.com

T+61 2 9250 7180  F+61 2 9251 7821 

 

SYDNEY OPERA HOUSE BENNELONG POINT

GPO BOX 4274, SYDNEY NSW 2001, AUSTRALIA

SYDNEYOPERAHOUSE.COM

 

 

 

As we reported in the Next Gen webinar this week, Release One of the Next Gen software will focus on Constituent themes.  We have already asked about Constituent Search and Constituent Relationships.  Today’s question surrounds Postal Addresses (we will ask about email, webpages, phones etc. in a separate thread).

 

Thinking about Postal Addresses in your business, some very BROAD questions: 

 

What are some challenges that you have surrounding addresses today?

Are there trends you are seeing that could impact postal address functionality in the future?

What do you like about Postal Address functionality in existing Tessitura? 

What would you like to see changed/improved about Postal Address functionality?

Any other thoughts about addresses, your business, and Tessitura?

 

(For extra credit: We ultimately take user requirements and express them as “stories”. Feel free to answer this thread however you’d like, but for fun, you could answer in the form of  a “story”.  An example of a story might be: “As a Special Events Director, I need to be able to send Gala Invitations that include very formal addressing (Street rather than St., Boulevard rather than Blvd), even if this isn’t the mailing convention for other aspects of our business.”)

Thanks!

Andrew

You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

Please consider the environment before printing this email.
=====This message is intended for the addressee(s) named and may contain confidential information.
If you are not the intended recipient, please delete it and notify the sender.
Views expressed in this email are those of the individual sender and are not necessarily the views of the Sydney Opera House Trust=====