Your AI chatbot captures a lead, requests a human handoff, or hears from a returning customer — and your Slack channel lights up in under two seconds. No webhooks, no Zapier, no missed leads.
Free on every plan · Works with any Slack workspace · One-click OAuth
Four steps, no engineer required.
In your InsiteChat dashboard, open Webhooks & Integrations and click "Connect Slack." You'll be taken to a standard Slack OAuth screen — authorize, and InsiteChat is installed in your workspace.
From the dropdown, choose which Slack channel should receive chatbot events. You can pick a public channel or a private one you've invited @InsiteChat to.
Toggle on any combination of "new lead," "conversation started," "escalation requested," and "offline message received." Each can route to a different channel.
That's it. The next time someone submits a lead form on your site, the notification lands in your chosen Slack channel in under two seconds.
Built for teams that already live in Slack — not a generic notification dump.
The moment a visitor submits the lead form or hits the escalation button, your Slack channel gets pinged. No polling, no delays, no email lag.
Every notification includes the visitor's name, email, phone, and the full chatbot conversation transcript so your SDR has context before they reply.
When a visitor clicks "talk to a human," the right Slack channel gets a banner alert with a "Take over" link that deep-links into your InsiteChat conversation view.
Send leads to #sales, escalations to #support, and outages to #ops. Multiple event types can route to multiple channels — it's all configurable.
Notifications use Slack's Block Kit with structured fields, buttons, and color accents — not a wall of plain text. Easy to scan on mobile and desktop.
Connect Slack through standard OAuth in under 30 seconds. No webhook URLs to paste, no manual Slack app configuration, no engineer required.
Three teams who set this up in their first week with InsiteChat and never look back.
Pipe lead submissions to your #sales-alerts channel. SDRs see them in real time, pick them up with a reaction, and reach out within minutes while intent is still hot.
Route escalation events to #support. On-call agents see which conversation needs a human, click through to InsiteChat, and take over the chat without the visitor waiting.
Most SaaS sites get traffic outside business hours. Use Slack's mobile app + scheduled notifications so your weekend on-call knows when a paying customer is stuck.
Each event type can go to a different channel, so #sales and #support don't drown each other out.
InsiteChat is a verified Slack application with the minimum required permissions: post to channels and list channels you've granted access to. We never read your existing Slack messages. You can revoke access at any time from your Slack workspace's "Manage Apps" page.
Everything you need to know about the InsiteChat + Slack integration.
In your InsiteChat dashboard, open the Webhooks & Integrations tab, click "Connect Slack," and authorize the app. Pick a channel, choose which events trigger notifications, and save. The whole setup takes under a minute.
No. InsiteChat is a verified Slack app — you just authorize it like any other Slack integration (Zoom, Notion, Loom, etc.). We handle all the Slack API plumbing.
Four event types out of the box: new lead submitted, conversation started, escalation requested (visitor clicks "talk to a human"), and offline message received. Each event type can route to a different Slack channel.
Yes. You might pipe lead submissions to #sales-alerts and escalations to #support. Configure each event type independently from the InsiteChat dashboard.
We use Slack Block Kit to format notifications with structured fields — visitor name, email, phone, conversation excerpt, and a button linking back to InsiteChat. Much more scannable than a wall of plain text.
No per-message cost or cap. Slack workspaces have their own API limits (~1 message per second per channel) which InsiteChat respects automatically with a small queue.
Yes. Disconnecting Slack stops future notifications but all historical messages stay in your Slack channels — they're just regular messages. Previously captured leads remain in your InsiteChat Leads dashboard.
No. The Slack integration is free on every InsiteChat plan, including the free tier. You pay only for InsiteChat message volume — no per-notification fee, no "integration add-on."
Direct webhooks force you to write code that formats payloads, retries on Slack rate limits, manages secrets, and handles channel routing logic. Our Slack app is OAuth-installed, formats messages with Block Kit automatically, picks the right channel per event type, and recovers from API errors. For a non-engineering team it saves a week of setup; for an engineering team it saves the maintenance tax.
Not from Slack itself. The Slack notification includes a button that opens the conversation in the InsiteChat Human Support dashboard, where you reply. We do not push agent replies through Slack threads because we want one canonical conversation log per visitor — having half the thread in Slack and half in our dashboard creates ambiguity in audit and reporting.
Yes. After OAuth, invite the InsiteChat bot to any private channel with `/invite @InsiteChat`, then pick that private channel from the routing dropdown. Slack does not allow OAuth apps to auto-discover private channels for privacy reasons.
Notifications queue in our backend (Celery) and retry with exponential backoff. If Slack is unreachable for more than 6 hours we mark the delivery as failed, log it, and email you a daily summary of any drops. The lead and conversation data themselves are always saved in InsiteChat — the Slack delivery is just one downstream notification target.
V1 uses a fixed Block Kit template optimized for scannability — visitor name, email, conversation excerpt, source page, "Open in InsiteChat" button. Custom templates are on the roadmap; for now, if you need a different format, use the Zapier integration which gives you a Slack action with full template control.
Zapier works but adds 5–30 seconds of delay (depending on your Zapier plan tier) and counts each notification toward your Zapier task quota. The native Slack integration is sub-2-second and has no per-notification quota. Use native Slack for high-volume teams, Zapier for low-volume teams that already pay for Zapier.
Free on every plan. Set up in 60 seconds. Never miss a hot lead again.
Get started free