The Messenger Design Choices That Decide Whether Visitors Talk to Fin AI

Most businesses running Fin AI spend their tuning time on the answers: writing custom answers, cleaning up help center articles, watching resolution rates. All of that matters. But the widget wrapped around Fin AI, the thing a visitor actually sees before any answer happens, gets almost no attention. That's a mistake, because the Messenger's design decides whether people open the chat at all, and what they expect once they do.

Launcher position and color are not just cosmetic

In Intercom, the launcher (the button that opens the Messenger) has its own settings for position and color, found under Settings > Messenger. You can push it left or right on desktop and tablet, and set a primary color that carries across buttons and highlights inside the chat window. You can also upload separate logos for light and dark themes, and choose whether the Messenger stays in a fixed mode or matches the visitor's system setting automatically.

None of this changes what Fin AI knows or how it reasons. But it changes whether the launcher reads as "part of this website" or as a bolted-on widget that clashes with everything else on the page. A launcher that fights your site's color palette or sits somewhere unexpected trains visitors to ignore it, the same way people learn to ignore banner ads. If your Messenger looks like an afterthought, fewer people will treat Fin AI as worth talking to.

The welcome message sets expectations before Fin says a word

Every visitor who opens your Messenger sees a welcome message first. This is configured under Settings > Messenger > Web > Content, and it supports dozens of languages if you serve an international audience. Intercom's own guidance breaks its job into three parts: say hello, explain what to expect, and give the visitor a sense of who they're about to talk to. For accounts running Fin AI Agent, this greeting moves into Fin AI Agent > Deploy > Chat instead, so you control specifically how Fin introduces itself, separate from any human-facing greeting.

This is where a lot of teams undersell what they've built. A generic greeting tells the visitor nothing about the fact that they're about to get an instant, always-available answer instead of waiting in a queue. A message that plainly states what Fin AI can actually do, whether that's answering a question on the spot, pulling up an order, or walking through a setup step, sets a visitor up to use it instead of asking for a human purely out of habit. You can also turn the welcome message off on specific pages using display conditions under Settings > Channel > Content, worth doing anywhere a chat prompt would be more distracting than helpful.

Decide who visitors see first: Fin, a human, or a menu

The Messenger has a "Spaces" setting that controls which sections show up: Home, Messages, Tickets, Help, News, and Tasks. Combined with the launch behavior setting, this determines whether a visitor lands on a home screen with options, or goes straight into a conversation. You can also customize the call-to-action button text separately for human-staffed conversations versus Fin AI, so a visitor can see a "Chat with us" option and a distinct option for getting an instant answer from Fin, rather than one ambiguous button that could mean either.

This matters because dumping every visitor straight into a blank conversation puts all the weight on the first message they type. A clear home screen, showing suggested topics or a visible Fin AI option, gives visitors a lower-effort way in. Fin AI Agent can also surface suggested prompts drawn from your site content, so visitors tap a question instead of composing one from scratch, which tends to produce shorter, more specific first messages that are easier for Fin AI to resolve correctly.

What "let Fin answer first" actually changes

Intercom offers a workflow template, found under Fin AI Agent > Workflows, called "Let Fin AI Agent answer first." Turning it on routes every new conversation to Fin before a human sees it, and Fin escalates only once it identifies that a person is needed, using conversation topics to route to the right team. Intercom recommends starting with a single channel, like your website, before extending it to email, SMS, or other channels, since steps can behave differently across channels. Worth knowing too: topic-based routing needs a real volume of history, Intercom cites a threshold of at least 5,000 total conversations before it can generate topic suggestions, so a newer account may need to route escalations manually at first.

Turning this setting on without adjusting the surrounding design is a common half-measure. If the welcome message still implies a human is on the other end, or the launcher looks identical to a plain support widget, visitors won't behave any differently even though the backend routing changed. The setting and the design need to move together.

Rethinking the entry point instead of just restyling it

Some of the sharper thinking here comes from inside Intercom's own product team, who've argued that an AI support widget shouldn't just be a repainted chat bubble. That bubble icon has spent over a decade training people to treat it as a last resort, something you click after you're already frustrated, which is the wrong signal when the assistant behind it can help before a problem develops, in sales or onboarding especially. One redesign they tested dropped the bubble for a small, closeable bar drawing a handful of likely questions from the site's own content, so a visitor taps an option instead of typing from a blank box, with light motion cues showing when the assistant is actually working.

The specific layout won't fit every business, but the underlying idea generalizes well. Visibility, color, motion, and wording all shape whether an AI entry point feels helpful or feels like clutter, and getting that balance right has, in Intercom's own reporting on early tests, been tied to a real lift in how often visitors start a conversation at all. If you're only touching primary colors and a logo upload, you're using a small slice of what the Messenger settings actually let you control.

A short checklist before you leave it alone

Confirm your launcher color and position actually match your site rather than the Intercom default. Rewrite your welcome message to say plainly that visitors get an instant AI answer, not a vague greeting. Check that your CTA button text for Fin AI reads differently from your human chat option. Decide deliberately whether visitors land on a home screen with suggested questions or go straight into a blank conversation. And if you're turning on Fin-first routing, do it one channel at a time and watch how it behaves before expanding.

None of this replaces the work of training Fin AI on good content. But a well-tuned AI agent sitting behind a widget nobody wants to click is wasted work. Auditing the Messenger setup alongside the Fin AI configuration behind it is exactly the kind of setup and tuning work I help businesses with, so feel free to get in touch if you want a second pair of eyes on it.

Cover photo by kuu akura on Unsplash.