Customer Distribution Rules

overview the customer distribution rules feature automates the segregation and distribution of customer data within the system its core purpose is to replace the centralized "customer segregation" rule functionality and manage customer data at the process level itself, rather than the system level this feature ensures that data used for dialing and customer contact is processed according to predefined logic for the specific operating business unit (process), enhancing control and data relevance key benefits process level granularity enables the uploading and distribution of customer data specific to a business process, providing greater control and isolation of data pools automated data routing rules are applied at runtime to automatically match, move, and validate customer records from a temporary staging area (customer prospect \<process id>) to the active customer tables data integrity if any customer data fails to match a distribution rule, it remains idle in the prospect table for review, ensuring no data is improperly actioned dynamic lead management allows for creating, updating, and migrating customer records across leads based on specified conditions functionality this feature operates via the "customer distribution rules" tab, accessible in the process settings data storage & flow each process maintains its unique and separate data structures, specifically an ameyo refresh table (ameyo refresh table \<process id>) and a customer prospect table (customer prospect \<process id>) customer data is first ingested into the ameyo refresh table and then transferred to the customer prospect table the configured rules analyze the data in the customer prospect table data that successfully matches a rule is moved to the data table definition of the process and is deleted from the customer prospect table unmatched data remains idle in the customer prospect table and can be manually exported or exported and extracted for analysis rule actions rules determine the final fate of customer records in the prospect table the two primary action types are "new" action creates a new entry according to the satisfied conditions "upload" action handles existing and new data by simultaneously performing three actions creates a new customer record if it doesn't exist updates existing customer records available for distribution updates and migrates a customer record if it is found in a lead other than the specified one prerequisites process creation the process must be created to make the customer distribution rules tab visible backend configuration backend configuration must be done to specify where the customer data (from sources like api or ftp) should be inserted into the unique process level tables customer data presence customer data must be uploaded (via csv ) or linked (via sources like staging database ) into the relevant process's tables usage instructions the following steps describe how to add a new customer distribution rule navigate to the process tab and select a process click on the customer distribution rules tab click the "new rule" button enter the rule name and rule description define the conditions click the "add" button in the conditions section select the attribute (e g , phone1, email, attempts) select an operator (e g , =, !=, <) provide the corresponding value add multiple conditions if required and select the logical operator ( "match any of the following" or "match all of the following" ) define the action click the "actions" tab select the type of action ( "new" or "upload" ) select the campaign and the lead onto which the customer data should be moved click "save" to create and enable the rule