Hi -
Our partner is building out our org, and a question has come up about the best way to capture client information when they register for a workshop, or request services. The way it's being set up is a client will click a link on our website, fill out a form with their contact info, choose from a dropdown menu the service they're requesting, and a case will be created, notifying the relevant employee. Apparently, some nonprofits use leads rather than cases to capture client data and keep track of their interactions with the company.
Would folks be willing to share what you use within NPSP to do this? Our clients might sign up for one aspect of our services, then return for several more groups, classes, or one-on-one sessions - some have moved on to volunteer with us, or represent our agency at events. We'd like to be able to see their full history with us, as well as be able to respond efficiently when they reach out or sign up for something.
Thanks for sharing any experiences or thoughts!
@Caren Knox As you said NonProfits makes different uses of each of the Object but my proposal always is as follows, you can check if helps your scenario
- Leads = People who fill out your form showing "interest in any of your workshop or services" and after they meet certain criteria they are converted and become "the person who will take the workshop or service"
- Cases = Questions, Complaints, Suggestions, Follow-ups from your Customers or Members about your Workshops or Services which you can also create a Lead but Cases are not the best practice to use for that.
In the scenario that you do not have any "acceptance criteria" for those who register you can not use Lead and go and create Contacts with a Status but I would suggest going thru Leads, Why?
Because you would be able to differentiate those "who are interested" from those "who really took or participate in the Workshops or Services" which are your contacts
