Addressing addresses

 

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

Parents
  • What I like about postal addresses currently is the ability to tie it a specific salutation, the seasonal months, and mail purposes. For the most part this works really well for me.

     

    However, I hate that addresses are tied to phone numbers because most people have cell phones that are not tied to an address. When an address gets inactivated if there is a phone it gets inactivated as well, when very well it’s an accurate one. It allows for a lot of user error if someone forgets to move the phone when inactivating an address. I think phones (like emails) need to be kept separate from addresses entirely.

     

    The story that happens to me most often relates to foundation and corporate records. For example, I need to pull an event list. Corporation ABC meets my select criteria, however N2 on that record is the contact for our corporate coordinator. I want to send the invitation to the CEO, COO, and CFO of that company. Right now I pretty much have to manually do that. I wish that I could create 3 salutations, 3 addresses tied to each unique salutation, select “Invitations” as my mail purpose and have them ALL pull into a list. When I look at a list of 20 I have to think to myself its really 40 because there are two people from each organization being invited. And I have to remember their names, and titles, and add them manually to my spreadsheet before I do a mailing.

     

    In an ideal world you would be able to mail to multiple addresses/salutations for one record. Though of course I don’t know how you would actually do that.

     

    What happens to me with foundations is usually that the giving is from the foundation but we want to invite the individuals at their home address. I can manually create a home salutation and address with an event mail purpose (which is what I do now) on their foundation record, but it seems clunky since I’m basically duplicating information from their individual record. I wish that there was a way to select the address I want to mail perhaps through associations? I can see that these constituents are related and while one record meets my criteria I am choosing the address from an associated record. This would also be helpful if I wanted to invite multiple board members from that foundation, I could then choose multiple home addresses or similar to the corporate suggestion have the ability to choose multiple names tied to the foundation address.

     

    -Marta

     

    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Andrew Recinos
    Sent: Friday, January 15, 2010 2:37 PM
    To: marta@smm.org
    Subject: [Tessitura Next Generation Forum] Addressing addresses

     

     

    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!

Reply
  • What I like about postal addresses currently is the ability to tie it a specific salutation, the seasonal months, and mail purposes. For the most part this works really well for me.

     

    However, I hate that addresses are tied to phone numbers because most people have cell phones that are not tied to an address. When an address gets inactivated if there is a phone it gets inactivated as well, when very well it’s an accurate one. It allows for a lot of user error if someone forgets to move the phone when inactivating an address. I think phones (like emails) need to be kept separate from addresses entirely.

     

    The story that happens to me most often relates to foundation and corporate records. For example, I need to pull an event list. Corporation ABC meets my select criteria, however N2 on that record is the contact for our corporate coordinator. I want to send the invitation to the CEO, COO, and CFO of that company. Right now I pretty much have to manually do that. I wish that I could create 3 salutations, 3 addresses tied to each unique salutation, select “Invitations” as my mail purpose and have them ALL pull into a list. When I look at a list of 20 I have to think to myself its really 40 because there are two people from each organization being invited. And I have to remember their names, and titles, and add them manually to my spreadsheet before I do a mailing.

     

    In an ideal world you would be able to mail to multiple addresses/salutations for one record. Though of course I don’t know how you would actually do that.

     

    What happens to me with foundations is usually that the giving is from the foundation but we want to invite the individuals at their home address. I can manually create a home salutation and address with an event mail purpose (which is what I do now) on their foundation record, but it seems clunky since I’m basically duplicating information from their individual record. I wish that there was a way to select the address I want to mail perhaps through associations? I can see that these constituents are related and while one record meets my criteria I am choosing the address from an associated record. This would also be helpful if I wanted to invite multiple board members from that foundation, I could then choose multiple home addresses or similar to the corporate suggestion have the ability to choose multiple names tied to the foundation address.

     

    -Marta

     

    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Andrew Recinos
    Sent: Friday, January 15, 2010 2:37 PM
    To: marta@smm.org
    Subject: [Tessitura Next Generation Forum] Addressing addresses

     

     

    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!

