ConnectWiz for Slack
Early accessSlack messages, answered with a real process behind them.
Messages from Slack land in the same routed, AI-assisted inbox as every other channel — with the security engineering Slack deserves and the current scope stated honestly: text conversations, in early access.
Confirmed — a rate-limit misconfig on our side. Fix deploying now, ETA 20 min. I’ll post here the moment it’s verified.
The case for the channel
Why Slack belongs in a support stack
Where B2B already lives
Your biggest clients ask questions in Slack because that’s where they work — meeting them there feels premium to them and, with a bridge, stays orderly for you.
History that outlives channels
Client Slack channels get archived and renamed; the ConnectWiz record doesn’t. Every promise made in Slack stays on the customer’s permanent history.
Internal helpdesks too
Teams bridge IT, HR and ops channels into the same queue — routing, ownership and history on internal requests, with the same mechanics.
Connect & security
Engineered like a channel, not bolted on like a plugin
Every Slack event is cryptographically verified and deduplicated before it can touch a conversation — the boring guarantees that make a bridge trustworthy.
Two secrets, both checked
The bot token is validated against Slack’s auth API before anything saves, and the signing secret proves every inbound event — Slack’s challenge handshake is answered automatically.
Cryptographic inbound
Every event is HMAC-verified over the raw body — Slack’s v0 scheme, compared in constant time — with a 300-second replay window so a captured request can’t be re-fired at you later.
Loop-proof by filter
Bot events and our own echoes are dropped before threading — the classic bridge failure (two bots answering each other forever) is filtered out at the door.
Replies land where they started
Each outbound reply posts back to the exact DM or channel the message came from — the address is kept fresh on the contact, never guessed.
The inbox
The full inbox treatment, from message one
Routed conversations
Slack messages land as conversations with department routing, assignment, tags, internal notes with @mentions and full history — on desktop and the agent mobile app.
Wiz answers first
The AI agent answers from your own content in 52 languages, escalates to humans with the thread attached, and hands back with one click — the same brain as every other channel.
One customer record
The Slack identity joins the same CRM contact as email and every other channel — one person, one history, one consent state.
Two-way translation
Agents read incoming messages in their language on demand and send drafts translated into the customer’s — per message, cached for the next reader.
Business-hours aware
Out-of-hours messages get honest expectations and land at the top of the morning queue; the first-response clock measures humans, not bots.
Text, reliably
Two-way text messaging is the scope today — sent through Slack’s official API, tracked on the conversation, never silently dropped.
Under the hood
The plumbing that makes "early access" safe to run
Processed exactly once
Every event claims a unique key in a dedicated ledger before processing; Slack’s retries and duplicates are recognized at the database layer and dropped — one message never becomes two.
The same pipeline as everything
Inbound goes through the exact message service the widget and WhatsApp use — routing, AI triggering, blocking and history behave identically, because they are identical.
Failures are named
A rejected send marks the message failed with the reason on the thread — never a silent drop, never a fake tick.
No invented limits
Slack publishes no hard text ceiling, so we impose none — an invented limit would reject messages that deliver today, and honesty cuts both ways.
The honest scope
What "early access" means here — in writing
Enabled with you, not at you
The integration is built and verified, but hasn’t yet carried enough live production traffic for an unconditional "live" label — so we enable it per workspace, with our team alongside. That’s what the badge means.
Text today
Media, buttons and rich elements are on the roadmap and deliberately unpromised — a page that sells a composer feature that isn’t there yet costs more trust than it earns.
Optimistic delivery
Sends are confirmed at the API level; per-message delivery receipts aren’t wired on this channel yet, and the thread doesn’t pretend otherwise.
One manual step
Slack has no API for registering event URLs, so pasting the Request URL into your Slack app config is a one-time manual step — our guide shows exactly where.
Roadmap & graduation
What ships next — and what flips the badge
The graduation bar is measurement, not marketing: enough live production traffic to verify the channel end to end. Then the badge comes off and these land, in order.
Media & files
Attachments in both directions are the first graduation item — unpromised until they ship, stated here instead of implied.
Richer identity mapping
Deeper agent↔Slack-user mapping and per-client channel structure are being explored with early-access teams — tell us your setup.
Delivery receipts
Per-message receipts aren’t wired on this channel yet; sends are confirmed at the API level and the thread doesn’t pretend otherwise.
Standard channel
What it costs
ConnectWiz side
- Slack is a standard channel: one of your plan’s included picks, or $9/month as an add-on — the same price during early access
- Early access adds hands: we enable and watch the channel with you, at no extra cost
- Conversations count toward your plan’s normal allowance; AI answers draw on your AI credits
Slack side
Your Slack account, verification and any platform-side terms stay between you and Slack — ConnectWiz adds no markup and never proxies your account relationship.
Your biggest accounts already live in Slack.
Request early access and we’ll enable the channel with you — honestly scoped from day one.