Share product ideas and upvotes with our product team
Adding UI functionality of having the profile box optionally be it's own separate window or modal that can be repositioned to suit teammate preference. The thinking here is that if it's not tucked in the bottom corner it would be easier for teammates to quickly change status when going between break, lunch, and end of day.Supporting idea here is also to add a keyboard shortcut to change our status’ quicker than the multiple clicks it currently takes.
As our approace to live support in our team is that an agent should be on multiple live channels at the same time. So you are either on phone calls or live chat (chat and social media) and then always on email.We would like for the agent to be able to choose what channels to be recieving conversations from. Currently it’s my understanding that if you are beign assinged emails, you are also being assigned chats. These two channels shouldn’t be considered the same.
We would get a lot of benefit if we were able to embed iFrames, or custom code in general, into Help Center articles. The particular use-case here is that we use Storylane to create interactive demos for clients, and right now our only options are to link to the demo externally, or insert it as a video in the article which causes us to lose the “interactive” piece of the demo.
Right now, every user that wants to upload multiple documents at once, needs to send them all separately. Why isn’t it possible to select multiple attachments at once? This would be a huge improvement for us as we want our users to upload multiple documents, but always sending them apart would be a waste of time. Does anyone has a workaround for this?
Currently, the integration allows updates to statuses and comments from JIRA to Intercom, which works fine. However, there is a limitation where a JIRA ticket can only be associated with one Intercom ticket at a time, which creates some inefficiencies in workflows.Issue: We track bugs that are worked on in JIRA through Intercom tickets. However, with the current limitation of the JIRA for Tickets app, we are only able to apply one JIRA ticket to a single Intercom ticket. This is problematic because it doesn't reflect the reality of how multiple customer support tickets may be related to the same JIRA issue as well as allow the automation for JIRA ticket status updates to be sent to Intercom and out to the customer via the custom statuses feature. Request: I would like to request an enhancement to the JIRA for Tickets app, allowing users to associate a single JIRA ticket with multiple Intercom tickets at once. This feature would work similarly to how the JIRA for Cloud app allows for multiple associations, and would significantly improve workflows for teams who track related customer support tickets across different issues in JIRA.By adding this capability to the JIRA for Tickets app, teams would be able to link a JIRA ticket to multiple customer support tickets, ensuring a more accurate representation of the work being tracked and updated across all associated tickets.
At my organization, our support reps do several tasks when they are not active on live conversations or responding to emails. It would be great to have the ability to add custom away reasons within Intercom. For example, our support reps are commonly reviewing social media posts as a part of their daily tasks, so if we could add this as a custom away reason, then it would give us more insight into what our support reps are doing throughout a given day and how much time they are spending on respective tasks. Ideally, admins would be able to add custom away reasons on the backend that would then appear as available options for reps when changing their away reason or status.
I don’t mind product placement in a free tier. You get what you pay for, that is fine. But we pay a substantial fee to have “powered by Intercom” under every email sent out by support. That is not professional looking and I’d like to be able to turn that off.This is injected currently as part of our auto response.
Summary: I would like a tester feature added to workflows, to test how/when certain rules will trigger. Similar to the code testing for integrationsContext: I spend a good amount of time building workflows. And one of the bug bares is creating a number of rules of how, when and who this workflow apply to, only for these not to work in unique use cases. Problem: Currently, to know exactly how the rules (e.g. audience rules) work is mostly trial and error, especially when multiple attributes are needed. Through experience, I do avoid the majority of issues, and with the help from Intercom’s Fin and support team I can troubleshoot issues. But this takes a lot of time, and for things to go wrong, for this to happen.Suggestion: When creating rules e.g. for audience, branches etc. there should be a testing box. Similar to the Preview option, and the “Test response” are when creating new integrations/data connectors. Where you can provide a scenario or user profile to confirm whether the rules will trigger or not.
We’ve noticed some issues regarding multichannel availability and would love to see some additional options or the ability to customize. These availability options would be nice, but ultimately I think the ability to customize based on our needs would be ideal: chats, phones, conversations, and like a callbacks option.
We would like to create guidance the can reference specific folders that we have set up for snippets. For instance, “if a client is asking about forms, first ask them which type of form they are using. If they say they are using a X form, only respond based on snippets from the X folder and if they respond with Y form, only respond with snippets from Y folder.”Same idea as well with Knowledge content, if we could use Guidance to have it only source articles from a specific section (church management, Giving, apps, etc) that could really help.
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.