66 results found
-
Have the ability to reassign a call to any user available regardless of team
When a user needs to reassign a call to another team member, they should have the ability to pick from all team members if needed, not just team members who were part of the distribution the call was originally scheduled.
This should list anyone in the distribution the call was scheduled from first, and then, if no one is available, list any remaining person available.
1 voteYou can now Reassign to other distributions or teams in the new reassignment flow. More details here.
-
dynamic population for the matched account and owner fields
Leandata does this and was a blocker for a customer
1 vote -
Write related Account to Lead in Distro
Stamp related Account/Contact to a field on the Lead Object.
3 votesThis can be solved with the Distro Variables feature. To get set up, check out this help article.
-
Ability to Change Team in Distribution after Publishing
When creating a distribution on the Fire Platform, we assign a team, but then it is not possible to change the team without re creating the whole distribution.
We need to be able to change the team in the distribution
6 votesYou can now swap out the team in a Distribution without rebuilding it from scratch. This makes it easier to respond to org changes while keeping your routing logic intact. Once you update and re-publish, your stats will reset for a fresh start.
-
Monitor Multiple Fields for Triggers
Currently, the Distro Trigger can only monitor 1 field for "When a specific field is updated." Having the ability to monitor multiple fields would be a big lift for us. We have a Primary Field, which we are using, but being able to monitor multiple fields would be a very nice to have.
Through the Entry Rules, we can make sure only the right Leads/Contacts are routed, but with only a single Trigger field, it makes it difficult to capture the right Leads/Contacts.
Ideally it would be similar to the Field Update interface where you can add multiple fields to…
3 votesYou can now Trigger Distro with multiple fields! Gif attached.
-
Allow configuring order based on recency when matching against opportunities
We use ownership rules heavily and our rules match against opportunities and their owners. Opportunities in our Salesforce instance can have different owners. Because Chili Piper randomly selects an opportunity to match against currently, this leads to inconsistency in terms of how the ownership rule is applied, which undermines the effectiveness of the rule. Please provide the ability to control the sort order in which opportunities are pulled back (or provide a sane default - always use the most recent opportunity based on the criteria) so that this rule can be relied upon.
2 votesThis is now possible in the Matching Hub using Lead to Opportunity and Contact to Opportunity Matching with filters and tiebreakers!
-
Add 'View Log' button in Distro routers
Add a button at the top of a Distro router that takes you directly to the linked Logs, next to 'Preview Flow'. You can do practically everything from within Flow Builder now except navigate directly to the Logs.
1 voteThe Distro Router links to its related logs. Screenshot attached!
-
Relative date math
Being able to say route here if within 60 days of X date field.
1 voteAvailable in the rule builder! Screenshot attached.
-
Distribution Hours
Ability to set the hours distribution (in our case, contacts) should run. For example, a contact is picked up by CP at 6pm local time, we want the distributor to only route that contact the following day during working hours. This is so that we can track SLAs accurately in Salesforce, as we do not expect our reps to be working at 6pm. Putting a busy block on one's calendar works for the weekend but not after hours on working days.
1 voteThis is now available in Distro. In the assign and update ownership node, you can toggle on and off during working hours. More details here.
-
Notify all members of a group queue when a Lead/Contact is assigned through "Queues for prospects who didn't take action"
When a prospect is assigned through "Queues for prospects who didn't take action" to a Owner from a queue booking link, all members should be notified about it and not only the Lead/Contact owner. It can give a better visibility to all members of this group queue.
1 voteIn Concierge Fire, you can now send a message when a lead is assigned that does not book. From here, you can cc an email and that email can be an address all users are on. Screenshot attached.
-
Add route to a Campaign
Ability to add a route in a Salesforce Campaign. Campaigns help Marketers track the results of a Campaign by providing important KPIs.
1 vote -
Write to Salesforce custom field when matched L2A
Would love the ability to match a Lead to an Account and not route to the Account owner.
Being able to write to a field on the Lead object which indicate it's matched to a certain account but hasn't been routed yet.3 votesThis can be solved with the Distro Variables feature. To get set up, check out this help article.
-
SLA feature in Distro being able to mark a field value as blank or clear it.
Distro being able to mark a field value as blank or clear it. Helpful not to have to build formula fields for this in sfdc. We have existing prospects coming back all of the time. Don't want to build out a formula field.
1 voteYou can set a field as null in Distro. Screenshot attached.
-
Ability to easily PAUSE reps from distirbutions for leave
Want ability to pause a rep in queues rather than individually remove from each queue. the main issue is with such a large sales org, there are a lot of instances where reps either forget to mark their calendars as OOO or unexpectedly have to go on leave, and the only solution for us is to completely take them out of each of the RR.
5 votesThis can be solved by setting a rep to zero 0% weight in the Distribution, and they will then be paused. Here is how.
-
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 votesAvailable in the rules asset.
-
Delete first queue rule
Currently not possible to delete first queue rule in a list.
2 votesSolved in DCP with rules and teams
-
Queue Rule config with logic tree
Instead of writing the conditions with AND and OR, it'd be easier to describe the queue rule with a logic tree. Some major routing software offers it and it's fool proof than writing conditions with AND and OR.
1 voteThis is now solved in our Rules available in the Demand Conversion Platform.
-
Don't use commas to separate queue keywords
Use a visual or other indication of a separate queue keyword so that commas in picklists can be used for routing.
1 voteSolved with rules and the new pill state.
-
Drag and drop users in queue order
It's very time intensive to manually click up or down to rearrange users in large queues.
1 voteYou can drag and drop the order of users in teams
-
Search all open opps for matching criteria
Search all open opportunities for a match to Queue criteria rather than just last modified.
13 votesThis is possible on the Fire platform in the Matching Hub. The Match to Opportunity tab has the option to change the filters (e.g. show Closed Won opportunities not just open for post-sales use cases) and tiebreakers (e.g. prioritise based on the created or close date instead of last modified). https://help.chilipiper.com/hc/en-us/articles/33532253394323-Matching-Leads-Contacts-to-Opportunities-and-Cases-with-Chili-Piper
- Don't see your idea?