Available in Version 3.1 and up
The Assignment Matching feature ensures that similar records are assigned to the same user. Here are a few common use cases for this feature:
- Assigning leads with the same email address to the same user.
- Assigning different prospects from the same company to the same user.
- Assigning cases from the same account to the same user.
Assignments made prior to enabling this feature are not matched against.
Follow these steps to setup assignment matching:
- Navigate to a Kubaru Router and click Edit.
- Check the Enable Assignment Matching checkbox.
- Configure the below fields:
|Matching Field||The field that records are matched on. If two records have the same non-null field value, they are considered a match.|
Formula fields can be used to configure more complex matching criteria.
|Match Against Assignments||Made by this router only: Only matches against assignments made by this router. Made by any router: Matches against assignments made by any router.|
Assignments will only be matched if the Match Against Assignments value is the same in both cases. For example, a record assigned with “Made by any router” will not match against one with “Made by this router only”, even if the matching field value is the same.
|Match Within Last||Matching assignments must be made within this time frame to go to the same person.|
|Count Null Matches||Determines whether multiple records with a blank value in the provided Matching Field are considered a match.|
|Assign Matching When Unavailable||Determines if matched assignments should be made even when the recipient is marked as unavailable.|
|Assign Matching When Out Of Office||Determines if matched assignments should be made even when the recipient is out of office.|
|Assign Matching When Logged Out / Idle||Determines if matched assignments should be made even when the recipient is logged out of Salesforce or idle in their session. Only applicable when Logged In Members Only is checked.|
|Match Against Active Only||Determines whether assignment matching should operate against previously assigned records that are now “inactive” in accordance with your active record definitions.|
- Click Save.