Iris CRM is a user-friendly CRM that is rooted in simplicity and usability. It’s a cloud-based platform designed to work as ERP for agents and consolidate day-to-day operations into a single platform. It also features tools that support residual income operations, merchant onboarding, lead and lifecycle account tracking, and numerous other integrations designed for growth and productivity. In a nutshell, Iris CRM functions as an end-to-end sales, customer support, and residuals management solution that can easily manage payments within a single platform, thus eliminating the need to invest in multiple systems.
Capabilities |
|
---|---|
Segment |
|
Deployment | Cloud / SaaS / Web-Based, Mobile Android, Mobile iPad, Mobile iPhone |
Support | 24/7 (Live rep), Chat, Email/Help Desk, FAQs/Forum, Knowledge Base, Phone Support |
Training | Documentation |
Languages | English |
Responsive Support team. Decently customizable to fit our needs.
I wouldn't say I like the global search feature.
We use IRIS CRM to maintain our book of merchant and agent partners.
Customer service from lead Tech Mohammad was essential to getting this up and running.
Intake took a very long time with a lot of back and more forth. Did not understand why they don't have an archive of all processors they work with.
Saved me hours of reconciliation time with MIDs and agents.
I like the most of the API and the experience that the sales reps can have. It does a lot for residuals which is a nice feature with your sales CRM. It is easy to create a good workflow for employees. They have a support rep named Eric; he is fantastic.
The dialer's recordings are awful. Call routing is not very sophisticated. There are no listeners for merchant tables. I would say my only real complaints are the dialer. It is below expectations, especially for what people pay for that feature. The dialer metrics are unreadable, and there are no API endpoints to get that data. It is not good. I would also say that permissions are not straightforward. For example, if you have a group setting, it will override label settings in documents. It is the right move, but tracking down a permissions issue can be next to impossible. Also, some minor things, like being able to hide statuses by group, not just the entire status category. Email triggers only go out to assigned users on a lead; it would be cool if there were an ability to email a class on a trigger whether or not they're set to a lead The tiny amount of permissions regarding people and their ability to view merchant records and financial information is highly annoying. For example, if a support rep is assigned to a lead, they will be assigned to that merchant record and can view the financial statement. How about permission to disable that for specific users? Or control that on a more granular level. That is a huge miss. Also, when financial information is pulled at ~3 AM, it will create a new lead record if a lead does not have a matching MID, which can be frustrating to clean up. A section should be made where administrators or accountants can connect leads with the correct merchant record before the system creates a blank. We have spent a lot of time cleaning this up because some banks get MIDs at the very beginning of the underwriting process, and some get them at the very end, so if the timing is off, you may have hundreds of leads in your system which have no info but a MID
It's a sales CRM and financial tool all in one.
You can integrate it with your website using their API, you can create leads, signature, many features to manage tabs and leads.
Bad layout, it takes a while to return something through their API, I had to ask them to return the lead ID (it's obvious) in a separate variable in JSON because they just added in a string like: Your lead ### has been created.... they already changed it.
Registration form for a Merchant.