Children
  • This input is coming from a database wonk, so its not entirely related to user experience, but with that caveat:

    The time restrictions on addresses are great but I think there must be a more elegant way to deal with that information both in the user interface and the database itself.  Currently, the default is to have each of the monthly check boxes filled which muddies up the front end and adds more data to the record.  I would love to see a system in which an address is assumed to be for all time periods unless there is an indicator that the user can see (it would be in a different color, for instance). 

    Also, the month by month selection is restrictive.  You should be able to add a very specific restriction that is either a one time occurrence or a recurring action.  Story time:

    A) A board member is going to Europe for three months.  During that time, they should not be sent any mailings. So I can enter it as "No Mail Delivery 04/15/2010 - 06/30/2010 - no recurrence"

    B) We have "Snow Bird" constituents who go to Florida every summer.  The restriction is then entered as "No Mail Delivery 06/01 - 08/27 - annual recurrence"

    As a bonus, the snow birds gave us their Florida address and we have entered it in Tess. The system then knows (by date) which address should be their primary one and displays the appropriate address on the constituent screen as well as in lists, extractions, etc. (For the DBAs in the room, I am envisioning a TX_ADDRESS_RESTRICTION table.)

    I second the vote for de-coupling phone numbers from addresses.  I know you can enter unrelated phone numbers now but under the current arrangement, its not an intuitive move.

    Finally I would absolutely LOVE a process that checks the format of the address against USPS naming conventions.  The user should be able to override it if they want, but if they spell out "Street" instead of "St" a pop up should alert them. We are currently using a script (which I think many others have as well) that auto-corrects certain items in the address but notifying the user at the time of entry is a good way to help enforce consistent data entry and ultimately helps get better results out of mailings.

    In the current system, I love the ability to click on the stamp to get an envelope.  I would love to see this expanded a bit so you can select from different types of documents.  Form letters for instance.

    "Thank you for your call today regarding _____. I hope that we have resolved the situation to your satisfaction.  If you have any further questions please contact <tessitura user's name and contact info>."

    This may have something to do with my love of Mad Libs.


    Can't wait to see how the constituent record evolves in the next generation!

     

  • I totally agree with the phone number idea - even with a land line, it's not entirely true that a phone number couldn't be moved to a new address.
     
    I also agree with Levi's breakdown of how the month checkboxes work (or don't work, as the case may be).
     
    The biggest issue that we have here is that we use AVS when running credit cards.  Currently, Transcend looks *only* at the primary address when checking the correct billing address on a credit card, which can create problems.
     
    There's a couple of ways to look at this, story-wise:
     
    1. Jane is purchasing additional tickets on her company credit card, but her primary address is her home address.  In order for her to use her company credit card, she has to provide the company billing address, which we have to add into her account (with an address type that we've made of "CC Charge - No Mailing"), make that address primary, charge the card, and then remember to change back to the primary address once the card has been charged.
     
    2. Jane and Mary share a subscription, but all of the tickets are mailed to Jane.  Mary calls in to exchange tickets for the pair of them, and there's an upgrade charge.  Mary agrees to pay the upgrade charge on her card.  Rather than moving to Mary's account, paying off the upgrade fee, and then moving the upgrade fee back to Jane's account (where the exchanged tickets are), we elect to pay the upgrade fee in the exchanged order (in this case, in Jane's account).  Then it's the same scenario - add Mary's address to Jane's account, mark it as primary, charge the card, and then at the end of the transaction remember to make Jane's address primary again.
     
    If the user forgets to mark the *real* primary address primary at the end of the transaction, then we end up mailing to the wrong address unless somebody catches the error.  This is especially problematic if we're processing a transaction where we're *not* mailing anything in that transaction - it's easier to forget to make the switch back, and then we end up sending the next piece of mail (postcard, letter, renewal, whatever) to the "non-primary" billing address, which is still inadvertently marked primary.  In the case of Jane, this is at least okay because Jane does receive whatever we're mailing (albeit at a different address than she'd prefer).  In the second scenario, however, Jane doesn't even receive the mailing - Mary does, which is problematic.
     
    All of this to say that we'd love to have a "Billing Address" address type that *doesn't* have to be primary but can still be seen somehow by Transcend, so that we can still confirm billing addresses without having to go through all of this.
     
    Christy
     
    Christy Carlson | Senior Sales Manager | 206.443.2210 x1003| Fax: 206.443.2379
    SEATTLE REPERTORY THEATRE | www.seattlerep.org | 155 Mercer Street, PO Box 900923, Seattle, WA 98109
    In Lower Queen Anne at Seattle Center
    ON SALE NOW | Speech & Debate Jan 15-Feb 21 Jan 15-Feb 21 | Glengarry Glen Ross Feb 5-28

    Seattle Rep is closed on Mondays

    twitter.com/seattlerep | facebook.com/seattlerep | blog.seattlerep.org

    Please consider the environment before printing this e-mail 



    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Levi Sauerbrei
    Sent: Friday, January 15, 2010 2:07 PM
    To: Christy Carlson
    Subject: Re: [Tessitura Next Generation Forum] RE: Addressing addresses

    This input is coming from a database wonk, so its not entirely related to user experience, but with that caveat:

    The time restrictions on addresses are great but I think there must be a more elegant way to deal with that information both in the user interface and the database itself.  Currently, the default is to have each of the monthly check boxes filled which muddies up the front end and adds more data to the record.  I would love to see a system in which an address is assumed to be for all time periods unless there is an indicator that the user can see (it would be in a different color, for instance). 

    Also, the month by month selection is restrictive.  You should be able to add a very specific restriction that is either a one time occurrence or a recurring action.  Story time:

    A) A board member is going to Europe for three months.  During that time, they should not be sent any mailings. So I can enter it as "No Mail Delivery 04/15/2010 - 06/30/2010 - no recurrence"

    B) We have "Snow Bird" constituents who go to Florida every summer.  The restriction is then entered as "No Mail Delivery 06/01 - 08/27 - annual recurrence"

    As a bonus, the snow birds gave us their Florida address and we have entered it in Tess. The system then knows (by date) which address should be their primary one and displays the appropriate address on the constituent screen as well as in lists, extractions, etc. (For the DBAs in the room, I am envisioning a TX_ADDRESS_RESTRICTION table.)

    I second the vote for de-coupling phone numbers from addresses.  I know you can enter unrelated phone numbers now but under the current arrangement, its not an intuitive move.

    Finally I would absolutely LOVE a process that checks the format of the address against USPS naming conventions.  The user should be able to override it if they want, but if they spell out "Street" instead of "St" a pop up should alert them. We are currently using a script (which I think many others have as well) that auto-corrects certain items in the address but notifying the user at the time of entry is a good way to help enforce consistent data entry and ultimately helps get better results out of mailings.

    In the current system, I love the ability to click on the stamp to get an envelope.  I would love to see this expanded a bit so you can select from different types of documents.  Form letters for instance.

    "Thank you for your call today regarding _____. I hope that we have resolved the situation to your satisfaction.  If you have any further questions please contact <tessitura user's name and contact info>."

    This may have something to do with my love of Mad Libs.


    Can't wait to see how the constituent record evolves in the next generation!

     

    From: Marta Garczarczyk <bounce-martagarczarczyk9387@tessituranetwork.com>
    Sent: 1/15/2010 3:44:17 PM

    What I like about postal addresses currently is the ability to tie it a specific salutation, the seasonal months, and mail purposes. For the most part this works really well for me.

     

    However, I hate that addresses are tied to phone numbers because most people have cell phones that are not tied to an address. When an address gets inactivated if there is a phone it gets inactivated as well, when very well it’s an accurate one. It allows for a lot of user error if someone forgets to move the phone when inactivating an address. I think phones (like emails) need to be kept separate from addresses entirely.

     

    The story that happens to me most often relates to foundation and corporate records. For example, I need to pull an event list. Corporation ABC meets my select criteria, however N2 on that record is the contact for our corporate coordinator. I want to send the invitation to the CEO, COO, and CFO of that company. Right now I pretty much have to manually do that. I wish that I could create 3 salutations, 3 addresses tied to each unique salutation, select “Invitations” as my mail purpose and have them ALL pull into a list. When I look at a list of 20 I have to think to myself its really 40 because there are two people from each organization being invited. And I have to remember their names, and titles, and add them manually to my spreadsheet before I do a mailing.

     

    In an ideal world you would be able to mail to multiple addresses/salutations for one record. Though of course I don’t know how you would actually do that.

     

    What happens to me with foundations is usually that the giving is from the foundation but we want to invite the individuals at their home address. I can manually create a home salutation and address with an event mail purpose (which is what I do now) on their foundation record, but it seems clunky since I’m basically duplicating information from their individual record. I wish that there was a way to select the address I want to mail perhaps through associations? I can see that these constituents are related and while one record meets my criteria I am choosing the address from an associated record. This would also be helpful if I wanted to invite multiple board members from that foundation, I could then choose multiple home addresses or similar to the corporate suggestion have the ability to choose multiple names tied to the foundation address.

     

    -Marta

     

    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Andrew Recinos
    Sent: Friday, January 15, 2010 2:37 PM
    To: marta@smm.org
    Subject: [Tessitura Next Generation Forum] Addressing addresses

     

     

    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!




    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!
  • I'll second Christy's issue with the billing address.  This is especially a problem for us on the web where the patron doesn't read the messaging that tells them the address has to match the billing address and then calls us very angry that our website keeps rejecting their perfectly valid card.

    Controlled addresses can be an issue for us.

    Story:

    A patron calls the main box office to report a change of address.  The operator changes the address on the General tab, but also needs to make sure that all corresponding controlled addresses at all organizations in the consortium are changed.