Hi!
Is there a way to track any changes and/or updates to specific constituent records? Ideally, it would be great if users could create a list of specific accounts and receive notification whenever any changes are made to an account on the list. I would like to be able to track certain prospects' ticket or subscription purchase, as well as any changes to addresses, contact level (email still ok?), etc.
Do any other development people have ways that they track specific constituent records?
Thanks!
Alexis
Thanks for the responses! From what I can tell, the Constituent Audit Report is great for monitoring email, phone, address, etc. changes. However, it doesn't tell me when single tickets have been purchased. I am interested in tracking the activities and purchases of specific prospects and can't figure out the best way to do this without having to check each and every prospect's record?
If you're looking to track ticket purchases for a group of prospects, I would investigate the Performance Report in the Development folder. We use a slightly modified version of this and run it using a list of prospects and VIP donors. Make sure to make your list dynamic.Dale
Unknown said: If you're looking to track ticket purchases for a group of prospects, I would investigate the Performance Report in the Development folder. We use a slightly modified version of this and run it using a list of prospects and VIP donors. Make sure to make your list dynamic.Dale
We use the Attendance by Performance report in a similar way. We have lists that it is run against and schedule it to send as weekly/monthly as needed by the recipient.
Dale,
That report is great, thanks for the tip! Here's a scenario that I'm not sure would work with that list, unless I run it daily? A prospect purchases a ticket on 6/19 for a performance on 6/20. Is there some kind of alert that I can get when particular constituents (from my prospect and VIP list) purchase tickets that will automatically pop up? Or do I just need to run this report every day using my dynamic list?
Thanks again for all the responses. Can't wait to learn even more at the Tess conference!!
Alexis,
This solution definitely gets away from the standard report methods folks have described before, but if it is a situation that you will be dealing with regularly it might be worth some customization. If I had to tackle this, I might look at creating a process in the database which created a CSI whenever one of your VIPs made a purchase. Or one that ran every 15 minutes or so which created a CSI when it found someone on your list who bought a ticket.
The CSI would then be assigned to the concerned party. This still doesn't deal with a notification being sent immediately, but it sounds like CSI is the best place in Tessitura to track what you are talking about.
You could also look at the SQL server sending an email when such a ticket purchase was made. But again, that would involve some customization.