Donor Portal

Options
We are beginning the process of looking at offering a donor portal for our donors. We are evaluating whether to use BBIS, build in another platform or purchase a vended product. What have other universities done? Here are a few questions...

Thanks for your help!

Amanda

amwood@uif.uillinois.edu
  1. What platform/software is the portal built with? Eg: Is it BBIS or any other platform?
  2. When was the portal launched/how long has it been live?
  3. What was your release plan (e.g. did you execute a soft release to select individuals/groups)?
  4. What was the size and composition of your technical/engineering team for building the donor portal?
  5. Did you need to increase staffing levels either for development work or ongoing maintenance?
  6. Did you consider hiring third-party contractors/consultants or was it completely built in-house?
  7. How many hours did you allocate (estimate) for development work prior to the initial launch? What was the runway (time period) from development work commencement to launch?

Comments

  • Hi Amanda,


    So I can't really answer too many of those questions. When I started at Carolina in 2013, we did have a c ustom .NET application that would allow donors to review their giving history. At the time we piggy-backed off Harris Connect login, and then later iModules.... but the application was on our servers.

    In 2017, we migrated our online giving platform from a custom .NET application to BBIS, and I built a custom part to show giving history (we still piggy backed off IModules authentication at the time, we did some customizations to handle that as well).


    At some point, I learned to hate developing custom parts, and learned about BBIS Custom Handlers, which allowed me to do more modern development using jquery on the front end, with the custom handler being responsible for returning the JSON Data. We switched over to BBIS authentication as well (with some first time user setup customizations, etc), and so the BBIS custom handlers were tied into that, so they could tell if the user was authenticated and who they were.

    Currently, our Donor Portal consists of 6 tabs. A summary screen, a "Give Again" tab where the donor can check one or more boxes for funds they'd previously given to, and then go to the donation form with those funds pre-populated... a payment history tab (where they can print review and duplicate receipts, or request a re-receipt (our e-receipting does not handle gifts with benefits)... there is a recurring gift tab, and a pledges tab (with a payment button)


    As we also built our Alumni Directory on top of BBIS but really mostly just using an Angular front end with BBIS Custom handlers on the back end, we also have a place where donors can update their profile. We do not use ANY out of the box functionality for the alumni directory or profile udpates. Profile updates are manually reviewed by staff in the General Alumni Association (even for non-alumni).


    Once I figured out how to work with BBIS Custom Handlers, developing in BBIS became a lot easier for me... all of this was my work except for the Angular-based alumni directory, but the profile udpate customizations are just regular html/jquery that lives on a BBIS page in an unformatted text part (which is also what the entire donor portal is)


    So it's been a work in progress over the course of my 8 years here!


    I've attached some screen caps of the donor portal tabs.


    Part of our plan this year is to make digital endowment reports available in the donor portal as well.


    Rick

    UNC-CH

    donor portal 1.PNGdonor portal 2.PNGdonor portal 3.PNGdonor portal 4.PNGdonor portal 5.PNGdonor portal 6.PNG

Categories