Slack
Post the leads your lead forms capture to a Slack channel, connected with one sign-in.
Post each lead your lead forms capture to a Slack channel as a formatted message when it arrives; a lead created from a booking is not posted. You set it up in Dashboard → Integrations, on the Slack tile. How that screen works is covered in Integrations.
What it does
When a visitor leaves their details, the lead appears in the Slack channel you picked as a Block Kit message with the fields your lead form collected. Slack is one more place leads go: the lead is still saved in Dashboard → Leads, and email and webhook delivery keep working alongside it.
You connect with one sign-in to Slack — there is no webhook address to copy.
Replying from Slack
Each lead card tells you how to answer the visitor from Slack: reply in a thread on that message and mention the app. The text after the mention is sent to the visitor in their live chat as a reply from your team, and the app confirms in the thread with Sent to the visitor. When a reply is not delivered, the app says why in the thread: the site's plan does not include Live Agent, the thread does not match a conversation, the message is only a mention or is too long for a chat reply, or the visitor arrived on a messaging channel such as WhatsApp (those are answered from the dashboard). A lead that arrived without a live chat says on its card that a reply there is not delivered.
To make this work the app asks Slack to let it read messages that mention it, in channels it has been added to, not the rest of the channel's traffic. The link between each lead thread and its conversation is kept for the period in the Data Retention Policy.
What you need
- A Slack workspace where you are allowed to install apps.
- The channel the leads should go to. A private channel works once the app has been added to it (see Settings).
- A plan that includes Slack — see Plan and limits.
How to connect
- Connect. Open the Slack tile and click Connect Slack workspace. Slack opens in a separate window; sign in, review what the app asks for — posting messages, listing your channels, reading messages that mention it, and a channel to post to — allow it, and the window closes by itself. While that window is open the panel waits for it, and if you try to close the panel it asks first — closing it would abandon the connection.
- Configure. Pick the Destination channel from the list, which loads from your workspace. Until you pick one, leads go to the channel you chose in Slack's window, though the picker shows no channel.
- Verify. Click Send test message — it becomes available once a channel is picked — and look for it in the channel.
Settings
- Destination channel — the one channel leads are posted to. The list comes from your workspace; Refresh reloads it.
- Private channels appear once the app is in them. In Slack, mention the app in a message in that channel, or open the channel's details and add the app from the Agents & apps tab, then click Refresh.
The channel is saved the moment you pick it. Each website has one Slack connection, and leads go to that one channel; they are not split between channels or workspaces. The access Slack grants us is stored encrypted.
Check that it works
Click Send test message. The message should appear in the channel within a few seconds. The tile shows Connected from the moment the connection succeeds, and the panel marks the workspace Active.
If it isn't working
| What you see | What to do |
|---|---|
| Popup blocked | Your browser stopped the Slack window. Allow pop-ups for the dashboard and click Connect Slack workspace again. |
| Slack connection not confirmed | The Slack window closed without reporting back. The panel re-reads the connection; if Slack still shows as not connected, start again. |
| The app isn't in that channel yet | Add the app to the channel (mention it there, or add it from the channel's Agents & apps tab) and pick the channel again. |
| Could not load Slack channels | Click Refresh. If it keeps failing, reconnect. |
| The Slack app is missing a permission this needs | The app in your workspace was installed without a permission that loading channels, saving the channel or sending a test message needs. Click Disconnect, then Connect Slack workspace again and allow what Slack asks for in its window; then pick the channel again. |
| Error on the tile, and the panel says This Slack connection is no longer active | Slack withdrew the access — for example the app was removed from the workspace. Open the tile and click Reconnect Slack, or Remove to drop the connection. |
A broken connection is also listed in the banner at the top of the Integrations screen; clicking it opens the Slack panel.
Disconnect, and what happens to your data
Open the Slack tile, click Disconnect and confirm in the Disconnect Slack? dialog. From then on no lead is posted to Slack. The access Slack granted is removed on our side at once.
Disconnecting also asks Slack, once, to revoke that access, unless the same workspace is still connected to another website on our service, whether yours or someone else's, or the stored access does not name its workspace. A revoke removes our bot from your channels but leaves our app installed in the workspace. If we did not ask, or Slack does not confirm it, the connection is still removed on our side and the screen does not tell you. To take our app out of the workspace when no other website should keep using it, remove it in Slack.
Messages already posted stay in your Slack channel. Leads stay in Dashboard → Leads, and email and webhook delivery are not affected. To move to another workspace, disconnect first, then connect the new one and pick the destination channel again.
Plan and limits
Which plans include Slack, and how many workspaces a website can connect: What each integration allows, by plan.