20 results found
-
Alert Specific admin/user when CRM integration disconnects
Integration users used to connect Chili Piper to a CRM are commonly a specific user created for the purpose of integration and is linked to an unmonitored email address, which means that when CRITICAL issues occur such as a calendar disconnection, the proper admins are NOT alerted immediately to take action. This causes continual challenges for clients when we get disconnected and Chili Piper essentially stops working. NEED to be able to specify certain emails/users to receive email notifications upon disconnect.
1 vote -
Integrate with ClickSend SMS
Integrate with other SMS providers, not just Twilio. Take a look at ClickSend instead :)
1 vote -
Email or Slack Notification when a Salesforce Event fails to create.
We have an automation in Salesforce that triggers off the Event creation by chilipiper. When that fails, the rest of the automation fails to trigger. Since there is no notification from Chilipiper that the Event failed to create we often don't find out about the issues until many days after the automation was supposed to trigger. If there was some sort of notification from Chiliper that an Event failed to create we could investigate it immediately.
1 vote -
Have the option to turn on duplicate lead creation in Salesforce
I've had a number of prospects wish that we could create duplicate leads when a meeting is booked via Chili Piper. This is a gap that Calendly hasn't figured out. Many teams I work with have a team dedicated to deduping leads in their CRM.
1 vote -
Retry event update for rescheduled events
Upon an event being rescheduled, CP only attempts to update the event date and time once - if CP receives an error or the record is locked due to other updates happening, CP will not retry to update the date and time. This causes rescheduled events to not get updated to new date and time.
6 votes -
Have the option to add a delay in creating a lead in Salesforce when a prospect books a meeting.
We have more that one automation firing (from other systems) at the point a new lead gets created. This can sometimes cause duplicate records to get created in Salesforce. I would like the option to add a delay (wait 5 minutes for example) to the creation of a new lead at the point the prospect books a meeting. So that if the lead has already been created in Salesforce, chili will simply update the booking fields for the existing lead rather than creating the lead instantly.
2 votes -
Show all additional guests & their response status on the event in Salesforce
Right now, only the main guest and their response status is tracked on the salesforce event. However, there are frequent situations where there are additional guests other than the main guest and host added through instant booker and who also receive an invite. Visibility into each of those guests' names as well as their specific response status would be a huge win.
17 votes -
Ability to pass specific values to Salesforce fields from a form submission
Ability to pass specific values to Salesforce fields from a form submission without having to create form fields and mapping them to a Chili Piper form where we put the field as hidden and assign a value to it.
6 votes -
Integration into SFDC calendar
Ability to create schedules and calendar blocks on each users calendar based on a custom object in salesforce
3 votes -
Align "Outcome" with "Booking Status"
Booking Status values should be "Booked", "Not Booked" or "No Option Presented".We have high inbound volumes, of which a significant portion are outside of our ICP. They are routed to a separate landing page rather than presented with the ability to book time, so their status in Chili Piper is "No Option Presented." However, our DQs look identical to qualified leads that have "Not Booked" in Salesforce. Both have blank Meeting Types with "Not Booked" Booking Statuses, and it makes reporting, automation, and a general lack of understanding for my salespeople a bit more tricky.
4 votes -
Make it possible to set the Salesforce record type
Lead Record Type and Account Record Type (RecordTypeId) are used to distinguish between different types of leads/accounts in our CRM. These fields aren't available for mapping or setting as hidden fields in Chili Piper. It would be very helpful to be able to set this on the lead, since we use CP for scheduling calls for different record types.
1 vote -
Launch CP in SF objects with email fields, not just Leads & Contact pages
A customer uses a SF object with an email field and the calendar icon doesn't populate because we can only see Lead or Contact pages.
4 votes -
Append Event manually via Chili Piper if needed
It would be great to be able to adjust where the Event is connected in Salesforce, especially if the Event failed to sync to SF. The use case is that if reps attach an Event to the wrong Case or a SF Event are fails to create due to user error, the manual creation of a new Event is very time intensive. (E.g. if I see the rep entered the email address of the customer instead of the case id, I can edit the event to look for x case ID and then retry sync to SF.)
4 votes -
Populate meeting date in a contact/lead field
We want the ability to capture the "meeting scheduled date" as a value for a contact/lead object field. This would help with all kinds of operational flows in Salesforce and connected systems (like Hubspot).
4 votes -
Events: option to add notes after a meeting
After an onsite meeting concludes, email or text the assignee with an option to log notes to the activity record for the meeting. Especially helpful for onsite meetings at events where reps are not carrying their laptop.
3 votes -
Attach events to closed opps in salesforce
We'd love the option to have Chili Piper relate an event to a closed opportunity, especially in scenarios when we are using a smart booking link with that opp ID. This is helpful when we have a prospect return to us after being closed lost. We also have team members who work out of closed won opportunities (sale is final, but product needs to be delivered).
2 votes -
Add support for Salesforce Person Accounts
Currently Chili Piper cannot write to or create Person Accounts in Salesforce. These are unique objects that are essentially an "account" for a contact with no associated Company. Currently the only real option for customers who use Person Accounts is to have Chili Piper create leads and then the customer will convert them to Person Accounts.
2 votes -
Pass the SF username when Reassigning or Cancelling an Event through Salesforce Button
If an user goes to an event in Salesforce and reassign the meeting or cancel it, we don't have any way to know who did it there. We need to have a way to track it, and passing this username internally would be the best way instead of trying to modify the Updated By field.
2 votes -
Update Chili Piper Information Salesforce Fields
Currently if you book a meeting, it gets created in Salesforce as an Event. If you use the Reassign CP button, and change the Queue and Meeting Type, ALL additional Chili Piper API connected fields will NOT update on the Salesforce Event (with the exception of the top fields that are native to an Activity Object for Events i.e. Subject, Date, Time, Assigned To). We use this workaround of using "Reassign CP" if the customer has booked the wrong meeting type so we can ensure they receive the correct customer correspondence according to the type of training they will receive.…
2 votes -
Leverage SF integration user for booking links
Presently, if a licensed user is not connected to SF and is booking meetings with their personal booking link, Events won't write to SF. We'd like the ability to leverage the SF global integration to write Events, even if the specific user isn't connected to SF.
2 votes
- Don't see your idea?