Share product ideas and upvotes with our product team
When sending emails in bulk, there’s always a portion of emails that get hard bounce or some other issue. Now, there’s no possibility for me to act quickly, e.g., archive contact with hard bounce. Instead I need to go one email by one. When the volume is big, this becomes very problematic.
The knowledge editor needs to have an undo feature so if you make a mistake you can revert back to the previous version of the article.
Would it be possible to add some settings when creating a new snippet via “Inbox > Improve this answer” more like what folder it should be and what tags it can have?
Would it be possible to have another chat export feature wherein chat events are visible?
Hi,I currently have a number of conversations in my inbox, all of which are still open and actively being worked on. Some of them are related to each other though so I'd love a way to group these together so my inbox is better organized. Basically folders of conversations within my inbox.Thanks,Julian
In my inbox, I have multiple conversations that are still open and relevant, and relate to the same topic. I don't want to close them until they're actually resolved but, in the meantime, they're kinda polluting my inbox. It would be greats if I could create folders of conversations in the inbox.
Hi there,I create articles and was wondering if more color options could be added to callouts. I use callouts to separate sections, as I find it makes the content easier to read. However, the available colors do not match the brand’s colors. Would love to see more options!
Hi, I would like of course much more customization in the article body of the help center (markdown, html etc.) but also, could we customize the callout colors throughout the help center so that they could be for example product colors?
A lot of our dealings with our customer involve IMEI-SV, an International Mobile Equipment Identity with Software version. This number is expected to be 16 digits long, exactly like PANs.Since we are also dealing with customer credit cards, we recently decided to enable the PAN redaction feature.We saw that most of our IMEI-SV numbers were redacted, rendering our teams work more difficult, which lead us to disable the feature.We think PAN redaction is useful feature, but would love to see a way to customize it to prevent false-positives.Depending how this is implemented on the intercom-side of things, it would be interesting to have way to exclude certain patterns. IMEI, and their -SV variants, start with 8 digits which represent a model/origin which is known to us and could easily be added to an exclusion list, preventing redaction.
I would love to be able to customize the homepage a bit more. we have a lot of collections, and it looks cluttered. would love to be able to choose which ones appear in the collections section and then have others accessible some other way - maybe a nav bar or as a link in the header
The table layout is great but the ability to sort and filter columns is very limited.
At the top of the new conversation a summary generated by AI that says “this client has recently messaged us about XYZ, and also reported bugs ABC in the last 2 weeks” Giving more context on customer’s past interactions so that we reduce being repetitive
Potential Bug Report--For months, I've been experiencing an issue with the Back Office tickets system. We have a name section in the back office ticket. It comes after the bulk of the data, so if you're doing this in order, you've grabbed links, added lots of context. Then you go down to the name. If you're lucky enough to have your name start with an "N," the shortcuts will trigger a new case and you lose all that case data and research you just put into that consult. I did verify with some of my other 'N'-named colleagues. I know if obviously effects a fraction of a fraction of users, but wanted to surface it as an issue for your teams to look into!
Separate views manage permissions for private and public views. Teammates should be able to add private views and pin public views but not delete or edit public views.In the meantime, adding view management to the activity logs would be helpful.
We would like to:Allow customization of time interval and frequency/amount of follow-ups Fin can send Allow customization of time to automatic close if client does not respond Why are we requesting this? (real scenario below)Fin followed up after 1 minute without a response Fin then followed up again, 4 minutes after the first follow-up The way Fin followed up (phrasing) was quite intense 10 minutes after the second follow-up, Fin closed the conversation without letting the user answer
It would be nice to have an indicator on the browser tab that changes when the agent’s activity status changes. Initial thought is to have a green dot for active, and a yellow dot for away, just like what is seen in the product.This can be helpful when agents have multiple tabs open in the browser.
This seems like the wrong place for this, but Fin sent me, so here goes…The example Java code shown in Intercom when going through the process to set up JWTs with Messenger does not specify the encoding. So if your JVM uses something other than UTF-8, the generated JWT will be invalid.I suggest it should be updated, to call the `.getBytes(StandardCharsets.UTF_8) method on the string to ensure the encoding is always properly handled.Map<String, Object> claims = new HashMap<>();claims.put("user_id", userId.toString());claims.put("email", email);String token = Jwts.builder().setClaims(claims).setExpiration(Date.from(Instant.now().plus(24, ChronoUnit.HOURS))) // Expires in 24 hours.signWith(SignatureAlgorithm.HS256, "<YOUR TOKEN HERE>".getBytes(StandardCharsets.UTF_8)) // Set proper encoding.compact();
For the ticket form, we can configure attributes, but it would be great to be able to display the description of the attribute to the customers in order to give more information on the attribute
We’d love it if our customers could have a consolidated view of all email and chat conversations they’ve had with us in the Messenger, so they have a full history of their correspondence in-app. Customers loved the ability to view their email history with us in Zendesk and we’ve received complaints about this feature loss since making the switch.We know that it’s technically possible to achieve this by processing emails as tickets instead of conversations, but tickets are such an awkward and overwrought workflow for our business needs.
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.