Code storage for Invitation pulls

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

 

 

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=====

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

 

 

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=====