Share product ideas and upvotes with our product team
Requesting a feature request regarding a customer’s ability to CC or add additional participants directly from our chat window within a conversation or ticket.The current lack of this functionality is creating a major bottleneck by forcing our teams to manually add the CC’s in every time and this also creates a less than fortunate experience for our customers who have 24/7 support and need to include team distros to support a follow-the-sun model. This is severely impacting our resolution time and customer satisfaction. We are also requesting the ability for us to build workflows so we can create a button or some mechanism for customers to add emails in CC at any point in the conversation or ticket from the chat window.
My suggestion is to update the round-robin assignment method to better manage ticket/conversation assignments. Specifically, it should be able to reassign tickets that were moved to 'unassigned' back to agents who were set to 'away' or had their status changed to 'reassigned'. It should also allow for tickets to be manually moved to the 'unassigned' queue.While the balanced method works well, it can be demotivating, particularly in small teams. In such teams, those who work harder end up receiving more assignments, which creates an imbalance.For example, we work based on ticket statuses rather than conversation statuses. As it stands, the person who solves the most tickets also ends up receiving more new ones. This becomes even more problematic in a team of four when one agent is out of the office for a week. During their absence, their colleagues resolve a significant number of tickets, but once that person returns, all pending conversations are reassigned to them, which can be overwhelming.
Right now there’s only an estimated timeframe for when an SLA will expire, like 2 hours for example. There’s no way to see the exact time that it will expire which is extremely frustrating. We need to play mental gymnastics at the end of the day or on a Friday to look at when a customer last responded, then calculate the exact time that it will expire, then do the same thing for all tickets with an SLA. Zendesk lets you hover over it and it shows the exact time it will expire- super easy and efficient. Please please please make this a feature so we don’t have to do more work to figure out when we have to respond by.
Make it possible to customize the height and width of the messenger when it is showcasing a Canvas sheet app as iframe in the messenger
Make it possible for a sheet app in the messenger to open in the Intercom messenger scenario where it is wider and bigger (as it is when you click 'expand' on the expand messenger button in the header of the messenger or as it shows in its bigger state when you are reading a help center article in the intercom messenger)Here you can see the ‘expanded’ state that I’m talking about:
When creating a canvas kit app make it possible for messenger home apps to call a function in the installed app/site or execute arbitrary JS in the installed app/site.
Hi, another suggestion we would like to add: Access to Copilot Conversation History Linked to Customer's conversation (For backoffice tickets)We would like to request a feature that allows us to view the conversation history between the customer advisor and Copilot, directly linked to the customer's conversation. In our workflow, we actively handle back-office tickets related to errors detected in sources and the way Fin AI responds. We rely heavily on conversation history attached to tickets to correct mistakes and improve content, as this helps us avoid misunderstandings. Currently, we have a back-office ticket type called Report on Fin AI, which is an effective way for us to improve our content and processes. We also created a ticket type called Report on Copilot, but so far, this does not function in the same way. Having Copilot conversation history linked would make this process much more efficient and help us maintain accuracy. I recall that last year there was a “Report” button in Copilot to flag mistakes to the back office, if my memory serves me correctly. It would be very helpful to have a similar feature again. Our internal routines are extremely strict and must remain accurate at all times.
Hi, a suggestion we would like to add: Scheduled Publishing and Unpublishing of Articles and Snippets (Internal and External) We would like to request a feature that allows scheduled publishing and removal of articles and snippets, both internally and externally. Similar to how social media platforms like Facebook enable scheduled posts, this functionality would help us manage content more efficiently. Often, we prepare content in advance for upcoming features or news. Having the ability to schedule publication ensures that this content goes live at the right time without manual intervention. Likewise, when certain features or information become obsolete on specific dates, it would be very helpful to automatically unpublish related articles on the same day. This functionality would also be beneficial during planned absences, such as vacations, or when key resources are unavailable. With scheduling in place, processes can continue seamlessly without requiring someone to manually update content.
It would be great to be able to create an escalation rule that will work only for one workflow. Or maybe to create an escalation rule based on the teammates acitivity - if active then escalte to team, if not active - let fin answer? What I want to do is to collect Fin attributes in every single conversation but I don't want Fin to handle all chats.
The ticket table is rather condensed, especially on smaller screens (screenshot below from a Macbook Pro 13”). This makes it difficult for our clients to read the titles and descriptions at a glance, resulting in them asking our team for an export. Some of the content is even hidden and can’t be viewed without scrolling horizontally. To make more space for the titles and descriptions, maybe there should be an option to hide columns from the table view? Ideally, the client could control that on their own view, and not change the view for other users.
I would love if we were able to help “train” Fin beyond content/guidance by giving a rating to past conversations that it’s been involved in. In other words, give Fin a way to learn off its previous answers, reinforcing answers we really like and highlighting/giving pointers on responses that weren’t exactly what we were hoping for. I see this as an iteration/update to the existing “Improve answer” button that appears on Fin conversations, prompting you to create new content. Instead, it could be a simple thumbs up or thumbs down, weighing the answer accordingly for future similar inquiries.
for hospitality companies would be beneficial to be able to get conversations from Airbnb messaging app in intercom like a conversation, it’s a great opportunity for intercom to bring customers from hospitality companies and also for us to be able to automate the messaging with Fin.
Right now, if you store a date in a people attribute in either unixtime or ISO 8601 format and use it in a message, it appears in “mm DD YYYY” format.But this format is not standard for all countries; each country has its own date format, and it should be possible to adjust it so that it is displayed according to the customs and practices of the contact's destination country.For example, in Spain the format is “DD-MM-YYYY,” in other countries it is “MM-DD-YYYY,” or “DD.MM.YY.”Please keep this in mind. Thank you.
We have a small team and no personalized service email addresses, but many team-inboxesWe separate incoming emails into different team inboxes based on the group email address and have set the balanced assignment rule for each team inbox.Now it happens that we wait for customer responses, or customers respond again to our closed conversation. Due to the balanced assignment, the assigned agent is repeatedly removed. It would improve our service immensely if the customer response always went to the agent who last worked on the case.
It would be great if there were an option for two Backoffice ticket type names: one internal, visible only to people with access to the tool, and one external, visible only to customers in shared tickets.
How it works now: Fin AI email replies from 1 email address only. This is incompatible when a workspace manages multiple brands and each brand has a different support email.Proposed solution: Fin AI is able to reply from multiple email addresses according to the Brands’ emails.
When working on an article or Snippet, it would be great for users to write notes about the article, reasons why changes were made, why it was archived, etc. So if multiple people are using Intercom in the company, you can instantly know why a decision was made about an article. Would love a little text box for notes in the sidebar with the other options.
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.