60 results found
-
When reassigning do not notify prospect
When reassigning a meeting, don't send out a cancellation notification to the prospect. only change the meeting owner to the new assignee - this way it doesn't effect the prospect
6 votes -
Write related Account to Lead in Distro
Stamp related Account/Contact to a field on the Lead Object.
3 votes -
'Text me now' option when brought to Booking Page
Text me now. The form currently has 3 options: "Call me now", "Start a video call", or "Schedule a meeting". We personally will not use "Start a video call". A preferred option for us and for our prospects is "Text me now" rather than a video call. So the client is in control of their experience by requesting to be called, texted or schedule appointment. We will upgrade our account from Concierge to Concierge Live w/ calling and texting if this feature becomes available. I'm sure I'm not the only one requesting it and that could benefit from it.
8 votes -
Customizable Internal Email Notification
Allow the internal email being sent to the new lead owner. This will allow for the email to include various fields the internal teams want to know without having to click into the record and dig around.
Example:
Subject:
New {!routed lead.leadsource} lead! {!routed lead.company}
Message:
Lead Link: https://seesaw.my.salesforce.com/{!routed lead.leadidcaseinsensitive_c}of Students (Opportunity): {!routed lead.opportunityofstudents__c}
Total Enrollment: {!routed lead.numseesawstudentstotalc}
Name: {!routed lead.name}
Role: {!routed lead.rolec}
Organization: {!routed lead.company}
District Account ID: {!routed lead.districtaccountr.accountidcase_insensitivec}
District Account Name:{!routed lead.districtaccount_r.name}1 vote -
Capping for Concierge
It would be great if Chili Piper can find another team or user when an assignee has reach a certain level of meeting booked.
Cap the assignee and distribute the other meetings to one other person or a team of users.
1 vote -
Don't require Redirect on unsuccessful booking in Fire Concierge
In Fire Concierge, remove the requirement for a redirect on unsuccessful bookings. Instead, allow users to remain on the same page with a message or guidance on how to complete their booking.
Since we are using this in-app, this would enhance user experience by minimizing disruption, enabling users to easily retry without navigating away from the booking page.
This change will streamline the booking process, reduce user frustration, and improve the overall flow, ensuring a smoother and more intuitive interaction when issues arise during the booking attempt.
1 vote -
1 vote
-
Fallback when rep's are OOO in Concierge
Allow for coverage if a rep or reps are OOO in Concierge.
1 vote -
1 vote
-
Export Logs - Distro
Add export logs functionality to run the analysis per the routed lead.
1 vote -
Distro/Form Concierge - Path Branching
It would be fantastic to build out more customization in routers rather than always having to go in a straight line by rules. More complex routing options like A) branching (based off a single rule or if/then criteria) would make the organization and rule building within routers much easier to follow (and educate others on).
Also, that ability to have rules trigger or route after another rule would be helpful. So basically first it checks for something like A) market segment and then B) checks territory. You could then build the secondary logic under the first branch to better understand…
2 votes -
Mark held meetings that were unqualified to credit back a rep
Weighting in Salesforce and Chili Piper differ because in Salesforce it's based on meetings held whereas in Chili Piper it's based on meetings booked. To make it easier to have the two match, there should be a way in Chili Piper to mark a held meeting as unqualified and credit the user back a meeting. Currently we can credit back no shows - but not unqualified held meetings.
2 votes -
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 votes -
Set fallback actions for when integrations disconnect
I wish when the status changed, there was a way to get an alert or automate a downstream change. If someone's calendar connection breaks, for example, we need to remove them from the cue. Right now, we just have to go into the user list and check everyone periodically.
1 vote -
Distro for Hubspot
Use Distro for Hubspot
4 votes -
Redirect links for deactivated users
The ability to redirect a personal booking link, for when employees leave a company but have emails out using personal booking links
8 votes -
Do not consider inbound meeting count if booked on a weekend/extra hours in the day
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 -
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 votes -
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 vote -
Upon round robin reset - continue in list order rather than move to top
Each time the round robin is reset, it starts over again from the top of this list of reps. This leads to reps at the bottom of the list often getting left out, an waiting all month / time period to be reached. It would be more fair if the round robin, even after being reset, would continue with the 'up next' rep in the list rather than bumping back up to the top.
1 vote
- Don't see your idea?