Tweet
Hi,
We run a call center within our company through which we call clients of various companies. However, these companies want us to keep their data separate. So we run multiple instances of CRM and in the long run this does not seem sustainable. For example, we now have 6 companies, so we have 6 CRM instances. Currently, we solve it so that when a lead comes in, we identify within the logic of the collection application which customer it is and then we save this lead into the appropriate CRM so that our operators can handle it.
The ideal situation would be if we have one CRM instance connected to multiple databases. So we would still identify who the lead came from, we would write it to the appropriate database, but the operator would actually be working on one CRM and maybe switching between contexts somewhere in the menu.
The problem is that the companies that hire us to handle their leads do business in very overlapping areas. So each company requires us to keep the data of their clients we call in a separate database. So we have a set of operators who have X browser windows open with X instances of the same CRM, but each of those instances is connected to a different set of contacts. It was still good at 2-6, but we're growing and it's not possible to run, for example, 20 instances of the same CRM. I will add, we are in the European market with GDPR. For example, if a database was leaked somewhere (for example, hacked) and got out, it would be a huge problem if, for example, the data of two companies appeared within one DB dump. That's why we're addressing this, we're getting pretty brutal audits from them to show that we're not mixing their clients' data with competitors.
The ideal situation would be if we have one CRM instance connected to multiple databases. So we would still identify who the lead came from, we would write it to the appropriate database, but the operator would actually be working on one CRM and maybe switching between contexts somewhere in the menu.
Is this possible with EspoCRM?
Thank you.
We run a call center within our company through which we call clients of various companies. However, these companies want us to keep their data separate. So we run multiple instances of CRM and in the long run this does not seem sustainable. For example, we now have 6 companies, so we have 6 CRM instances. Currently, we solve it so that when a lead comes in, we identify within the logic of the collection application which customer it is and then we save this lead into the appropriate CRM so that our operators can handle it.
The ideal situation would be if we have one CRM instance connected to multiple databases. So we would still identify who the lead came from, we would write it to the appropriate database, but the operator would actually be working on one CRM and maybe switching between contexts somewhere in the menu.
The problem is that the companies that hire us to handle their leads do business in very overlapping areas. So each company requires us to keep the data of their clients we call in a separate database. So we have a set of operators who have X browser windows open with X instances of the same CRM, but each of those instances is connected to a different set of contacts. It was still good at 2-6, but we're growing and it's not possible to run, for example, 20 instances of the same CRM. I will add, we are in the European market with GDPR. For example, if a database was leaked somewhere (for example, hacked) and got out, it would be a huge problem if, for example, the data of two companies appeared within one DB dump. That's why we're addressing this, we're getting pretty brutal audits from them to show that we're not mixing their clients' data with competitors.
The ideal situation would be if we have one CRM instance connected to multiple databases. So we would still identify who the lead came from, we would write it to the appropriate database, but the operator would actually be working on one CRM and maybe switching between contexts somewhere in the menu.
Is this possible with EspoCRM?
Thank you.
Comment