Hello,
Invitation code storage:
We are trying to determine the best place to store codes on records to pull lists for:
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
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,
HeatherSeattle Rep