> ## Documentation Index
> Fetch the complete documentation index at: https://docs.upflow.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Customer smart rules
> Apply customer-level automations in Upflow with smart rules built from a trigger, optional filters and a final action, and review the triggers available.
To discover and understand our smart rules logic and behavior, we invite you to read [Smart rules](/en-us/collection-and-collaboration/smart-rules/smart-rules) first.
Customer smart rules apply to any customers in Upflow unless they have been excluded.
Smart rules have three steps, out of which the first and third are mandatory, while the second is optional based on your needs: **Trigger > *Filter* > Action**.
## Triggers
Here are the triggers available for customer smart rules:
| **Trigger** | **Description** |
| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Customer is created | Triggered when a customer is created |
| Customer is created or updated | Triggered when a customer is created or updated. Updates relate to customer properties, including the outstanding balance, custom fields or workflow assignments. |
| Customer outstanding amount threshold | Triggered when a customer's outstanding amount exceeds or falls below a certain value. You will need to specify exceeds vs. falls below, as well as the appropriate value. |
| Customer rating threshold | Triggered when a customer rating exceeds or falls below a certain value. You will need to specify exceeds vs. falls below, as well as the appropriate value. (see examples at the bottom of this article) |
| Customer average payment delay threshold | Triggered when a customer's average payment delay exceeds or falls below a certain value. You will need to specify exceeds vs. falls below, as well as the appropriate value. |
## Filters
You can then add the specific filters/conditions this rule should follow to be applied. You can add as many conditions as you want, and those conditions will be additive (Condition 1 **AND** Condition 2).
* If you add multiple conditions, they will be additional:
Within the same field, multiple values will not be complementary\*, but independent from each other:
* If Country is US **Or** CA **Or** GB, then...
Filters apply to customer properties, including custom fields (cf. [Filters in Upflow](https://docs.upflow.io/en-us/upflow-configuration/organization-configuration/filters#filters-in-upflow)).
## \*Text type fields
For Text type fields, you will see the options "Contains" and "Does not contain". The value you enter in this condition must have the exact same wording both in the rule and at the customer level.
If in the rule you use "B2B" as value, the value in the customer custom field must be "B2B". If it's "b2b", it will not apply. If your rule is set on "Contains = B2B, B2C", it will not apply either, as the rule will look for customers with the exact value "B2B, B2C".
If you wish to use the same behavior for multiple values, please duplicate the rule. One rule per value.
## Actions
Finally, you can select which action this rule should perform. Each rule only supports one action:
| **Action** | **Description** | **Example scenario** |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| Assign users | Assign users to the corresponding customer. You can specify one user or use a custom field with the email address of the corresponding users. | Assign all the Sales and CSMs to their customers depending on a custom field value |
| Assign a workflow | Assign a workflow to the corresponding customer. | Assign workflows automatically depending on countries, payment behavior, etc. |
| Assign payment methods | Assign payment methods to the corresponding customer. | Assign the card payment method to all your SMB customers |
| Exclude from Upflow | Exclude the customer from Upflow. Be careful; you will not be able to import it back afterward. | Exclude from Upflow your internal customers |
| Send a notification\* | Send a notification to the person of your choice via the channel of your choice and with personalized content. | Send a notification to the customer's CSM when their outstanding amount is over their credit limit. |
When you are done, click the **Save & Close** button at the top right. Don't forget to give your rule a name so you remember what's in it. And activate it!
## Delete or deactivate a rule
## Apply the rule to existing customers
The rule you created will only apply to customers matching the rule’s trigger as detailed above.
For existing customers, you must ensure to use the option “Apply to all existing objects matching the rule’s conditions” when activating or reactivating the rule.
For more detailed examples, check [Smart Rules - Assignment Best Practice](/en-us/collection-and-collaboration/smart-rules/smart-rules-assignment-best-practice).
## When the customer rating threshold...
The rule trigger "Customer rating threshold" is usually meant to receive internal notifications to take actions, based on your customers' rating changes.
Note that there's no "equal to" condition today for this trigger. For the rule to apply, the rating has to actually exceed or fall below the selected rating in the rule.
The rules' creation will depend on the changes you want to be notified for.
When a customer rating threshold...
* Exceeds B, it will apply for any customers moving to rating A.
* Exceeds C, it will apply for any customers moving above C, so to A and B.
* Falls below A, it will apply for any customers moving from A to B/C/D
* Falls below C, it will apply to any customers rating A/B/C moving to D.
* Etc.