npx @buildinternet/releases get intercomRecently shipped Fin Voice procedures and a batch of macro upgrades.
Fin Voice procedures turn plain-language descriptions into working phone flows. Operator, Fin's agent for customer operations, drafts the steps — including what happens when no order is found or a call needs a human — and you test and approve them before any caller reaches them.
walks through the build and the call. Fin Memory still carries customer context across conversations.Macros absorbed the work teams used text expanders for. Fill-in fields (text, long text, choice; optional or required) prompt for details and drop only the finished reply into the composer, with a live preview. Macros can now be applied while creating a ticket, so the message becomes the first reply or note and follow-up actions run automatically.
Inbox hygiene got several fixes.
Phone and reporting gained visibility. Outbound calls that don't connect now show a specific reason — invalid number, line busy, declined, blocked by carrier, or region not permitted. Reports' custom metrics let teams filter built-in metrics or divide one by another, calculated across full history. Tooltips can be sized Small, Medium, or Large for accessibility, and Shopify replacement orders can ship to a newly typed address from the inbox.
Search conversation in the conversation menu finds text within the chat being viewed, with every match highlighted and navigation between results. Previously, finding something in a long Messenger conversation meant scrolling through the message list.
Teammates can dictate replies and notes in the Inbox composer for up to two minutes, with the transcription appearing as text at the cursor for editing before sending.
Assigning SMS numbers to a brand makes Intercom automatically send from the matching number whenever that brand is selected in the Inbox or Outbound composer, instead of manually picking a number per send. Replies to a branded number are tagged with that brand, and Fin answers from the brand's Help Center rather than the workspace default.
Teammates with the Can manage shared macros permission can now view everyone's personal macros in Macro settings. From there they can convert a useful one to a shared macro, or delete one that's out of date. Your best replies get shared, and old ones don't pile up.
Customers move, mistype addresses, or want a replacement delivered to work. Teammates can now type a new shipping address right in the Shopify replacement order form in the Inbox, and pick the state or province from Shopify's own list, so the order reaches the warehouse with an…
New feature — Outbound Messaging
Reports covers a lot of ground, but not every team's number is in the built-in set. A closure rate for email only, or a reopen rate on a single tag, wasn't something you could put on a chart. Now you can build it yourself — by applying your own filters to a built-in metric, or…
Until now, an outbound call that didn't connect showed a generic result, so teammates couldn't tell whether the number was wrong, the line was busy, or the call was blocked.
Teammates' avatars now appear on conversation rows in the inbox Table view, so you can see at a glance when a colleague is already handling a conversation and avoid duplicate replies.
Creating a ticket and applying a macro used to be two steps: create the ticket, reopen it, then apply the macro. Now you can do both at once.
Reading code in conversations just got easier. Code now renders in its own scrollable block, complete with syntax highlighting, line numbers, and a one-click copy button.
Until now, connecting Fin to your tools meant building a data connector yourself: configuring the technical details by hand. Data connector templates are now generally available, with ready-to-install templates across Stripe, Shopify and Statuspage.
Getting the current contents of a View out of Intercom meant rebuilding its filters in a report or copying rows by hand — and a report answers a different question anyway: what happened over a date range, not what matches right now.
Until now, the Data Connector health page showed HTTP status codes as a single snapshot — so you couldn't tell when a connector started failing or whether a fix held. Now status codes appear as a chart over time, right alongside the existing latency chart, on whatever time range…
Until now, a ticket's time counted only against the team currently assigned — so once it handed off, the earlier team's time disappeared from your reports and the path it took couldn't be reported on at all.
The data Fin needs most to resolve conversations, like orders, subscriptions, usage, and billing, often lives in Snowflake, and until now Fin couldn't reach it. With the Snowflake MCP Connector, Fin securely connects directly to an MCP server running inside your own Snowflake…
