69 results found
-
Tables - Sorting
Anywhere a table is displayed in Fire, I would like the ability to sort by a column.
My first priority would be Assets since they are where changes happen most often:
- Teams
- Distributions
- Rules67 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}4 votes -
Send a notification when the CRM actions are stuck in pending status
Send a notification to the Admin whenever the CRM actions of a Concierge record is stuck in pending for more than X minutes.
2 votes -
Adding comments / sticky notes to a flow
Not sure if this is the correct place for this, but it would be super helpful if you could allow the creator of a flow to add comments to each routing rule. This can be in the form of a sticky note for example and could be a way to distinguish each flow.
2 votes -
Include form values in redirect URL as part of the URL instead of as Query Parameters
I'm trying to redirect to landing pages based off the locale of a user so they get redirected to a page translated to the correct language. The locale is typically part of the URL and not a Query parameter. It would massively reduce the complexity of our routing if we could simply specify a spot in the URL to place a value from the submitted form.
For example: https://ourwebsite.com/<locale_code_here>/thank-you
1 vote -
Names for groups in rules
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 -
Can we removed Meeting Type that does not have schedule link from Handoff Router
Can we removed Meeting Type that does not have schedule link from Handoff Router
1 vote -
QA/UAT Environment Setup for Concierge Routers Testing
We currently have 20+ advanced concierge/routers and need a dedicated QA/UAT environment to test them under the same conditions as in the production workspace.
Issue:
• The application does not support copying between workspaces, requiring us to rebuild everything manually, which is inefficient and time-consuming.Request:
• Enable a QA/UAT environment where concierge routers can be tested exactly as they function in production.
• Provide a solution to copy configurations between workspaces to streamline testing and deployment.1 vote -
dynamic population for the matched account and owner fields
Leandata does this and was a blocker for a customer
1 vote -
Ability to Change Team in Distribution after Publishing
When creating a distribution on the Fire Platform, we assign a team, but then it is not possible to change the team without re creating the whole distribution.
We need to be able to change the team in the distribution
5 votes -
Automated Team Management via CSV or API Integration
Enable team members and routing updates via CSV upload or API integration,
1 vote -
Job feature within Distro
Would love to replenish accounts for an AE/SDR who has less than 150 accounts. (e.g. if an SDR has <150 account in "working", then we route them more accounts"
1 vote -
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
7 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 -
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 -
Export Logs - Distro
Add export logs functionality to run the analysis per the routed lead.
2 votes -
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 -
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…
3 votes -
1 vote
- Don't see your idea?