Skip to content

Routing

Categories

JUMP TO ANOTHER FORUM

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

94 results found

  1. It would be helpful to add a rep to a specific team when someone is on vacation and have their availability be specified for that team rather than universally, so they are only booked when the person they're covering is on vacation and not taking away other potential bookings from that person when they're back

    1 vote

    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  ·  Teams  ·  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. 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)
  3. When working with 50+ queues due to large territories or broad teams/larger organizations, updating queues becomes a tedious and time-consuming task. It would be great if you could group queues together, and change a queue setting or add/remove a particular rule from the entire group at a time. Alternatively, you could select from a list of queues which to update, and trigger a mass update without a specific group defined.

    21 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  ·  1 comment  ·  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)
  4. 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)
  5. 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)
  6. You can refer to ticket #18327. When someone fills out a web form, CP looks for the owner and finds a matching account but no lead or contact record. Salesforce creates the lead and assigns it to a non user like Rev Ops. If the prospect books a meeting then it works perfectly, it assigns it to the right person as the owner. However, if the prospect does not book a meeting when it goes in it finds the lead is assigned to Rev Ops so it is triggered to round robin out to the next BDR. The ask here…

    1 vote

    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)
  7. A user that is apart of multiple teams where assignments across rulesets are factored into algorithm. A true round robin for a single router.

    1 vote

    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)
  8. Currently if a customer does not have an ownership queue on in the router but is routing based on account rules we fail these queues. Could we potentially have a switch in the router instead of having to tell customers to create a "dummy ownership" queue? Something more intuitive because customers are not able to figure this out on their own.

    1 vote

    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  ·  Advanced Matching  ·  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. Create a Double Round Robin option so that an AE can be paired with any SE on a call

    83 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  ·  5 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)
  10. 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.

    4 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)
  11. There is a feature in QFPWDTA where the Account owner or the Contact owner is notified of the submission, even if the rep does not have a Chili Piper license. Even when an Ownership queue is not listed in DTA, the owner will still be notified.This is a breach of security as we should not be notifying anyone about Chili Piper data if the admin did not provide consent to notify the person who does not have a Chili Piper license. ---The functionality should be to notify the owner ONLY if the rep has a Chili Piper license AND is…

    1 vote

    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)
  12. When looking to see which reps (or otherwise) are assigned to a particular queue, it would be great to have a 'quickview' pop-up feature when hovering over the "Assignees" icon, that quickly identifies who is assigned to a said queue, similar to the pop-out view in Reports > DistributionBenefit: Would save an extra step in having to click 'Edit' in order to view the queue assignees and would be fairly simple to create via a .mouseover or .hover function in jquery.

    1 vote

    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)
  13. 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)
  14. 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

    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  ·  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)
1 2 3 5 Next →
  • Don't see your idea?