CRM for Credit Unions
On September 12th, we had a special webinar with Dennis Smith, VP of Sales at UpCurve Cloud where we covered the top 5 ways that Sugar provides credit union functionality.
Thank you to everyone who participated in this webinar. Below is the video recording and Q&A.
- About UpCurve Cloud
- Top 5 Ways Sugar Integrates with Credit Unions
- Where Does CRM Fit?
- Product Availability and Interest Tracking
- Incentive Approval Management
- Interaction Management
Questions & Answers
Q: How is the Social Media (SugarCRM Hint) function charged by the record?
A: It is not. It is part of the license, so there is no limit on the number of queries that you can make within your SugarCRM Hint license.
Q: What email platforms do you work with?
A: Essentially, all platforms. We range from Microsoft Exchange to Gmail and Lotus Notes.
Q: Does it work on mobile?
A: Yes, Sugar has a free downloadable mobile app, which lets you access your CRM data from outside of your office. Sugar can be deployed both On-Premise (inside of your network infrastructure), or a Cloud environment, or even a private Cloud environment. But regardless, Sugar’s functionality can be accessed from mobile, both from Android and iOS devices.
Q: How long does it take to implement?
A: This depends on the use case. Very rarely has a credit union given us full access to completely overhaul their systems. We try to engage in a limited use case, whether it's a call center or a particular campaign and begin to build momentum. It's easier to start with a return on investment model, based on a proof of concept than it is to start an implementation from scratch. We have some engagements that are very quick, designed around one specific use case. These usually take a few weeks or a month. For a complete implementation process around all the different business units of an organization, it could take from six months to a year.
Q: Is this through an API connection?
A: We integrate CRM using three different ways. Our preference would be an API connection because it is in real time. In some instances, legacy applications don't give us the availability to do that. We can also integrate via a batch file or web services. Anyone of those three items is more than applicable. Usually, what we're doing is we're holding on to the member ID and issuing the query via API at the time of screen load so that we're getting real-time, up-to-date information.