> For the complete documentation index, see [llms.txt](https://eohelp.weaver.com.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eohelp.weaver.com.co/crm/details/customer-pool/pool-configuration.md).

# Pool Configuration

## 1. List Page

<figure><img src="https://1526800164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F50DeL6mO9sNbAZBSEdaN%2Fuploads%2FWEJNt2LKf4nVt0aEgP7h%2Fimage.png?alt=media&amp;token=6fc5b69e-e169-4be2-a786-377fa600441b" alt=""><figcaption></figcaption></figure>

## 2. Manage Pool

### 2.1 New Pool

Create a new pool

Step 1: Click on the \[New] button on the page

Step 2: Read more at[#id-3.-pool-configuration](#id-3.-pool-configuration "mention") to to learn how you can configure the new pool according to your needs.

<figure><img src="https://1526800164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F50DeL6mO9sNbAZBSEdaN%2Fuploads%2F4acnXl4bJySMfZYHHmrx%2Fimage.png?alt=media&amp;token=8987b38a-a73a-4a82-93e6-b2beff4b3aac" alt=""><figcaption></figcaption></figure>

### 2.2 Edit Pool

Edit the existing pool's configuration

Step 1: In the more settings \[···], click on the "Edit" button to the configure page.

<figure><img src="https://1526800164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F50DeL6mO9sNbAZBSEdaN%2Fuploads%2F1xIrL0SA8LpFkzhd7pU1%2Fimage.png?alt=media&amp;token=b0bda1d9-35ec-45ac-8677-af933618e4c9" alt=""><figcaption></figcaption></figure>

Step 2: Read more at[#id-3.-pool-configuration](#id-3.-pool-configuration "mention") to to learn how you can configure the pool to your needs.

### 2.3 Delete Pool

Although there is a \[Delete] button for all the pools, only empty pools with no customer data can be deleted.

Step 1: In the more settings \[···], click on the "Delete" button to delete the respective pool.

<figure><img src="https://1526800164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F50DeL6mO9sNbAZBSEdaN%2Fuploads%2FtleU7RuIC1P4WyY89zgM%2Fimage.png?alt=media&amp;token=02b1028a-4410-4f2f-baa1-6c156bd75f19" alt=""><figcaption></figcaption></figure>

## 3. Pool Configuration

### 3.1 Basic configuration

Basic information settings to define the group name, administrator and members.

<figure><img src="https://1526800164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F50DeL6mO9sNbAZBSEdaN%2Fuploads%2FOXnztUmaEJ9wHdDq3xHG%2Fimage.png?alt=media&amp;token=d7e51dd8-e0ac-4fa8-8204-ddc5370a3899" alt=""><figcaption></figcaption></figure>

* Group name: Required
* Administrator:&#x20;
  * Can be multiple users
  * Permission: To pick up, return, change the grouping, appoint the account manager, and perform the automatic allocation of all customer data in the pool.
* Members
  * Can be set for All users, or individually, or by department, or by role.&#x20;
  * Permission: Manage their own customers in the pool (view, edit, return, etc.), and at the same time, they can access customer data in the pool that do not have an account executive.

### 3.2 Allocation mechanism

It is used to set the member's permissions of the pool and the automatic allocation rule of the pool.

<figure><img src="https://1526800164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F50DeL6mO9sNbAZBSEdaN%2Fuploads%2F8w3SNBzt9FOfDu9xjYdI%2Fimage.png?alt=media&amp;token=2c6ed24b-2469-40c9-9955-d1be2e078b6d" alt=""><figcaption></figcaption></figure>

#### 3.2.1 Allocation

* Tick to enable.
* Purpose: Allows the members to pick up and return the customer in the pool, if its not enable then the member can only view and edit the assigned customers.

#### 3.2.2 Distribution of limit

1. Max. no. of customer whose cards were picked up by members

* Tick to enable
* When enabled, it defines the maximum number of customers that a member can pick up.

2. Cannot be picked by the same member within a customer returned to the pool (days)

* Tick to enable
* When enabled, customers who have been returned cannot be picked up by the previous account executive for a set period of time, but the administrator can assign a new account executive.

#### 3.2.3 Fast Allocation Rules

<figure><img src="https://1526800164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F50DeL6mO9sNbAZBSEdaN%2Fuploads%2FfCBdg4Gd9tbSnNjwBmxy%2Fimage.png?alt=media&amp;token=96d2e4ac-57cf-4c99-8bff-df03ea903f59" alt=""><figcaption></figcaption></figure>

1. SQL statement:&#x20;

* Execute the SQL statement and set the allocated personnel as the account executive for customers if the conditions of the statement are met.

2. Assigning personnel

* Determine the range of personnel to assign as the account executive if the SQL conditions are met.

3. Allocation Method

* Average: Customer that meets the SQL conditions will be distributed equally to the personnel assigned.&#x20;
* Limit the no. of customer allocated during the cycle time

<figure><img src="https://1526800164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F50DeL6mO9sNbAZBSEdaN%2Fuploads%2FGXW1Jbh8bsTpl9c9EBV5%2Fimage.png?alt=media&amp;token=10445e76-ac2c-42d5-ae01-bafd4960d89a" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1526800164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F50DeL6mO9sNbAZBSEdaN%2Fuploads%2FiK2fnpxdJEsTC6KBBPec%2Fimage.png?alt=media&amp;token=12fa7c5b-b733-471c-a171-92109324a0bf" alt=""><figcaption></figcaption></figure>

Step 1: Set the cycle&#x20;

Step 2: Specify the number of customers each assignor can get

Remark: When the set limit is reached, customer will no longer be automatically assigned to the personnel, but can be assigned by the administrator

* Prorated

<figure><img src="https://1526800164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F50DeL6mO9sNbAZBSEdaN%2Fuploads%2FBXN2SMQ5Nc6DesvvBDgo%2Fimage.png?alt=media&amp;token=185af98c-cc2d-4b4c-b36a-0cd4b7e18003" alt=""><figcaption></figcaption></figure>

Customer data that meets the conditions of the SQL statement will be distributed to the appropriate personnel in accordance with the set ratio.

* Remark:
  * Multiple allocation rules can be set for the same pool, prioritized from top to bottom.
  * If the conditions are not met, or if all staff have already been allocated the maximum number of customers, then the customer's account executive will be left empty.
  * The rules applies to the customers that are newly created, imported, returned, and changed grouping into the current pool.
  * New rules will only apply to newly added customers; existing customer will not be reallocated to other account executives.
  * Customers imported and newly created in a specific pool will be assigned to account executive based on the quick allocation rules established for that pool.
  * Customers that were changed grouping will be automatically assigned with an account executive according to the rules.

### 3.3 Recycling mechanism

The recycling mechanism is for customers whose contact log has not been updated for some time, automatically return to the pool for other members to pick up.  &#x20;

<figure><img src="https://1526800164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F50DeL6mO9sNbAZBSEdaN%2Fuploads%2FSuN5hrdpEAcEf6JoyCDO%2Fimage.png?alt=media&amp;token=b9343960-65ae-4dc1-92b8-bbcb6cd878d1" alt=""><figcaption></figcaption></figure>

#### 3.3.1 Recycle customers who have not added a new contact record after acquisition (days) \[N]

The customer will be returned to the pool if no new contact record are made on the Nth day after the customer has been appointed or picked up

i.e.: Customers assigned before 9:00 a.m. will be returned at 9:00 a.m. on the Nth day; customers acquired after 9:00 a.m. will be recalled at 9:00 a.m. on the \[N+1] day.&#x20;

#### 3.3.2 Recycle customers who have not added a new contact record since the last follow-up (days) \[N]:&#x20;

If the contact record is not added after N days, the customer is automatically return to pool.

#### 3.3.3 Recycle customer, month of created customer

Recycle the customers who have been not contacted for *xx days*, created within N months

xx days: setting refers to the two settings above

#### 3.3.4 Number of days in advance of customer recycle reminders

Recycling reminders will be made for customers based on the "Recycle customer, month of created customer".

When the customer's created date is within that month, only the corresponding account executive will receive the continuous recycling reminders.

## 4. All seas set

All, where customers who have not been assigned to a pool will be placed here as a general category.

Step 1: Click on the "All seas set" button

<figure><img src="https://1526800164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F50DeL6mO9sNbAZBSEdaN%2Fuploads%2FGvmY0QymfYxEXwO8uWoQ%2Fimage.png?alt=media&amp;token=dc5fc713-5934-4c5e-92a3-bacf193cd579" alt=""><figcaption></figcaption></figure>

* Only the system administrator can view and click the \[All seas set] button

Step 2: Assign the members of the all seas to allow them to view the customers in the pool.

<figure><img src="https://1526800164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F50DeL6mO9sNbAZBSEdaN%2Fuploads%2FCmtZ9pz1IbcY2QkF6spe%2Fimage.png?alt=media&amp;token=f26bccaf-077e-4f76-8c82-67537e4f3e24" alt="" width="375"><figcaption></figcaption></figure>
