You can now share news, product updates, or announcements across all customer Slack channels in a single Broadcast.

There's no need to manage separate conversations or threads, you can target one or multiple customers directly from Intercom and see replies all in one place.

Beta now available in your workspace.

Reach the right customer segment every time, with efficiency, confidence, and brand consistency.

(1) Reusable audiences: create once, reuse everywhere

Define customer segments once and use them across Content, Guidance, and Data Connectors—so every interaction stays consistent.

(2) Audit & test with confidence: know exactly what customers will see

See what each audience will experience before launch. Use filters and Batch Testing to validate targeting with confidence before going live.

(3) On-brand identities: distinct look & feel for every brand (available in Messenger)

Give each brand its own Fin avatar and name in Messenger, so customers instantly recognize who they’re engaging with. Pair with audience-specific Guidance to align tone of voice for a fully on-brand experience.

Coming soon: Preview, Workflows, Tasks, Simple Deploy, Content Suggestions, AI Insights Reports, and AI Agent Identities for Email.

📘 Learn how to set up Fin Audiences & Identities

Slack is now a native channel to Intercom, where Fin can resolve conversations.

You decide which messages trigger an Intercom conversation, and Fin and your teammates can respond seamlessly - straight from the Inbox.

Beta now available in your workspace.

You can now enable internal articles as a knowledge source for Fin.

This includes all internal knowledge articles — both those created natively in Intercom and those imported from Notion, Guru, and Confluence.

This update is live and available to all customers today.

With code blocks for Data connectors, you can transform and manipulate API responses using Python directly in the Data connector setup. Unstructured or oversized payloads from APIs can often increase the chances that AI agents, such as Fin, misinterpret or fail to deliver clear answers.
​
Code blocks enable you to preprocess, filter, and reshape API responses before they reach Fin - all without backend changes.

When Fin replies over email, source links now appear right next to the relevant text — no more jumping to the bottom. This makes it faster to verify information, reduces visual clutter, and helps build trust in Fin’s responses.

What's new:

• Inline verification: See exactly where information comes from without breaking your reading flow.
• Cleaner layout: No more long footers — everything’s in context.
• Automatic update: Works for all email replies, no setup required.

Try it now

You can now control how Fin routes escalated conversations to your team using branching logic in Workflows. This new capability lets you create custom branches based on which piece of Handover and Escalation Guidance was applied - so every escalation goes to the right team, every time.

With Workflow branching, you can:

• Route escalations with precision, depending on the specific guidance Fin applied
• Mirror your support policies by creating branch-specific logic that aligns with your team structure and handover processes.
• Combine with other conversation attribute filters - like customer type, pricing plan or language - for even more precise routing.

This gives your team more flexibility and confidence when handling high-stakes or complex support scenarios with Fin.

Head to Fin Guidance in your workspace to explore the latest improvements.
​

The Fin preview experience now lets you impersonate real users and see exactly how Fin will respond. Simulate real scenarios using live or dummy data, test automations like Fin Tasks, and validate every answer.

Get full visibility and control to refine responses and deploy with confidence.

You now have more control over how you disclose to your customers that they’re receiving a message from an AI Agent, whether from the Fin Messenger, Zendesk Messaging or Tickets, or Salesforce cases.

AI Agent label on the Fin Messenger

In the Fin Messenger, you can choose whether to display an "AI Agent" label next to Fin (or your AI Agent)'s name on each message.

The toggle that controls this is in Fin identity settings and is:

• ON by default if you’re already using Fin.
• OFF by default if you’re not yet using Fin.

AI Agent disclaimer in Zendesk Tickets and Salesforce case emails

In Zendesk Tickets and Salesforce cases you can choose whether to display an "AI Agent" disclaimer in each Salesforce case or Zendesk Ticket email.

• The disclaimer reads: “This answer was composed by [AI Agent name], [Workspace name]’s AI Agent.”
• The toggle that controls this is in Fin’s email responses settings and is ON by default for all customers.

AI Agent introductory message

You can choose whether to enable Fin to introduce itself as an AI Agent at the start of conversations in the Fin Messenger, Zendesk Messaging and Salesforce cases.

The introductory message can be added as a message step immediately before the Fin answer step in workflows. It is also included by default in workflow templates.

In some regions, letting your customers know they’re speaking with an AI Agent may be a legal requirement.

You now have more control over how you disclose to your customers that they’re receiving an email from an AI Agent.

You can choose whether to:

Add an introductory sentence at the beginning of Fin (or your AI Agent name)'s first reply in an email conversation, letting the recipient know that the conversation is with an AI Agent. This is off by default but can be added via:

• The ‘Fin introduces itself’ step in Fin simple deployment for email.
• Adding a message step immediately before the Fin answer step in existing Fin over email workflows.
• Creating a new email workflow using the Fin over email workflow template, where a suggested, A/B tested introductory message is pre-populated.

Display an "AI Agent" footer below Fin (or your AI Agent name)'s signature on every email.

• The footer reads: “This answer was composed by [AI Agent name], [Workspace name]’s AI Agent.”
• The toggle that controls this is in Email Settings and is ON by default for all customers.

In some regions, letting your customers know they’re speaking with an AI Agent may be a legal requirement.
​