• Replies 4 replies
  • Subscribers 413 subscribers
  • Views 23 views
  • Users 0 members are here
Related

Code storage for Invitation pulls

Jamie Roff
$organization

Hello,

Invitation code storage:

 

We are trying to determine the best place to store codes on records to pull lists for:

 

  • Corporate contacts
  • Foundation
  • Individual

 

These records need the ability to be easily extracted via List Builder and/or Extractions for invitations to events.  Our internal suggestions are “Attributes” or “Interests.”   If you use “Attributes” or “Interests” or if you have any suggestions of another location, can you please respond with rationale?

 

 

Thank you,

 

Jamie Roff

  • $organization

    Jamie -

    We use Attributes to track people who are opening night invite list (I think that is what you are looking for, sorry if I'm off base!). Because we have different department with different opening night lists (and multiple spaces) we have one attribute for our main stage opening night and have departments as the drop downs. This allows our marketing department to pull lists and distribute them for proofing to the various departments.

    We've run into instances where someone just wants a person added for X show and not on the regular opening night list and for that we have a CSI for one timers that we link to the actual performance that they are supposed to be invited to.

    This allows us to set up those vendors who need extra tickets to one show without cluttering up our opening night list.

    Hope that helps,

    Heather
    Seattle Rep 

  • $organization

    Thanks Heather!  

     

    _______________________________________________________
    Jamie Roff
    Manager of Development Systems
    Orange County Performing Arts Center
    600 Town Center Drive   Costa Mesa, CA 92626
    T 714.556.2122 x4212   F 714.549.1352   E JRoff@OCPAC.org

    http://www.ocpac.org/facebook.com/OCPAC P Please consider the environment before printing this email. 

    From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Heather Kraft
    Sent: Friday, September 24, 2010 5:02 PM
    To: Roff, Jamie
    Subject: Re: [Tessitura Development Forum] Code storage for Invitation pulls

     

    Jamie -

    We use Attributes to track people who are opening night invite list (I think that is what you are looking for, sorry if I'm off base!). Because we have different department with different opening night lists (and multiple spaces) we have one attribute for our main stage opening night and have departments as the drop downs. This allows our marketing department to pull lists and distribute them for proofing to the various departments.

    We've run into instances where someone just wants a person added for X show and not on the regular opening night list and for that we have a CSI for one timers that we link to the actual performance that they are supposed to be invited to.

    This allows us to set up those vendors who need extra tickets to one show without cluttering up our opening night list.

    Hope that helps,

    Heather
    Seattle Rep 

    From: Jamie Roff <bounce-jamieroff2912@tessituranetwork.com>
    Sent: 9/24/2010 11:42:05 AM

    Hello,

    Invitation code storage:

     

    We are trying to determine the best place to store codes on records to pull lists for:

     

    • Corporate contacts
    • Foundation
    • Individual

     

    These records need the ability to be easily extracted via List Builder and/or Extractions for invitations to events.  Our internal suggestions are “Attributes” or “Interests.”   If you use “Attributes” or “Interests” or if you have any suggestions of another location, can you please respond with rationale?

     

     

    Thank you,

     

    Jamie Roff




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

    



_______________________________________________________________________
    Privileged And Confidential Communication. This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC ?? 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.
  • $organization

    Hi Jamie

     

    We do a lot of opening night/invitation based activity, using the Activity module for rsvp management.

    Our model is that each business area (eg media, government, arts ‘industry’, corporates, donors etc) creates their own list, then these are combined into a Master list by a central coordinator.

     

    We use Constituency codes to provide initial segmentation and internal ‘ownership’ of a record, then each area uses Attributes in ways that suit their needs to id who they consider for invitations.

     

    Some areas use an invitation ‘level’ Attribute (ie A, B, C where A is ‘always invite’, B is literally B-List, etc); others use a shared cross-organisation ‘VIP Arts Interest’ attribute that defines art forms of interest to any customers we consider invite-worthy! This is pretty flexible and can be used to indicate interest in specific repeating programs or events, as well as genres.

     

    Having said that these are all just base-line values for the List creation - its usual for the resulting Lists to then be manually reviewed, with some names deleted and others added, based on the specialist knowledge of the Constituents in each area and the nature of the event.

     

    Regards

    Peter

     

    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

    http://www.sydneyoperahouse.com/logos/LogoBlack.gif

     

    From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Jamie Roff
    Sent: Saturday, 25 September 2010 02:47
    To: Peter Nelson
    Subject: [Tessitura Development Forum] Code storage for Invitation pulls

     

    Hello,

    Invitation code storage:

     

    We are trying to determine the best place to store codes on records to pull lists for:

     

    • Corporate contacts
    • Foundation
    • Individual

     

    These records need the ability to be easily extracted via List Builder and/or Extractions for invitations to events.  Our internal suggestions are “Attributes” or “Interests.”   If you use “Attributes” or “Interests” or if you have any suggestions of another location, can you please respond with rationale?

     

     

    Thank you,

     

    Jamie Roff




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. 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=====
  • $organization in reply to Peter Nelson

    We  just started using constituencies for these.  We chose that over attributes because of the ability to set a date range

    Here are 2 use senarios that come to mind:

    1. you know someone is leaving a company at a future date, you can mark it with an end date & not have to worry about remembering to remove the attribute.

    2. Invitations are based on a date range related to the gift date, you can add or update the constituency to reflect the benefit period.

    ~Sadie

    Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

    Sadie Martin Treese

    Accounts Receivable Coordinator/ Tessitura Project Manager

    Pittsburgh Public Theater

    621 Penn Avenue

    Pittsburgh, PA 15222

    (412)316-8200 ext 769

    Fax: (412)316-1624