Skip to content

Routing

Categories

JUMP TO ANOTHER FORUM

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

7 results found

  1. The addition of an AI agent that can intake a prose style description of routing pathways and outcomes and translate that into a router framework. Ideally across all routing products.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Rather than creating and managing Rules in Chili, the request is to be able to manage them externally in a table, such as Google Sheets, and then have a way to call and update them in Chili Piper.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. The ability to enter a prompt and have rules built by AI

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. It would be very helpful—and in some cases game-changing—to provide a way to describe routing flows using code instead of the web UI. For complex flows with many routing rules and distributions (e.g., 10 sales teams in various regions or countries, speaking various languages), it's very inconvenient to maintain such a flow consisting of dozens of routing nodes.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. When you have several branches of logic, it's hard to know what each group is used for. Helpful to be able to name the group so it's easier to update later. For example, Group 1 name could be US Territory.

    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)
  6. 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)
  7. Currently, when a rep who is in a queue has their calendar blocked off for PTO Chilipiper marks them as OFF and they are not selected in queues until their calendar block ends. For example, if I'm on PTO this week with my calendar blocked for all day events and someone is trying to book a meeting for next week, I won't be next in queue and am marked OFF, even though my calendar is empty the following week. This feature needs to be smarter and recognize that I'm bookable next week, even if my calendar is blocked today.

    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

    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?