All ideas

Customer requested ability to " only include the 2 questions regarding “Residence address” and “Work/Work address” in determining eligibility. If the member fails, we would complete the validation on our end." After these two questions, for exampl...

CUCollaborate could append a code to attribute an application to a source (eg CUCollaborate): To pass an source identifier over to MeridianLink we would need to append a ‘referralsource’ URL query parameter to the end of the URL – this then fills ...

The descriptions and wording of lead originations in JoinCU is creating confusion and overcomplicating the data. For example, leads are described as coming from 'Own Site' even though they have no implementation on their website. The leads may hav...

To create the functionality for clients to customize the business logic in order to change the display of reason of eligibility. So for example, "you are eligible to join because you live in 21490349" to "You are eligible to join because you live ...

Client wants to use the dashboard as a CRM for their request letters. If they want to make changes to their SEG letters they want the ability to reupload. Clients will also have SEGs that want to manually sign, or if they have in-person business d...

I would like to see the demographics of members associated with a particular branch.

Could we show social impact by branch?

When there are business development reps for multiple different regions, we received feedback that this would be a more useful tool if we could configure who receives notifications based on the region of the targeted SEG.

We should expose the SEG application as an API

Customer uses a Business Intelligence tool and wants to automate the process of exporting JoinCU user activity reports. Having scheduled reporting would allow them to automate the process and ingest those excel files and take out the extra work th...