45 results found

1. Ownership queues

   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 is if CP found the right owner before the lead record was created it should also find the right owner if the prospect does not book a meeting because Rev Ops is not a user in CP.

   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… more

   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

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

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Grouping Assignments across Teams in Distro

   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

   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

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

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Dummy Ownership Enabled in Routers

   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

   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

   Idea  ·  0 comments  ·  Advanced Matching  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Don't update Account or Contact Owner through QFPWDTA

   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 in an Ownership queue listed in DTA. Or we create an admin toggle that says, "allow all Account owners to be notified if the contact goes through QFWDTA?"

   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… more

   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

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

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Create 'Quickview' on hover for queue assignees

   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

   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

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

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close