Chat on your site. Answered in Slack.

Route website chat into Slack

Web Chat
Slack

The fastest way to lose a website visitor is to make them wait. 66% expect a reply within five minutes, and a chat bubble nobody's watching is just a slower contact form. If your team lives in Slack all day, routing website chat into Slack puts every visitor's question in front of people who are already there - so the answer comes before they bounce.

Why this pairing

Why teams send Web Chat to Slack

Website chat lives or dies on speed; Slack is where your team is fastest. Pairing them turns the bubble on your site into a Slack message your team can answer in seconds, instead of a widget that quietly waits.

  • Visitors start a conversation on your site instantly - no email, no signup.
  • Every chat lands in Slack, where your team already works, so it gets seen fast.
  • 66% of customers expect a reply within five minutes; answering from Slack is how busy teams hit that.
  • Each chat is its own Slack conversation, easy to claim and hand off.

How it works

One thread, both ends

A visitor opens the chat bubble on your site and types. No login, no app to install - the conversation starts the moment they hit send.

InboxBarn routes that conversation into Slack as a channel per conversation in the workspace your team already lives in. Your team reads it and answers it right there, in the tool they already have open - no portal to log into, no queue to refresh.

The reply always goes back on the channel the customer used.
Whether your agent types in Slack, the dashboard, or somewhere else entirely, the answer is delivered to the chat bubble on your site, where they were already waiting. The customer sees one continuous conversation in the tool they chose - they never know, or need to know, where the work actually happened.

Setup

Set it up in three steps

  1. 1

    Drop the widget on your site

    Paste one <script> tag, or use the inline “On Site” container for an embedded panel. The widget loads in its own Shadow DOM, so it never collides with your styles.

  2. 2

    Connect your Slack workspace

    Authorize the workspace and choose where routed conversations should appear. Your team replies in the channel; the customer never sees Slack.

  3. 3

    Pick a category and go live

    Map the source to a routing category (general, billing, VIP, sales) and point your destination at it. Send a test message - it should appear on the other side in seconds, and your reply should land right back where it started.

77 of the Fortune 100

use Slack. Slack is already open on the screens of the people who answer your customers - routing to it just meets them there.

Source: Slack, 2024

Questions

Frequently asked

Does the visitor need Slack?

No. They chat on your site and see your reply in the bubble. Slack is entirely your side.

How do I install the widget?

One <script> tag, or the inline “On Site” container. It runs in a Shadow DOM, so your styles and the widget never interfere.

Where do my Slack replies appear?

Live in the visitor's chat bubble on your site - typed in Slack, delivered to them in real time.

Can sales and support chats go to different channels?

Yes. Conversations are categorized, and each Slack channel subscribes to the categories you assign.

Connect Web Chat to Slack today.

Every channel is included on every plan - no per-channel taxes. Wire up the bridge in a few minutes and answer your customers from the tool your team already lives in.