Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    518 Ideas

    Søren PedersenNew Participant

    Use the ARC seal from trusted forwarders in Fin's email authentication checkSubmitted

    When Fin is deployed on email, the setting "Prevent Fin from processing emails that fail authentication (DMARC)" only checks the authentication result when the message reaches Intercom. It ignores the ARC seal that a forwarder adds.Many teams don't receive email at Intercom directly. Their support address is a Google Workspace or Microsoft 365 mailbox that forwards to Intercom. The forward changes the server that delivers the email, so SPF fails for every sender who doesn't sign with a DKIM key for their own domain. Most Microsoft 365 customers on default settings are in that group. Their DMARC result then fails, and Fin skips the email, even though it was genuine and passed authentication when it reached our mailbox.For us, 26 genuine customer emails were skipped in 10 days. Turning the setting off isn't a good option, because it's the only thing stopping Fin from answering forged emails.Request:1. Let a workspace mark its forwarders as trusted (for example Google Workspace or Microsoft 365, or specific domains). For mail from those forwarders, Fin should use the authentication result recorded in the forwarder's ARC seal. This is how Gmail and Microsoft 365 themselves handle forwarded mail.2. As an alternative or addition: when an email fails the check, let Fin ask the sender for the one-time code before it runs any data connector, instead of skipping the email.Related: "Add more ways to fix: Fin did not try to answer because the sender could not be authenticated". 

    Services PartaNew Participant

    Let admins set the default audience for API-synced content import sources in the UISubmitted

    Content import sources created through the AI Content API (sync_behavior "api") have no Settings or Target tab in the UI. "Open settings" is greyed out for them in Knowledge → Sources and in Fin AI Agent → Train → Content. For website sync sources, the same menu opens Settings → Target → Audience control, where an admin picks a default audience and adds audience rules.Support confirmed this is expected today: for API-synced sources the default audience can only be set through the API (audience_ids and apply_audience_to_existing_content on the content import source).Why it matters:Many teams split the work. One team creates content in an external tool that syncs it into Fin. Another team owns Fin audiences in Intercom and never touches that tool. Today that audience owner can only change audiences page by page, and every new page from the source arrives as "Everyone". An app that syncs content has to request audience scopes, pull audience names and IDs, and build its own audience picker just to cover this. That goes against least privilege and moves audience decisions away from the people who own them in Intercom.What we'd like: the same Target / Audience control for API-synced sources as for website sync sources, so workspace admins can set the default audience and audience rules in Intercom, while the app keeps managing only the content.

    JHarlowe
    JHarloweConnector

    More Granular Permissions Set For ProceduresSubmitted

    Summary: We'd like the ability to grant teammates access to create and edit Fin Procedures without also giving them visibility into or access to Workflows, automation settings and other sensitive operational areas of our Intercom workspace. Current Behavior: Today, Procedures live within the Fin AI Agent tab, which is accessed via the "Can view Fin and Automation settings" permission. This same permission also exposes Workflows and Simple Automations. There is no way to grant procedure-building access in isolation, any teammate who can work on procedures can also see workflows. To prevent teammates from editing workflows, we can withhold the "Can manage Automation settings and inbound Workflows" and "Can manage outbound Workflows" permissions, but those teammates will still have full visibility into workflow configurations, which is not ideal from an access control and operational security standpoint. Requested Change: Introduce a dedicated permission (e.g., "Can manage Fin Procedures") that:Allows teammates to create, edit, and manage Fin Procedures Does not expose Workflows, Simple Automations, other automation settings or operationally sensitive areas of the workspace Can be granted independently of any workflow-related or data / security related permissionsUse Case: We want to involve subject matter experts and content contributors in building and refining Fin Procedures, teammates who understand our processes deeply but should not have access to the broader automation and workflow configuration of our workspace. Today, there's no clean way to enable this without overexposing sensitive operational settings. Desired Outcome:A permission model that lets us confidently delegate procedure authorship to a wider group of teammates, with clear boundaries that protect workflow integrity.

    Cherry VC
    Cherry VCNew Participant

    Automatically Add User and Company Notes as Internal Notes During Workflow HandoverSubmitted

     Currently, important contextual information stored in User Notes and Company Notes is not automatically surfaced within a conversation when it is handed over to a Support team.Support agents may need to manually navigate to the user's or company's profile or surface the fields on top of all the data already available in the details section to review existing notes, which adds unnecessary steps and increases the risk of missing important information.This is particularly challenging when notes contain relevant customer context, known issues, special handling instructions, or other information that Support agents should be aware of before responding.The AskIntroduce a workflow action that allows us to automatically retrieve User Notes and Company Notes and insert them into a conversation as an internal note when a conversation is handed over to a human Support agent.Ideally, this functionality would allow us to: Add a workflow action to retrieve existing User Notes, Company Notes, or both. Automatically post the retrieved information as an internal note within the conversation. Trigger the action at a specific point in the workflow, particularly before or during handover to a Support team. Clearly distinguish between User Notes and Company Notes in the generated internal note. Ensure that the information is visible only to internal teammates and not to customers. Example Use CaseWhen a customer interacts with Fin and requests human support, the workflow automatically retrieves any existing User Notes and Company Notes associated with that customer.Before the conversation is assigned to a Support agent, an internal note is generated containing the relevant information.Example Internal Note:Customer Context (Automatically Generated)User Notes: Customer prefers email follow-ups. Previously reported recurring issues with a specific feature. Customer only works Monday to Wednesday. Snooze conversations outside of working days if follow up is needed. Company Notes: Customer has a known ongoing issue currently under investigation. Special handling instructions have been documented for the account. Currently on escalation due to migration issues  This ensures that every Support agent receiving the conversation has immediate access to important customer context without having to manually look for it. Expected Benefits Improved Support Efficiency: Reduces the time agents spend searching for existing customer information. Better Context During Handover: Ensures important user and company information is consistently available within the conversation. Improved Customer Experience: Reduces the need for customers to repeat information already documented. Greater Consistency: Provides all Support agents with the same contextual information across conversations. Reduced Risk of Missing Information: Helps prevent important customer notes or handling instructions from being overlooked. Desired OutcomeThe ability to configure workflows to automatically surface existing User Notes and Company Notes as internal conversation notes, particularly during handover from Fin to human Support.This would help create a more seamless AI-to-human handover experience and ensure Support teams have the context they need directly within every conversation.