Lead Uniqueness Check -- 2

Task: Service for Checking Lead Uniqueness Between Agencies and Developers Without Sharing Full Contact Information Main Objective: To create a service for verifying the uniqueness of leads between agencies and developers using contact data hashing to ensure privacy. Modules: 1. Data Retrieval Module: - Automatic connection to CRM to retrieve data on new leads. 2. Manual Data Upload Module: - Ability to manually upload data, such as CRM exports, for further processing. 3. Data Hashing Module: - Conversion of contact details (name, phone number) into hashes. - Consideration of various data formats (spaces, parentheses, dashes, etc.) for accurate recognition of identical contacts. 4. Tag Assignment Service: - Automatic assignment of tags in the CRM for a lead if it already exists in the database and is linked to another developer or agency. - The tag indicates the specific agency or developer currently working with that lead. 5. Rules Verification Service: - Flexible configuration of rules that define further actions with the lead. For example: - If a lead is already being handled by one developer, further work with it must cease. - If a lead is being handled by another developer, the work may continue depending on established agreements with agencies and developers. 6. Database Interface: - Visualization of information for each lead, including: - Who is handling the lead (agency/developer), - Lead registration date, - Current lead status. Process Flow: 1. Data Upload to CRM: - Connect to the CRM for automatic hashing of the new lead's data and transfer it to the database. For the initial stage, we can use manual data uploads. 2. Data Hashing: - Contact details are converted into hashes to protect confidentiality. 3. Lead Handling Rules: - If the lead already exists in the database, it is tagged to indicate that another developer or agency is already working with it. - Rules are configured to determine what actions should be taken based on which developer or agency is currently working on the lead (continue work, stop, etc.). 4. Uniform Data Formatting: - Normalize data during hashing (removal of spaces, parentheses, and dashes in phone numbers, etc.). 5. Notifications for Partial Matches: - If only some data matches (e.g., the name), the system issues an alert for manual verification. Additional Requirements: - The database should store information about developers and their contacts. - Use of no-code and low-code solutions like Airtable and Zapier to simplify and automate the process. - The first CRM we will start working with is kommo CRM. - There should be the capability to connect to other CRMs in the future.