Share product ideas and upvotes with our product team
Is there a way to turnoff the junk filtering or whitelist specific addressed? We had a user be marked as junk when we had actively been talking to them.
Merging email conversations and messenger conversations is not currently possible. It would lessen confusion to limit the conversation list when trying to merge to only show conversations from the same channel.
It would be awesome if we would be allowed to edit user attributes after having added these additional attributes from the same chat window instead of having the hassle of heading to contacts, them company then select the user to edit the user attributes all the time due to time consumption
Some clients request that a specific email address be added to all of their support inquiries for their tracking purposes. As of right now, we must manually add their email address as a participant or CC. It would be a great time saver (and ensure 100% compliance) to be able to use the existing rule of email domain contains: “example.com”, to trigger the addition of an email address as either a participant or as a CC in a workflow.
I'd like to create dependencies on my custom fields.I have a custom field that tells me the main subject of a conversation, but it would be great if I had the option of breaking the subject into specific subjects. It would lead me to more visibility on the subjects that are being asked the most. For example:If I have a conversation data point called Category with a list of relevant things about our product, I would like to create a Sub-Category conversation data point that allows me to break this done.
Would like the ability to do attributes based on dependencies so if a specific attribute value is selected then another attribute field would pop up to add information in. This is specific to things where additional context is required.
Our team has been utilizing Zendesk for a while now, and we've found that it provides excellent ticket field options. One particularly useful feature is the ability for certain fields to appear conditionally, depending on what's been selected in other fields. Let's say we're discussing a shop and I've got 1000 fields. One of those fields is where agents choose the product type. I want only the fields related to that product type to be visible for the agents to select. For businesses that offer a wide array of products or services, this would be a significant victory as they require a comprehensive way of capturing diverse details on each of them.
We primarily use inbound emails as our form of communication. Many times, it is hard to collect their qualification information specifically just a basic name. The “Ask a question” app that is created by Intercom helps, but it only allows one question at a time. It would be great to have another way to do this, or if that app was updated to allow you to add multiple questions.
Enable Canvas Kit Sheets/ iframe for inbox
It would be so useful if there was a native app that could be setup between Intercom and Wix so that data would automatically transfer in between the two without having to setup complex API’s for us that are on small teams with no in-house developers.
It would be extremely helpful to have the ability to add keywords to an article, making it easier to find. For instance, on our platform, users can invite colleagues to collaborate within the tool. While we use the term “Invite,” users might search for “Add colleague,” “Connect with colleagues,” or other variations. If their search terms don’t match our exact wording, relevant articles may not appear in the results.Being able to assign keywords to articles would ensure they are discoverable regardless of the terminology users choose.I came across a suggestion in the Support forum to include a callout section at the bottom for keywords. However, since these keywords would be visible to users, this approach isn’t ideal.Additionally, it would be great if the bot could leverage these keywords to identify relevant sources when responding to users’ questions.
Context/background: I’m currently trying to boost or promote our “Talk to a person” button at the end of Fin conversations. Currently, they’re rather small and unintrusive, so customers often don’t know they can access Live chat with the team or human that way. So they often abandon the conversation. One idea I tried was to add a message when customers become inactive, to prompt them to click the button. However, it looks like the original buttons get hidden when inactive. So, while I’ve amended this so users know to open a new chat to do this, but this isn’t ideal. Idea(s): So following this, I have 2 ideas:Idea 1: More options for when customers are inactive: E.g. a workflow, or custom answer. Setting for how long users can be inactive before the live chat it closed. If possible, options to highlight the buttons. Idea 2: More customisable options for buttons. It would be nice to have the buttons be bigger. Maybe get these to pop-up or highlight after a while.
Current StateUpdates to tracker tickets do not impact the state of the primary ticket while back office tickets’ updates will impact the primary ticket.IssueOur Support teams, primarily our Technical Support teams, have to design different workflows (not the product feature) to manage back office and tracker tickets. This leads to missed updates on tracker tickets when Jiras are updated or resolved.RequestIt would be great to not only align on the behavior of these two ticket types but to also create a feature that allows the owner of the back office or tracker ticket to alert the owner of the primary ticket when a ticket has been resolved. This alert could be something as simple as an indicator on the ticket in the inbox or an option at the time of resolution to say, “yes, reopen the primary ticket and alert the ticket owner.”
I think being able to A/B test not just outbound (when user visits a page) workflows, but all workflows, could be highly beneficial for testing out changes (in policies, handling etc) before committing to them. This could especially be useful creating an A/B testing PATH inside a workflow - trying to see how customers react to FIN for example, before feeling comfortable setting it live.
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.