Share product ideas and upvotes with our product team
We have multiple sources of knowledge for Fin, including confluence, websites, and articles hosted on Intercom. Occasionally, the sync will fail for confluence or a website. I’d like a notification to be sent to the admins of the account when this happens so that we can review and re-sync as needed.Fin relies entirely on these sources to be able to help our customers and agents, so it seems like a big oversight in Intercom that if the content fails to sync nobody is notified.
It would be good to allow teammates to set a default reply method.At this time, there is no way to for example make sure a Note is always the default when creating a comment in a conversation.Some teammates only add internal notes and don’t want to constantly pay attention they don’t add public comments.A configuration option in the teammates personal settings would be great.
At this time macros cannot be used for Back-office and Tracker tickets.These can only be created manually.Our Operations team created dozens of back-office tickets each week and it would save them a lot of time if they could do this with a macro. That would give them a template in which they can just fill in some data.
I'd love to see the option to enable advanced customization for the Help Center layout, allowing users to leverage HTML, CSS, or iFrames for deeper control.Additionally, implementing an optional sidebar navigation structure (both right and left) as a configurable layout element would give users more flexibility to tailor the Help Center for branding, usability, and navigation needs. Sidebars can also boost SEO, AEO, and GEO, benefiting content discovery and accessibility.
For example, we want to report on Fin AI Involvement based on conversation closed date but that is only possible via the API. All reporting for Fin Involvement is based on conversation started date. It seems critical for native reporting to be able to report on a metric by any date field available - whether it be started or closed date. That way we can report on things like MoM closed conversations alongside # with Fin involvement and have the two metrics be apples to apples.
Hello,Can you all please create a metric that will track how long an agent works on a ticket. Like it only counts when the ticket is actively open and being worked. Right now there is nothing like that and its very difficult to figure out average work effort per ticket.
I’ve seen a few posts on the forum regarding the ability to embed iframes or generic HTML into help center articles but they are all a bit dated so I would like to raise it once more for consideration.
We send our CSAT rating request 5 minutes after a conversation ends. Since they don't expect a rating to be sent, they often have already closed the chat window.As a result, the CSAT rating request usually remains unseen for over 3 minutes and is then forwarded to the client’s email without any conversation history, since it is the only part of the chat they haven’t viewed. There’s a chance clients could give a negative rating since the rating request appears in their email without any conversation history.I suggest that when Intercom forwards unseen conversation to emails if they’re unseen for 3 minutes, it should include a transcript of the entire conversation.
We are currently monitoring all customer conversations where Fin is involved to ensure an excellent customer experience. While a report already exists that pulls all conversations in which Fin has participated, there is no mechanism to leave the evaluation of the quality of Fin’s responses with real customers.I propose introducing a simple rating system within Intercom that allows us to assess Fin’s performance with three categories: Good, Acceptable, or Poor. This would work in a similar way to the evaluation logic currently used in the Test module.Implementing this functionality would enable us to: Track the accuracy and helpfulness of Fin’s contributions. Monitor Fin’s “health” over time. Compare Fin’s performance across different topics and contexts. This improvement would provide valuable insights into Fin’s effectiveness and ensure we continuously deliver a high-quality customer experience.
The only options are Live, Paused, or Delete - which isn’t too helpful. You don’t always want to delete a message or a Series. You might want it paused and return to it another time and change the rules or you were just testing something out.It would super helpful if you can “Archive” with the ability to “Unarchive” at a later date if you want to reuse the message or series.
Currently if you offer multilingual support in AI, you will need to create duplicate snippets in every supported language. This creates extra work.Having the same multilingual functionality for snippets as articles would be much more convenient. Articles do support multiple language versions within a single article using translated content objects, which makes management much easier.Having snippets work similarly to articles with built-in language version management would definitely streamline the multilingual content workflow.
It would be very helpful to also use custom email templates (HTML and visual) not only for outbound campaigns but for conversations with users and leads.
Currently, in the Inbox, next to the "Open/Closed" toggle, there is an option to sort conversations by fields such as "Start Date" or "Last Activity." However, there is no option to sort or filter by "Rated Chats."It would be very useful to have a "Rated Chats" option directly in this sorting/filter menu, allowing users to easily identify and review conversations where customers left a rating.At the moment, the only way to achieve this is by using the API with specific fields like conversation_rating.score, conversation_rating.replied_at, or conversation_rating.requested_at. Adding this filter directly in the interface would make it much simpler to track customer feedback without relying on API queries, improving the visibility of evaluated interactions and enhancing workflow efficiency.
When changing workflows, the changes are only active for conversations that were created after the change.This is an issue. Suppose a major issue was found in the workflows, affecting multiple conversations and tickets. There is no way to solve that issue for the current/existing conversations and tickets, only for new ones.
Received from Intercom Support : So if a workflow triggered on a customer's email and the customer sends another email within a 2-minute window, the workflow will not run again.Some of our customers send us a lot of emails during a small period of time. Because of this settings, a lot of those emails are not handled by the workflows we have in place to get the conversations assigned to the correct teams. Therefore, a lot of what is coming in, is unassigned, leaving us with much manual work to assign everything.Could this 2 minute window be made configurable ?
With Explore access, lite agents can drill-in to get a list of the conversations/tickets they need to see. But they also have the ability to change the filters. Allowing them to see a totally different set of tickets than what was originally intended for them.It would be nice to have the ability to allow lite agents to access a report, but to only allow them to drill-in, without allowing them to change the filters.
Response from the Support team : So I have just checked with one of our engineering teammates and they have confirmed that the side conversation creation flow creates conversations through the standard email conversation flow, but never accesses parent conversation brand data or inherits any brand configuration.When setting a brand in a conversation, the goal is to have a specific signature. It is unacceptable that when you send a side conversation, a different brand is being used.
I open multiple tickets for my team to Intercom Support weekly and it is very difficult to keep track of previous responses/troubleshooting. I would love for a way to be able to search in my previous conversations to quickly reference!
Many times we receive duplicate conversations from users who are looking for assistance quickly, it would be awesome if Fin could recognize they are opening multiple conversations and maybe mention to the user that they have another chat open and to further correspond there or automatically close out the duplicate and leave an AI summary in one.
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.