---
title: Customer Distribution Rules
slug: contact-center/customer-distribution-rules
docTags: 
createdAt: 2025-10-15T04:20:46.350Z
---

## 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

1. 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>).
2. Customer data is first ingested into the **Ameyo Refresh Table** and then transferred to the **Customer Prospect Table**.
3. The configured rules analyze the data in the **Customer Prospect Table**.
4. Data that successfully matches a rule is **moved** to the **Data Table Definition** of the Process and is **deleted** from the Customer Prospect Table.
5. 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**:

1. Navigate to the **Process Tab** and select a Process.
2. Click on the **Customer Distribution Rules** tab.
3. Click the **"New Rule"** button.
4. Enter the **Rule Name** and **Rule Description**.
5. 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"**).
6. 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.
7. Click **"Save"** to create and enable the rule.
