Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3155 Ideas

    Gaby CabreraNew Participant

    Support regional language variants in Messenger, matching Help Center capabilitiesSubmitted

    Problem:Our Help Center supports regional English variants (English (US) and English (Canadian)) and correctly serves the right version based on language override (we’d like to confirm as well that language override takes priority over browser language) when accessed directly. However, the Messenger only supports base language codes (e.g., en), not regional variants. This means a member with language_override set to en-US and one set to en-CA both see identical Messenger content (our default content set to en-CA ), there's no way to differentiate.Why this matters:Most of our members access the Help Center through the Messenger, not by visiting Help Center articles directly. So in practice, our regional Help Center translations only work for the small fraction of traffic that lands on articles directly — the primary access point (Messenger) can't route members to the correct regional version at all. This creates real accuracy problems: US members can end up seeing Canadian-specific content (pricing, policies, terminology) and vice versa, which actively misleads them.Requested feature:Allow Messenger language settings and language_override to support regional locale codes (e.g., en-US, en-CA, fr-CA, fr-FR), not just base language codes — so Messenger-served Help Center content matches the same regional targeting already available for direct Help Center visits.

    Christopher HayesNew Participant

    Add Telegram Business functionalitySubmitted

    Right now, Intercom's Telegram channel (Settings > Channels > Telegram) only supports connecting a standalone bot created via @BotFather. Customers have to find and message a separate bot username, which feels disconnected from the actual business.Telegram now offers "Business accounts" (available to Premium subscribers) that let a company keep its real, verified Telegram account — complete with opening hours, quick replies, greeting/away messages, and a business chat link — while automating replies through the Bot API's business_connection feature. A connected bot can send and receive messages on behalf of that real account instead of a separate bot identity.It would be great if Intercom supported connecting a Telegram Business account as a channel, the same way the current bot flow works today:- Conversations from the Business account land in the Inbox, with Fin and Workflows at full parity- Replies go out through the business_connection, so customers see the business's real name and photo — not a bot- Native Telegram Business settings (hours, quick replies, greeting messages) stay usable in Telegram itself, while Intercom handles the actual conversationThis matters most for teams whose customers are concentrated in markets where Telegram is the primary channel — a verified business account feels far more trustworthy and personal than a generic bot. Right now the only way to bridge this gap is third-party middleware, which adds cost and an extra hop. Native support would remove both.

    Gustav Riederer
    Gustav RiedererNew Participant

    Automatically stop Fin when a conversation is assigned to an agent (no agent reply required)Submitted

    We use Fin in the Inbox, but we repeatedly run into the same problem: Fin sometimes sends very long messages and occasionally incorrect or irrelevant information.At the moment, Fin only reliably stops once an agent actively replies in the conversation.This is a real issue in day-to-day operations because when I’m on the go, I often can’t reply immediately — but I still need to stop Fin instantly as soon as I see that it’s going in the wrong direction.Feature request: “Stop Fin without replying”I’m requesting a way to immediately pause or stop Fin without requiring an agent to send a message.Clear trigger examplesFin should automatically stop when any of the following happens: The conversation is assigned to an agent An agent takes over / opens the conversation A manual toggle in the conversation header: “Pause Fin” / “Stop AI replies” (one click) Controllable on mobile (e.g. via the Intercom mobile app while on the go) Why this matters Prevents incorrect information from being sent to customers (quality & brand risk) Avoids unnecessary long AI messages in the chat (customer experience) Allows a safe handover to a human even when mobile, without having to send a “placeholder” reply just to stop Fin Acceptance criteria When a conversation is assigned to an agent, Fin stops immediately (no further messages or follow-ups). Agents can pause/stop Fin without sending a reply (UI control). The feature is available on mobile (at least stop/resume). Optional: audit log (e.g. “Fin paused by Gustav via assignment/manual toggle”).