Share product ideas and upvotes with our product team
Current behaviour: when a phone number or email address matches multiple relations, the item is automatically linked to the most recently used relation.Expected behaviour: present all matching relations and let the user select the correct one.Why: auto-linking to the most recently used relation silently attaches items to the wrong one, which is easy to miss and awkward to correct afterwards.
Hi there,Pretty simple, some of the fields that chats have are not visible within Macros, such as the Subject field.The only subject field visible in Macros at the moment only applies for tickets - not chats.If Macros could just be expanded to include more things and possibly include an order similar to the order within the chat it might also make it easier to spot which ones you need.
Add the ability to review and leave QA feedback on cases that were handled by more than one agent, in Monitors. Reviewers should be able to either leave one comment covering the case and all agents' work as a whole, or leave individual, agent-specific feedback for each agent involved in the conversation.When a reviewer opens a case in Monitors that involved multiple agents, give them two review options:Case-level comment: a single piece of feedback addressing the case and the agents' combined handling of it (e.g., evaluating handoffs, overall resolution quality, consistency across agents). Per-agent comment: individual feedback tied to a specific agent involved in the case, scoped to that agent's own contribution.These options shouldn't be mutually exclusive. A reviewer should be able to leave one overall comment on the case and separate feedback for one or more of the individual agents in the same review pass.
Sometimes our users report multiple bugs in a conversation. We would like to be able to have two separate tracker tickets in this case but the system will only allow 1 to be linked at a time.
Hello! I really love the AI compose, rephrase and expand, but I often find the tone to be less than desirable, specifically around shortened words (I have/I’ve, We are/We’re). It would be great if AI compose could have some slight guidance on workplace specific requirements, such as the option to allow/restrict shortened words. Another adjustment that comes to mind is including/excluding the final sentence on the email (Many thanks, [YOUR NAME] [YOUR TITLE]). Its a relatively minor issue, but it definitely adds up over time! It would be great to someday use the AI compose feature without needing to make any adjustments manually!
ProblemTicket reporting does not support filtering or breaking down data by the ticket submitter (the teammate or team who created the ticket). While reports allow filtering and grouping by the assigned teammate or team, there is no way to report on where a ticket originated. Feature RequestAdd Ticket Submitter (Teammate and Team) attributes filter to Intercom's ticket reporting module.This would enable "origin-to-destination" reporting to track who creates back-office or internal escalation tickets, rather than only tracking who ultimately resolves them. Why It Is Needed Cross-Departmental Visibility & Operational Efficiency: Without a submitter attribute, managers cannot identify which internal teams generate the highest volume of back-office requests or track how issues move across teams. Having this data allows operations to optimize ticket routing, address root causes, and target staff training where demand originates. Agent Productivity & QA Audits: Tier 1 agents who triage incoming issues and create secondary tickets for Tier 2 teams currently get no visibility or credit in reporting once the ticket is reassigned. Reporting on submitters ensures full accountability for created tickets, enables quality audits on submitted tickets, and accurately measures internal support demand. Complete Workflow Analytics: Assignee-based metrics only tell half the story—they track who completed the work, but mask the origin of internal demand. Submitter reporting bridges this gap to provide full end-to-end visibility into internal support workflows.
Right now, if you want to add a custom image or anything to any sort of outbound message, they can ONLY go in the messenger. I think there should be the ability to add custom imagery to banners and other messages that we can choose to display in a static way to our users.
Some of our agents correspond with customers using the alias feature, but if we want to loop in a vendor in a side conversation it's more confusing with the alias (and signature which is customer-facing).I’d like to be able to eitherhave an option to not use the alias feature just for side conversations have a per-conversation override for the alias featureIt would also be great if the signature was separate for side conversations for the same reason.
I want to be able to autoatically upload images without hosting public URL. It seems like a workaround that should not be necessary. This would make it easier and more intuitive to automate. So what I want:- Have local image files that I can upload automatically as part of an article or integrate them with a seperatae step automatically- Either through API or MCP
When I export a conversation to PDF, it’s missing the images (which are replaced with a placeholder: [image])I feel that omitting these screenshots/etc is omitting valuable context from the ticket, so they should be part of the export.
We would love to see an option that allows callers to remain in the queue without having to make an active IVR selection.In our market, the most common expectation is simply to wait for an answer. Requiring callers to press a key to continue waiting can create unnecessary friction and may lead to confusion or abandoned calls.An option to let callers stay in the queue automatically, while still offering callback or other choices as optional alternatives, would create a more natural and user-friendly phone experience.Would anyone else find this useful?
Please add Hinglish as a separate language, it is very simple to add, most of the models know how to comunicate with help of it, and understands the contexr good.It will allow to support Indian market much better, since not all understands English good and also no one are using Hindi, since it is complicated to type.
Like Fin if you adjust a scorecard answer and add reasoning, the AI bot will learn from this so future reviews will take that feedback in to account
I WANT TO WORK OUR SUPPORT CONVERSATIONS IN A KANBAN VIEW. WHEN WILL THIS BE AN OPTION?
Currently, the message list displays all of a user's past inquiry threads. I would like to request a feature that allows users to hide or archive them on their end.
Hi there!We use external tools to aid our articles visually, and we would love to be able to embed them in your articles.Additionally, allowing HTML, CSS or iFrames would let us customize the articles to match our company look.Looks like quite a few people are asking about this in the Help Center, so fingers crossed it’ll be added in a future update.
For workflow that involve Fin, I have no choice on whether to let Fin engage with the customer or not. I need to use Fin to analyze new messages to determine intent and follow routing rules, but there’s no way for me to stop Fin from responding to the customer’s inbound message. Why?? Doesn’t make any sense. I should be able to leverage Fin for background back-office automations without exposing Fin to the customer.
The Teammates page only shows how many teams a user belongs to, not the actual team name(s). Should list the NAMES of the teams in the Teammates page, not the quantity. Today, I have to go to the Team Inboxes page and check every single team and search for the user. This is time consuming and very prone to oversight.
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.