Best Match Account Functionality

The best match account process is a filtering mechanism based on the rules configured in a specific order to get a record (lead/opportunity/cases/contact) to match to one account.

Creating Fullcast Policy Rules for Best Match Account

Fullcast policy rules are configured in the Salesforce instance.

  1. Log in to the Salesforce account.
  2. Click on the Setup and search for Custom Metadata types
  3. Click on Manage Records against Fullcast Policy Rules.
  4. Click New and start creating the rules.
  1. Enter label name which must begin with a letter and use only alphanumeric characters and underscores. The name cannot end with an underscore or have two consecutive underscores.
  2. The Fullcast Policy Rules Name is automatically picked which is the unique name used by the API and managed packages.
  3. Pick Criteria and Condition fields from the drop-down menu available.

Criteria and Condition Setting

Criteria

Fields Compared

Conditions supported

Field Compare

Field 1 on the Field 1 Object (Eg. Lead/Contact) to Field 2 on the Field 2 Object (which should always be an account)

AND, OR

Literal

Field 2 on the Field 2 object(Account) to String value provided on the Custom Metadata.

AND, OR

Tie Breaker

2 best match accounts

MAX, MIN

Fuzzy Logic

Unsure data fields

AND, OR

Field Compare Example

Literal Example

  1. String field needs to be updated only if the Criteria field picked is LITERAL.
  2. Field 1 Object is Lead or Contact which needs to be compared with the Account.
  3. Field 1 is the API field of the Field 1 object which needs to be compared API field of the Account.
  4. Field 2 Object should always be Account which is compared with Field 1 object.
  5. Field 2 is the API field of Field 2 Account which is compared with the API field of the Field 1 object.

📘

Tie-Breaker criteria

‘TIE BREAKER’ - Using the Field compare or Literal criteria if we get more than 1 Account, the TIE between the records has to be broken to find a single record.

  • More than one tie-breaker criteria could be used.
  • ‘MIN’ is used to order the records in ascending order.
  • ‘MAX’ is used to order the records in descending order.

Tie-breaker Example

The final account could be decided by the rules configured as shown.

Single Rule (One order only)

  • In the below setup we have 3 rules resulting in always one account as the output which is ensured by the Max condition.
  • Since it's based on a single rule we have order for all of them as 1

Multiple Rule (Multiple order)

  • In the below setup we have 2 rules resulting in always one account as the output which is ensured by the Max condition.
  • Since it's based on two rules we have order for all of them as 2

🚧

BMA Logic

If the rules don't create a single best match account, the BMA logic will select the oldest created account.

  1. Choose which operation to be performed from the drop-down menu for the field Operator. Use the below table to pick the correct operator based on the Field type being used in Field 1 and Field 2 in the rules.

Data Types

Operators Supported

PICKLIST

Not Equal To

MULTIPICKLIST

Equals To

Contains All

Contains Any

Does Not Contain

URL

Not Equals To

STRING

Equals To

EMAIL

Does Not Contain

Contains Any

Contains All

BOOLEAN

Not Equals To

Equals To

CURRENCY

Not Equals To

PERCENT

Equals To

DOUBLE

Greater Than

Greater Than Or Equals To

Less Than

Less Than or Equals To

DATE

No Equals To

DATETIME

Equals To

Greater Than

Greater Than Or Equals To

Less Than

Less Than or Equals To

  1. Enter the number according to which the rule has to be executed. For example, if it has to be executed first then the order number is 1. If it has to be executed third, then the order number is 3, and likewise.
  2. Module name carries the name of your choice. It is an optional field.
  3. Click Save to trigger and call the policy rule whenever necessary.

The below table gives an idea about the supported basic logical expressions and setup

🚧

Expression that will not work

Primarily with four fields in two logical group
Ex:
(Address OR Phone) AND (Name OR Domain)
(Name AND Phone) OR (Address AND Domain)
ADDRESS OR PHONE OR (Street AND City AND POSTAL)

1 OR 2 AND 3 (1 OR 3 )

Calling BMA from Process Builder

  1. The process builder needs to be created in order to sync the domain and call the BMA.
  2. Once the lead is triggered BMA should be fetched.
  3. BMA will be fetched based on the BMA rules.

Ignore BMA (Version 2.15)

Best Match Account can be ignored and the record could be sent to Territory Based Routing by checking the flag in the Routing queue.