July 20, 2012 at 19:34Workle has classified its customers' clients
The issue of protecting personal data has always been relevant for any startup, it is no less important for Workle developers . Let us explain the “Vorklovsky” specifics: the site is a platform for the exchange of information and data (including personal, such as phone numbers) between Workle users and managers from partner companies.
Our users have customers to whom they offer various products (insurance, loans and tours abroad). Managers of insurance companies, for example, are in the habit of tracking when a CASCO, CTP, etc. policy expires in order to propose an extension in advance. So it is with banks and tour operators - project partners.
Where is the guarantee that the client will remain with the Workle user, but will not use the services of the same insurance directly? It is in our interests not to allow such a situation in any case.
The developers proposed to solve this problem as follows: to classify the personal data of customers using call routing.
Here's how it goes. In the process of processing the transaction involved three parties: a client who wants to purchase a product; a Workle user who intends to sell this product to him, and a partner company manager who processes applications and, in fact, draws up the product for the client.
The Workle user communicates with his client, clarifies his wishes and identifies needs, and then sends a request to the partner company through the Workle website. It is processed by the manager of the company, after which he contacts the client to clarify the parameters of the product and agree on the timing of the application. The manager calls a special phone number that is processed by the call routing service. Then it is automatically connected to the answering machine, which communicates the rules of communication with the client, after which the manager follows the instructions of the answering machine (“To call the customer, click the star, application number ...”, etc.). The database call routing service determines which client the manager wants to call and connects to it.
This solution to the problem of database protection, according to Workle developers, is most effective for a site of this specificity. Although, in order to set up the entire routing process, much more needs to be taken into account: for example, to foresee all possible situations (erroneous entry of the application number, the client is not available for calling, the application is closed by the Workle user, etc.) and adjust the answering machine. However, the result is worth it - managers of the partner companies of the site will not be able to contact customers of Workle users without the knowledge of the latter.
You will learn more about protecting the customer base from the video .
Our users have customers to whom they offer various products (insurance, loans and tours abroad). Managers of insurance companies, for example, are in the habit of tracking when a CASCO, CTP, etc. policy expires in order to propose an extension in advance. So it is with banks and tour operators - project partners.
Where is the guarantee that the client will remain with the Workle user, but will not use the services of the same insurance directly? It is in our interests not to allow such a situation in any case.
The developers proposed to solve this problem as follows: to classify the personal data of customers using call routing.
Here's how it goes. In the process of processing the transaction involved three parties: a client who wants to purchase a product; a Workle user who intends to sell this product to him, and a partner company manager who processes applications and, in fact, draws up the product for the client.
The Workle user communicates with his client, clarifies his wishes and identifies needs, and then sends a request to the partner company through the Workle website. It is processed by the manager of the company, after which he contacts the client to clarify the parameters of the product and agree on the timing of the application. The manager calls a special phone number that is processed by the call routing service. Then it is automatically connected to the answering machine, which communicates the rules of communication with the client, after which the manager follows the instructions of the answering machine (“To call the customer, click the star, application number ...”, etc.). The database call routing service determines which client the manager wants to call and connects to it.
This solution to the problem of database protection, according to Workle developers, is most effective for a site of this specificity. Although, in order to set up the entire routing process, much more needs to be taken into account: for example, to foresee all possible situations (erroneous entry of the application number, the client is not available for calling, the application is closed by the Workle user, etc.) and adjust the answering machine. However, the result is worth it - managers of the partner companies of the site will not be able to contact customers of Workle users without the knowledge of the latter.
You will learn more about protecting the customer base from the video .