Can different bots post to different channels?

Yes. The integration is per bot, which is what makes it usable for agencies and for teams running separate bots per department.

Will it flood our channel?

Only if you send everything. Restrict it to escalations and captured leads and the volume matches the number of moments that genuinely need a person.

Can we reply from Slack?

The notification carries the conversation so the team can see the context and pick up through your normal reply route. Treat it as the alerting surface rather than the reply surface.

Configure

Send escalations and leads to Slack

Your team already has too many places to check. Escalations should arrive in the one they actually watch.

Start freeNo credit card. 2 minute setup.

Another inbox is another thing nobody checks

Notifications that live in the tool that generated them get attention for a fortnight. After that they are a tab nobody opens, and a time-sensitive escalation waits until someone happens to look.

Escalations sitting unread in a dashboard
Leads found hours after they were captured
No visibility for the team into what the assistant is handling
Response times determined by when someone remembers to check

Connect your workspace

In the bot's integration settings, connect Slack and authorise the workspace. The connection is per bot, so agencies running several clients can route each client's escalations to a different workspace or channel.

Choose the channel deliberately

A dedicated channel beats a busy general one, because notifications in a noisy channel are scrolled past. Whoever owns response time should be in it, and it should be quiet enough that a message in it means something.

The delivery channels panel with a webhook field prefilled with a Slack incoming webhook URL pattern, beside an email channel, each with a Send test lead button. — A Slack incoming webhook goes straight in the webhook field. Send test lead confirms it lands in the channel you intended before you depend on it.

Decide what gets sent

Escalations and captured leads are the two that matter. Sending every conversation turns the channel into noise within a day and guarantees the important ones are missed.

Escalations

Someone needs a person — this is the time-sensitive one.

Captured leads

High intent, and worth a fast reply.

Check the message contains the question

A notification saying 'new escalation' forces someone to go and look. One containing the actual question lets whoever sees it decide immediately whether it is theirs, which is the difference between a useful alert and an interruption.

Common questions

Can different bots post to different channels?: Yes. The integration is per bot, which is what makes it usable for agencies and for teams running separate bots per department.
Will it flood our channel?: Only if you send everything. Restrict it to escalations and captured leads and the volume matches the number of moments that genuinely need a person.
Can we reply from Slack?: The notification carries the conversation so the team can see the context and pick up through your normal reply route. Treat it as the alerting surface rather than the reply surface.