WealthEngine

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,

Heather
Seattle 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.)

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.

Dale

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.

Dale

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.

Dale

Timely conversation here! PlayMakers just got WE data and I was chewing on the best way to handle it. Thanks Tess forums!

Carli