Prospect Pool coding!

Kendra Johnson

Hi, RE NXT community. I'm 2-months into my RE NXT journey, and attempting to build robust Prospect Pools for each of the 6 foundations I partner with. (Health system where each hospital has its own supporting foundation, but could just as easily be a university with multiple colleges.) As I identify new prospects for each Foundation, I am currently using a Custom Field (Attribute in RE database view) Category named Prospect Pool, with 6 possible Values, one for each of my foundations. The problem I've created for myself is trying to THEN use a code to denote that a constituent should no longer be a member of that particular Prospect Pool (they've been disqualified for some reason) to ensure that as I run future queries the constituent no longer shows up (maybe 6 months from now through a trigger for giving $5K or something) on my list of individuals to assign to that Prospect Pool again. OR that there is a field I can use that shows up IN my query that tells me “No, no…you already put them in the Pool but the Foundation dq'd them.” I ALSO want to be able to report out on how many prospects have been ID'd for any pool at EOY, so simply removing the Custom Field is a no-go. Wow…that's a lot. Thank you for your thoughts. (Also happy to chat if you have a process you're willing to share for how you keep track of “buckets” of prospects.)

JoAnn Strommen

Two possible things come to mind right now.

1. A prospect status of disqualified. Use that as exclusion criteria in your queries for future lists. This assumes DQ'ed from one pool mean DQ'ed from all pools

2. For your attribute Category Pool A/B/C etc then use a table for description field with entry of say active or disqualified or whatever other options you might need.. With a table you can also exclude from queries.

Kendra Johnson

@JoAnn Strommen Hi, JoAnn! Thanks so much for your response and ideas. I'd thought about Status (and have been “playing around” in the Prospect Management tile a bit), but as you mention, I may not want to “blanket” DQ someone. They may still be a viable prospect for another of my Foundations. So yup…that will work in some cases for sure! Your second thought is really interesting. Right now, I have one single Attribute/Custom Field called Prospect Pool, then a drop-down for my 6 Foundations. Are you saying to create six individual Attributes, one for each of my Foundations? So one for Prospect Pool - X Foundation, Prospect Pool - Y Foundation, then use the Values drop-down (pulling from DB view) to denote things like Identified, Disqualified, Not Prospect at this Time, etc.? If so, I'm noodling on it (and thinking about what I need to buy my database director for Christmas to add 6 new Attributes and a handful of Values). Hahaha!!! Thank you!