Slack
Connect a Slack workspace so your AI agent answers questions in Slack and your team gets instant alerts about qualified leads and customers who ask for a human. Replies come from the same knowledge base, live store data and credit rules as your website chatbot.
What it does
- •Answers in Slack — @mention the bot in a channel, or send it a direct message. Replies appear in a thread.
- •Qualified-lead alerts — when a lead scores above the minimum you set (default 50 out of 100), a summary with the customer's details is posted to the channel you choose.
- •Human-handoff alerts — when a conversation is escalated to a person, your team is notified with the reason and a link to the conversation.
- •Buttons — Take over, Reply (for Slack conversations) and Resolve, directly under the alert.
Connecting
Open Integrations → Slack
Approve the permissions
Choose channels
Send a test
Lead scoring
Each lead gets a score from 0 to 100: email (25), phone (20), name (10), company (10), a detailed message (10), buying-intent wording such as pricing or quote (15), a handoff request (10) and an active conversation of three or more messages (5). An alert is sent when the score reaches the rule's minimum.
AI replies and credits
- •Each AI answer uses credits exactly like a website chat message, and appears in your Inbox and analytics with the Slack source.
- •Use the AI replies switch on the Slack page to stop answering messages while keeping the alerts.
- •If a person has taken over a conversation, the AI stays out of it.
- •If your plan's credits run out, the bot tells the user it cannot answer right now.
Taking over from Slack
When the interactive buttons are enabled, Take over assigns the conversation to the matching AIChatVault user (matched by email) and pauses the AI. Reply opens a form and sends your message to the customer in their Slack thread. Resolve closes the handoff. The alert updates to show who acted.
/invite @YourBot.Permissions the Slack app asks for
AIChatVault asks only for the permissions its features need. It does not request access to read the history of your channels: it receives only messages that mention the bot and direct messages sent to the bot.
- •
app_mentions:read— see when someone mentions the bot in a channel. - •
im:historyandim:read— receive and read direct messages sent to the bot. - •
chat:writeandchat:write.public— post answers and alerts, including in public channels the bot has not joined. - •
channels:readandgroups:read— list public and private channels so you can choose where alerts go. - •
team:read— show your workspace name on the connection. - •
users:read— show who is writing and who took over a conversation. - •Optional:
users:read.email— match a Slack person to a teammate by email when they take over, and capture an email address for Slack leads.
Private channels: invite the bot with /invite @AIChatVault before using them for alerts or questions.
Security and data handling
- •Every request from Slack is verified with Slack’s request signature and rejected if the signature is invalid or the request is more than five minutes old.
- •Slack retries and repeated events are recognised, so the same message is processed once.
- •Your workspace access token is stored encrypted. Each chatbot connects its own workspace, and a connection is only used for that chatbot’s organization.
- •Slack conversations are saved in your AIChatVault inbox like conversations from other channels, and AI answers use credits in the same way.
- •You can pause the integration, switch off AI replies, or disconnect at any time. Disconnecting removes the stored access token; you can also remove the app from your Slack workspace settings.
Disconnecting
Click Disconnect on the Slack page. Alerts and answers stop immediately and the stored access token is deleted. Conversation history remains in your Inbox.
