Share product ideas and upvotes with our product team
It would be great to have a feature in the "Analyze" portion of Fin AI Agent, to mark that I've "Reviewed" a conversation. Or maybe even leave notes for myself and other managers to see outside of the context of the conversation, only in the context of the “Fin Performance” or “Optimize.” Thinking like UI green check marks I can select when I’ve reviewed something, or flag a conversation to revisit and work on later. We've been reviewing all of our Fin "sent to teammate" to see how we can get more of those resolutions from Fin. Sometimes the answer is perfect, and the customer just doesn't read... And I'd like to somehow notate that I've "Reviewed" a conversation so I don't review it again in the future
As you can’t add public holidays into the office hours, we’re having to manually adjust the office hours every time there is a support closure I think it would be helpful to be able to multi select days in this view, rather than having to add a new office hour line for every day, and then just omit the day of the closure. It’s a 1 minute job that ends up taking ages because you have to duplicate loads
The content for the product tour should have the possibility to come from an external source as well, such as an API. This allows us to centralize all help materials—tooltips, product tours, and other content—in one place for easier management.
User storyAs a product owner of a multi-tenant SaaS platform,I want to provide a unified product tour experience that dynamically adapts to the feature set available for each customer,so that I can deliver relevant onboarding without having to maintain separate tours for each customer variation. DescriptionWe have a SaaS product where all customers access the same user interface via their own subdomains (e.g., customer1.domain.com, customer2.domain.com). While the UI remains the same, each customer has a unique set of features enabled based on their subscription or use case.For example, if a product tour contains three feature-based steps: If a customer does not have Feature A, the related tour step should be hidden. If a customer has Feature A and Feature B, only the relevant steps for those features should be shown. If a customer has all three features, they should see the complete tour. So we would like to design a single, flexible product tour that: Automatically adapts to show only the steps relevant to the features available for that customer. Supports conditional logic so that we don’t have to create a separate tour for each feature combination, which is not scalable. Incorporates page-level logic based on CSS elements: If a targeted CSS element (e.g., a .button, .tab, or .widget) doesn’t exist on the page, the tour should: Fallback to another step targeting a different CSS element (if configured), or Skip the current Pointer or Post step entirely. Use a Workflow to decide the next step in the Product tour (If this, then that)
The possibility to change from only seeing chat timestamp in days to be able to see the exact date and time (as you get when hovering over the “3 day” stamp.
It would be great if the suggestions could be filtered or manually grouped so that subject experts only have to review the content that relates to them. The current system is only effective for if one person is able to review them all.
With the new CX Scores, would be great to be able to use that data field as a trigger for kicking off automated workflows. Example- Ticket or Conversation that received a 1 or 2 rating - automatically be able to send to a specific team, or alert @mention who we might need to review and potentially outreach to the customer again in hopes to improve or resolve their experience. Right now its manual and reactive by going through reports.
There is really two parts to my idea. For one, we find it really annoying to have to create a tag to use a csv file to send a one off email through the Outbound section. We don’t want our workspace to get overloaded with a bunch of tags just because we are sending an email. Although you can use audience rules, a lot of the times we have to do email=xxx.com or email=xxx.com for how many people we are wanting to send to just to get around from having to tag them. Could it be possible to make tagging the users from a CSV upload in an outbound email to be optional? Also, a way to send dynamic emails to certain emails would be nice too rather than having to use the ruling. So maybe like a bar that lets you type in an email and send without ever having to update the email or add an attribute that I have to edit under each person per each email I need to be set up like this.
Please allow to choose multiple selection in the List option when close the conversation.
I’m looking to trigger certain external workflows when certain articles are updated in our intercom instance. Example workflows include (but is not limited to) customer and internal newsletters. This would be a pretty cool feature to ensure eyeballs are kept on high-value articles whenever they change/are updated, especially as more and more disparate teams are collaborating to ensure these articles are up-to-date.
As the product owner for our intercom installation I would like to hide the inbox from the left panel for teammates that don't handle tickets.For instance our marketing department writes articles, send outbound messages and does automations.They don't need to see the button to the inbox and should not be able to be assigned to a ticket.
Since Intercom allows for multiple contacts (users) to have the same email address, using a combination of attributes and/or fallback logic is a better way to identify a particular user compared to email alone. Intercom's Zapier action Find user provides a number of options which would allow you to return a single user as a result, but the Add note action does not. Because the Add note action only allows email as an input, it errors anytime Intercom returns multiple users with the same email. And because it only allows email as an input, there is no way to get around this — and this makes this action unusable in all cases where an email address belongs to multiple users. Feature request summary: Bring Intercom's Add note Zapier action to parity with Intercom's Find user Zapier action by allowing multiple attribute inputs for finding users and/or fallback logic when multiple users are identified.
Currently, Intercom’s article editor only supports anchor (jump) links for headings H1 to H4 using the “Copy anchor link” feature. I am requesting a built-in way to create a jump link for <p> tags or other non-heading elements—manual anchor tags like <a href="#my-section"> . I would like to create direct jump links to normal <p> tags or regular texts within the same article which are not currently supported in the current editor workflow.
Translate CSAT feedback into default workspace language. Right now, we’re translating the conversation but then when a user leaves feedback in their native language, I still need to use a third-party tool to translate the feedback to understand it.
I would like to be able to upload my own recording for the outbound call message that notifies customers that the call is being recorded.
I'd like to submit a feature request on FIN AI Agent Suggestions. It would be great if it could be possible to sort the list. A use case would be the ability to sort suggestions based on number of conversations used to generate the suggestion so we can begin or focus on optimization efforts that would have the most impact.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.