6 results found

1. Fuzzy Matching for Account Matching

   Adding the ability to search on multiple factors for Account Matching in addition to just email domain. This would solve for situations where companies have multiple accounts for the same company (typically different country locations).An example would be searching based on email domain + another field such as country.This would also allow for matching to accounts for public email domains as well.

   37 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Released  ·  1 comment  ·  Rules  ·  Delete…  ·  Admin →

2. Greater/less than date field rules in Distro

   Currently it is not possible to create a rule in Distro where "Date Field is greater than X Date." You have to create a formula field in Salesforce to calculate the UNIX date and then reference that field in your Distro rules. Being able to reference date fields directly opens up a lot of doors for routing and simplifies the process.

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Rules  ·  Delete…  ·  Admin →
   Released  ·  AdminAlly Hardesty (Product Operations Manager, Chili Piper, Inc.) responded

   Available in the rules asset.

3. SFDC Account Teams Routing

   We have customers like Shopify and Avalara moving away from multiple lookup fields to Account Teams and would like this to be supported in our routing/rules.

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Rules  ·  Delete…  ·  Admin →
   Released  ·  AdminAlly Hardesty (Product Operations Manager, Chili Piper, Inc.) responded

   This is now available for all products on the Demand Conversion Platform! Check out more details on custom matching here and specifically on routing to an Account Team / Opportunity Team using Chili Piper's Custom Matching here.

   
   

4. Allow rules logic to determine assignee when multiple owners match in a queue

   Imagine you have an ownership queue that has both a rule for Account ownership and Contact ownership with rules logic of "1 OR 2". Currently if there is a match for both rules, the assignee is chosen based on who is first in the physical order of the reps in the queue's assignee list. This means that if the Contact owner is listed first they will be assigned the meeting even if the Account owner matches and the rules logic lists the Account ownership rule first. This also means that in order to guarantee that Account ownership is prioritized over Contact ownership that two separate ownership queues must be created.Instead, what I propose is that we determine the assignee in these situations based on the rules logic. If the first rule is for Account ownership, the second rules is for Contact ownership, and the rules logic is "1 OR 2", then it should route to the Account owner because that rule is listed first in the rules logic. This will eliminate the need for customers to create multiple ownership queues and create a more intuitive setup.Reference this JIRA: https://floatingapps.atlassian.net/browse/CPP-6856

   Imagine you have an ownership queue that has both a rule for Account ownership and Contact ownership with rules logic of "1 OR 2". Currently if there is a match for both rules, the assignee is chosen based on who is first in the physical order of the reps in the queue's assignee list. This means that if the Contact owner is listed first they will be assigned the meeting even if the Account owner matches and the rules logic lists the Account ownership rule first. This also means that in order to guarantee that Account ownership is prioritized over… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Rules  ·  Delete…  ·  Admin →
   Released  ·  AdminAlly Hardesty (Product Operations Manager, Chili Piper, Inc.) responded

   This can now be customized in the flow builder where the order can be set in the flow. Available in form concierge on the Demand Conversion Platform.

5. Customize DQ routing based on logic

   Ability to customize disqualified leads IF they hit certain logic. Example - If an inbound lead/prospect hits a queue and is OWNED by a CSM, ability for us to DQ them and IF they hit that logic, route them to specific landing page.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Rules  ·  Delete…  ·  Admin →
   Released  ·  AdminAlly Hardesty (Product Operations Manager, Chili Piper, Inc.) responded

   Available in the Demand Conversion Platform with Form concierge. Using the flow builder you can create a customized experience and redirects.

6. Duplicate Rules

   Instead of starting from scratch each time for rules, it would be great to be able to duplicate a rule from a previous row and just swap out the value.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Rules  ·  Delete…  ·  Admin →
   Released  ·  AdminAlly Hardesty (Product Operations Manager, Chili Piper, Inc.) responded

   In the Demand Conversion Platform, you can now duplicate Rules!