Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    2806 Ideas

    Jessica from AmericorNew Participant

    Feature request: Preserve forwarded email content and attachments from Apple Mail in IntercomSubmitted

    Hi Intercom team,I’d like to submit a feature request regarding forwarded emails and quoted content handling in Intercom. Feature requestIt would be very helpful if Intercom could preserve and expose the full forwarded email content, including quoted messages and attachments, regardless of which email client was used to forward the email. Current behaviorWhen an email is forwarded from the web interface of the email provider, the forwarded content and attachments are visible in Intercom as expected.Example conversation:https://app.intercom.com/a/inbox/iln7babw/inbox/shared/all/conversation/215474365038458?view=ListHowever, when the same email is forwarded from Apple Mail on macOS, the quoted forwarded content and/or attachment is not visible in Intercom.Example conversation:https://app.intercom.com/a/inbox/iln7babw/inbox/shared/all/conversation/215474364926343?view=List Why this mattersOur workflow depends on reading forwarded customer emails inside Intercom and also accessing this conversation data through exports and the API.At the moment, if the email is forwarded from Apple Mail, the quoted forwarded content is not available in the Intercom conversation export as text or PDF, and the same incomplete data is returned through the API.This makes it difficult to reliably process forwarded emails, because the available conversation content depends on the email client used by the sender. Expected improvementPlease consider adding support for preserving and exposing the full forwarded/quoted email content and related attachments in Intercom, including cases where the email was forwarded from Apple Mail or other desktop email clients.This would make forwarded email handling more consistent across email clients and more reliable for API-based workflows.Thanks!  

    UjjwalNew Participant

    iOS App Feedback (Primarily Feedback, Not a Feature Request)Submitted

     First off, I wanted to share that the new iOS app update feels like a significant improvement overall. The UI refresh looks modern, navigation feels cleaner, and features such as inline image rendering within email chains are genuinely useful. The update has encouraged me to use the mobile app much more frequently than before.That said, after spending more time with version 5.0.0, I came across several issues and pieces of feedback that I wanted to share with the team.1. Blurry UI During NavigationObserved BehaviorWhen navigating between different sections of the app, portions of the UI occasionally become blurry or appear improperly rendered.Additional Notes The issue often improves or resolves after scrolling. The behavior is intermittent but noticeable enough to impact usability. Screen recording was provided in the support conversation. FeedbackThis feels like a rendering or view refresh issue that may have been introduced with the new UI architecture.2. Queue Count Synchronization IssuesObserved BehaviorQueue counts do not always update correctly after conversations are automatically assigned.Example Conversations were successfully routed from the SME queue to individual team members. The SME queue should have shown 0 conversations. Instead, it continued displaying 3 conversations. Pull-to-refresh did not resolve the discrepancy. The only workaround was completely closing and reopening the application. FeedbackThis can create confusion when managing workload and queue health because the displayed counts do not accurately reflect the actual state of assignment.3. Missing "Reassign Replies" Toggle (Highest Impact Concern)Previous BehaviorThe profile/settings area previously contained: Away Mode toggle Reassign Replies toggle Current BehaviorOnly the Away Mode toggle is visible.The Reassign Replies option appears to have disappeared entirely.Why This MattersUnlike the other issues reported, this directly affects team workflows and productivity.The ability to control conversation reassignment while away is an important operational feature that many support teams rely on daily.RequestCould the team confirm whether: This was intentionally removed? The setting has been relocated elsewhere? This is a bug introduced in v5.0.0? Of all feedback items listed here, this is likely the most impactful from a workflow perspective.4. App Crash When Opening Contact DetailsObserved BehaviorThe app crashes immediately when tapping on a customer's name within a conversation.Notes Screen recording was provided. This appears similar to a previous issue that occurred when opening conversations containing particularly long email addresses. That prior issue was fixed, but this behavior feels related. ImpactThis prevents access to customer details and creates a disruptive experience when managing conversations. Overall FeedbackOverall, I genuinely like the direction of the new iOS experience. The visual refresh, improved email rendering, and general modernization are all appreciated.The feedback above is being shared because I use the app heavily throughout the day and would love to see it become a reliable primary workflow tool. Most of the concerns are centered around stability, state synchronization, and preserving existing workflow functionality.If I had to prioritize the items: Missing Reassign Replies toggle Contact-detail crash Queue synchronization/count refresh issues Blurry UI rendering Thank you to the iOS team for the significant work that clearly went into this release. I look forward to future updates and am happy to continue providing feedback as I spend more time with the new version.PS - I have attached all the screen recordings on chat with a support rep from your team. 

    Auto-Translation for TicketsSubmitted

     Why It Matters:Customer Experience: When customers receive replies in their native language, it significantly improves satisfaction, trust, and perceived support quality. Not replying in the customer’s language can lead to frustration, misunderstandings, and reduced resolution rates. Agent Efficiency: Manual translation of converted chats is time-consuming and error-prone. Agents spend extra effort translating messages, which slows response times and reduces the number of tickets they can handle. Scalability: As your business grows globally, manual translation doesn’t scale. Auto-translation enables seamless multilingual support without hiring additional translators or expanding language-specific teams.Risks to Consider:Accuracy & Nuance: Machine translation may not always capture context, tone, or industry-specific terminology, potentially leading to miscommunication. Data Privacy: Translating customer data through third-party services may raise compliance concerns (e.g., GDPR, data residency). Customer Expectations: If translation quality is inconsistent, customers may become frustrated when messages are unclear or inaccurate. Implementation Complexity: Integrating translation into ticket workflows requires changes to existing systems and may impact performance or user experience.Impact of Not Translating:For Customers: Receiving messages in a language they don’t understand can lead to confusion, repeated follow-ups, and a perception of poor support. For Agents: Manually translating adds cognitive load, increases response times, and may lead to burnout or errors. For the Business: Poor multilingual support can result in lower CSAT scores, higher churn, and missed opportunities in non-English-speaking markets.