Tips for Lead-to-Account (L2A) matching

Hey there! 

Ensuring that your Leads will be routed to the correct account in Chili Piper is a goal that can be achieved by setting the correct rules in an Ownership queue.

How have you been handling Lead-to-Account matching in your company? What is your setup?

The most common rule logic to be added to your Ownership queue would be the one below: 

Account Owner.Email = Assignee Email Address 

You can check more details about this configuration and the required setup here. 

You can also add rules to your Ownership queue that are associated with a custom field under the Account object. For example: 

Account.CustomField = Assignee ID

Let's also see an actual use case example where the queue rule below evaluates a custom field called CS Owner:

In this case, the flow would be the following:

• Let's assume we have a match to an Account. The queue evaluates the custom field (CS Owner in our example) under the Account object.
  
  
• Whenever a prospect is routed through this queue, we will check if one of the assignees enabled in the queue matches the ID set in the custom field.
  
  
• In our example, suppose that John Doe is the CS Owner for Acme, and his Salesforce UserID is 005abcde. This same ID will be set in the CS Owner field so that the queue rule will compare all assignee's Salesforce UserIDs with the string set in the CS Owner field. When identifying that John's UserID is 005abcde, we'll have a match with the same ID set in the CS Owner field.
  
  
• If none of the users in the queue match, the queue will "fail to match", and then Chili Piper will proceed to the next queue in the list for evaluation if you are using an inbound router or act as a Round Robin queue in case you are using the Ownership Queue booking link directly.

We would love to hear about your experience and how your company handles the Ownership flow! 😊