Skip to content

Routing

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

94 results found

  1. If a queue is built out with weighting, lets say one rep is 5 meetings for everyone elses 1, when calibration "current level" resets to zero, as soon as they take one meeting we bump the other person up next in the queue because the person set to 500% is at .2 level which is higher than zero. Customers (home depot for example) want the reps set to 500 to take 5 meetings before allowing the other rep to take one. we should set calibration up to understand this

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Idea  ·  0 comments  ·  Fairness  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. When implementing Chili Piper across different pages, we would like to have the option to hide the X for some popups (e.g. when embedded in a DOM element), and not for others. Currently, this is only achievable using the REST API or with CSS for the entire workspace. It would be very useful to have a JS option for the JS API to hide the X.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Idea  ·  0 comments  ·  Form Router  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Investigating  ·  0 comments  ·  Rules  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CRM Router  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Rules  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. There is a situation in our org where the sales persons work extra hours/weekend currently with the round robin routing they will have to wait for others to catchup weightage that's no bounty for the extra effort for the sales people.

    Is there a way to build a system that only consider round robin for the office working hours and extra hour/weekend meetings aren't counted?

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Fairness  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Currently we use weights to try to ensure reps are load balanced from a schedule perspective, however, we've found this to be insufficient and end up needing to manually reassign meetings between reps. We'd love for Chili Piper to be able to automatically reassign meetings between a pool of reps as schedules firm up.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Currently, any manual calibrations made to a queue are not automatically reflected in other queues across a group. An admin must instead add/remove meetings to every queue in a group manually to keep them balanced.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Fairness  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Currently not possible to delete first queue rule in a list.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Queues  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. We run into a common problem with very small queues (for example, our AE1s, of which we have <20) and during certain times of day (i.e., morning huddles or lunch periods) where the queue itself is devoid of "Available" reps. When this happens, we have a separate process we would like our SDRs to follow to find a warm body for the live transfer; however, in their haste, they often do not even notice that the queue is empty and suggesting an "Unavailable" AE -- and will pull them out of rotation when they cannot take the call. When this…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Remove the calibration-effect of a user if they're removed from the queue

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Algorithms  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Many customers look for deduping in their routing software to help keep their CRM data as reliable as possible. For example, LeanData offers deduping. We have seen many Distro cross-sell opportunities fall through because Distro cannot do deduping.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Be able to bring over existing meeting queue rules to distro to make the build easier.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Queues  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Allow for Distribution based on availability in either Queues for Prospect Who Don't Take Action or in Distro.

    There is research that says a lead has the highest intent within 7 seconds. Therefore, if Chili can distribute within 7 seconds, it should be able to distribute to only reps that are available.

    Chili Piper is already looking at calendar availability of reps; therefore, it should be able to use that logic in Queues for Prospects Who Don't Take Action or in Distro.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Algorithms  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Leads are for closers and your closers are busiest. This lead system allows a potential client to select a time and then the round robin is based off who is available. This puts more appointments in less effective closers appointment books. My top Sales guy only received 3 leads out of like 60 because of this. You need to have an option to do either. If I cannot get this honed in with weighting and teaching my top sales guy how to leave the most sought after appointment times open to me, we will be canceling your product. I would…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Idea  ·  0 comments  ·  Algorithms  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Hide router testing link if SF leads not generated to ensure that we can't attempt to test something that definitely won't work.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Idea  ·  0 comments  ·  Form Router  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Let's say we ask for CRM on our form and we only want to let people book a meeting if they choose 'Salesforce', and if they choose anything else, we don't want to let them book a meeting.Right now, we have to put a rule in every queue associated with this router to say 'CRM = Salesforce', and that means updating a ton of different queues as we have queues for every territory.It would be much more efficient if we could build a 'Disqualification' queue where we could just say 'If CRM isn't Salesroce', don't show the ability to book…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Idea  ·  0 comments  ·  Form Router  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Conditional rules that make it easier for users to be auto-included in specific ownership queues if they are in the same router with other Queues with Rules

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Idea  ·  0 comments  ·  Queues  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Please add a feature that prompts me to save a queue before exiting. I have lost too many queues thinking I saved them when i in-fact didi not

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Idea  ·  0 comments  ·  Queues  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Handoff workspaces need to add functionality to read multi-select checkboxes from the HubSpot Forms integration.Currently Chilipiper cannot read if multiple checkboxes are supplied on a HubSpot form and you cannot do reliable routing based on form submission checkbox preferences.I've included an example image below. If more than one option is chosen this is not honored in the handoff router. Additionally Chilipiper then writes the incomplete value back into HubSpot causing data errors.This is critical functionality!!!

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Idea  ·  1 comment  ·  Form Router  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?