Just wondering who out there has used WealthEngine: Prospect Research Technology? We have it and are using it just fine but it was suggested that we import the WealthEngine information into Tessitura. Just wondering if anyone had any experience doing this, what fields you imported (Inner Circle, P2G Ratings...), and if it seemed helpful or worth the time and money to do? Any information/experience you could share would be a great help.
We just got it ourselves and are about to start using it. From the feedback I got, nothing is imported into Tessitura since the data changes so often. We'll be probably keeping the information in a Access file. Feel free to email me jmccoy@pacificsymphony.org - maybe we can compare notes when we get more into using it!
STC used WealthEngine to screen our database and we imported the data into Tessitura this year. We imported the Five Year Gift Capacity Rating, Propensity to Give, Birth Month/Year, and the three Planned Giving ratings as attributes. We relabeled the ratings so that they would be easier to understand at a glance. This info probably could go somewhere else (like Research), but attributes seemed the most feasible for our IT department. IT also uploaded the actual WE table into Tessitura, which allows us to pull lists on other criteria like Influence and Inclination without actually importing the data to individual accounts. I'm afraid I don't know too much about this second part but STC's Tess guru, Brian Graham (bgraham@shakespearetheatre.org), might be able to tell you more.
We haven't had a lot of opportunity to play around with the ratings yet, but primarily we plan to use it to research Planned Giving prospects.
Please e-mail me at mnimke@shakespearetheatre.org if you have further questions. Thanks!
We did a Wealth Engine screening of about 50,000 constituents a few years ago. I only imported the capacity and prelim capacity into a custom tab which included other 'moves management' type information. I made sure it was clear that the information came from a specific wealth screening on a specifc date.
One can't assume that this information is 100% correct so for us it was just a starting point for more research. Our staff are aware that the Wealth Engine capacity is by no means their actual capacity.
I also made sure to create a help document that I added to Tessitura explaining the Weath Engine screening and data so future users can read what its all about.
Dale
Leah -
We did Wealth Engine a few years ago as well and we imported a lot of the information into local but distinct tables and then set up some custom keywords that allowed come of the information to be used as list criteria. We also made a custom screen to display a lot of the WE information. The place where we used it most (especially when the information was fresh) was printing some of the ratings and capacity on our phone room lead sheets. This allowed our phoners to have a little more information about the person they were calling.
We found that we always had to take Wealth Engine with a grain of salt which is why we didn't want to import it into anywhere we wouldn't be able to easily identify as Wealth Engine (i.e. we didn't import the birthdates into our birthday field. We found many instances where it got the age of some of our important donors wrong and aged them significantly!).
HTH,
HeatherSeattle Rep
We also do annual screenings from WealthEngine. We intend to replicate most of the information off of tables mapped into a custom screen. We also would like to have the 5 year giving capacity ratings immediately visible to our Development officers. Any thoughts on how to go about doing this? The attributes idea is good but we are consider using constituencies that would then be read and translated into a symbol on the header. Constituencies would also allow Development easy front end updating of this dynamic verified/unverified data using the Constituency report feature. Has anyone else done anything similar? (I posted this question in another spot. Apologies in advance for the duplicates if you are reading this a second time.)
We also do annual screenings from WealthEngine. We intend to replicate most of the information off of tables mapped into a custom screen.
We also would like to have the 5 year giving capacity ratings immediately visible to our Development officers. Any thoughts on how to go about doing this? The attributes idea is good but we are consider using constituencies that would then be read and translated into a symbol on the header. Constituencies would also allow Development easy front end updating of this dynamic verified/unverified data using the Constituency report feature. Has anyone else done anything similar?
(I posted this question in another spot. Apologies in advance for the duplicates if you are reading this a second time.)
Maylee,
I guess it depends on your own company's business practices but for us, we use constituencies to denote a constituent's relationship to the company so we probably wouldn't put something like a wealth engine capacity there.
If you do integrate this data into the constituent record - outside of a custom tab - I recommend that it is well documented so that future users know where the data came from and what it means.
Also you should consider security issues. If its in the header and constituencies it could be available to the entire company depending on your setup. Especially since the data is unverified, you may not want it visible to all.
One final thing, if you do want this data in the header, you could easily pull it from a custom table, it doesn't have to be a constituency to be in the header.
Thanks Dale for your quick response.
Documentation is always good advice.
Regarding security, header would only be seen by Development control group.
Question on custom table - is just the initial setup done on the back end? Can data refreshes/updates be done on the front end? Constituency is definitely an odd pathway but once the programming is done, can be keyed off of the Tessitura table that can be updated by the end user.
A custom tab can be set up so that information in a custom table can be updated via the constituent record.
You can also make some of the data view-only and some updateable if you want.
We went that route. We put the Wealth Engine data into the tab as view-only and then had separate fields for "actual capacity" (verified capacity) so that the Wealth Engine data was never altered.
Timely conversation here! PlayMakers just got WE data and I was chewing on the best way to handle it. Thanks Tess forums!
Carli
Hello,
I have been tasked to import Wealth Engine data into Tessitura. There is only 1 column we need imported (P2G Ranking). I am not sure how to updated/add records to the database. Does anyone have any insight into what a script would look like to import the P2G Ranking? The information I have is the customer number and the ranking.
Thank you for any replies regarding this request,
Aaron Richards
Hi Aaron -
It all depends on your organization. As mentioned earlier in this thread a lot of people load it to a new local table and then build custom views/screens to see the information. Again, this depends on what your organization wants to do with this information, how they want to view it, etc. There is no standard place in Tessitura to upload WE information to.
Good luck,
Heather
COCA is looking into Wealth Engine. Has anything changed in the last 2 years since this posting that would improve the import capabilities? Or have other products researching prospects replaced Wealth Engine?
Hi Shelley,
We've been looking into this as well. As I understand it, WealthEngine is working on a new product due later this year that will tighten integration with Tessitura and allow automated import, at some extra cost. That's about the extent of my knowledge about it though--I'm sure they would be happy to tell you all about it!