Skip to content
AskVault Docs
Try Free →

How to connect Slack to AskVault

Written by , Founder, AskVault · Reviewed by Aashiq
Last updated: · 4 min read

When to use Slack as the channel

Slack is the right channel for any case where the chat lives inside a Slack workspace instead of on a website. Three common patterns:

  1. Internal knowledge-base bot. Employees ask the bot questions in #engineering, #hr-faqs, or #it-helpdesk. Bot answers from your indexed Confluence, Notion, Google Drive content.
  2. Customer-facing support in shared Slack channels. Some B2B SaaS companies run shared Slack channels with their enterprise customers. The bot answers product questions inline.
  3. Sales enablement. RFQ-response bot embedded in #sales. Reps DM the bot or mention it in deal channels.

For external-facing chat (your website visitors, your WhatsApp customers), use the relevant channel instead. Slack is for people who already have Slack accounts.

Setup

The setup is one OAuth flow.

  1. Open AskVault. Go to Deploy > Slack.
  2. Click Install Slack App. A new tab opens with Slack's standard OAuth consent screen.
  3. Pick your Slack workspace. If you're a member of multiple workspaces, choose the right one from the dropdown at the top right.
  4. Review the permissions and click Allow. AskVault requests four scopes: chat:write (send messages), app_mentions:read (listen for @-mentions), channels:read (list channels the bot is in), users:read (resolve user IDs to names for analytics). No other scopes.
  5. You're redirected back to AskVault. The connection shows as active.
  6. Invite the bot to channels. In Slack, open any channel where you want the bot active. Type /invite @AskVault. The bot joins the channel.

That's the whole setup. Direct messages to the bot work immediately without invitation.

How team members use the bot

Three ways to invoke it.

Direct messages. Open the AskVault bot in Slack's left sidebar (under "Apps"). Send any question. The bot replies in the DM.

@-mentions in channels. In a channel the bot has been invited to, mention it: @AskVault what's our refund policy?. The bot replies in the thread.

Slash command (recommended for quick queries). /askvault what's our refund policy? works in any channel without needing to invite the bot first. Available across the entire workspace once the app is installed.

The slash command is the lowest-friction way to use the bot. You don't have to remember which channels it's in. Type the slash command, get the answer, move on.

Multiple channels, different bots

Sometimes you want different bots in different channels (e.g., a sales-knowledge bot in #sales and an HR-policy bot in #hr-faqs). Two patterns work:

Pattern 1: one workspace, audience-tagged content. All content lives in one AskVault workspace. Tag HR documents with audience: ["hr_team"] and route by channel using automation rules. Cheaper and simpler.

Pattern 2: separate workspaces per bot. Create separate AskVault workspaces, each with its own knowledge base. Install the Slack app in each workspace. Slack will distinguish them by app name. More overhead but cleaner if the bots really are different products.

Most teams start with Pattern 1.

Identity verification on Slack

Slack's OAuth flow already verifies the calling user's identity. AskVault gets the verified Slack user_id on every message, so you don't need an HMAC verification step on top.

For audience-based scoping (HR documents only visible to HR team), map Slack user groups to AskVault audience tags under Settings > Slack > User Group Mapping. When a Slack user from the @hr-team user group queries the bot, their request carries the hr_team audience tag automatically.

This requires the usergroups:read scope. AskVault will prompt you to add the scope when you enable user group mapping. Growth+

Limits and pricing

Slack's free plan limits message history to 90 days; bot messages count against this. Paid Slack plans don't have this limit.

Slack's API has rate limits per workspace: 1 message per second per channel for non-Block-Kit messages. AskVault stays well under this in practice.

The Slack channel is included on the Growth plan and above. Free and Starter plans don't include Slack. Growth+

Common pitfalls

Bot doesn't respond when @-mentioned. Either the bot isn't a member of the channel (run /invite @AskVault) or your AskVault workspace's query quota is exhausted (check Billing > Usage).

Bot responds in some channels but not others. Check Deploy > Slack > Channels for which channels are enabled. The default is to respond in any channel the bot is invited to, but you can restrict to a subset.

Slash command doesn't work. The Slack app may not have the slash command permission set. Re-install the app from Deploy > Slack > Reinstall to refresh permissions.

Multiple AskVault bots in one Slack workspace. This happens when two team members each connect their own AskVault account to the same Slack workspace. Either disconnect one or rename them so users know which is which.

FAQ

Does this work with Slack Enterprise Grid?

Yes. Enterprise Grid customers can install the AskVault app at the workspace level or the org level. Org-level install requires Slack admin approval and gives the bot access across all workspaces in the org.

Can the bot post to a channel automatically (without being asked)?

Yes, with chat:write.customize scope (which we request only when needed). Useful for sending automated alerts when the knowledge.gap_detected webhook fires, so the team gets notified when employees ask unanswered questions.

Will Slack count bot messages against my Slack message limit?

Yes, bot messages count toward your Slack workspace's message history. On the free Slack plan, this means bot conversations older than 90 days roll off. Use AskVault's Live Chat > Conversations for the canonical conversation history; Slack is just the surface.

Can I uninstall cleanly?

Yes. Slack admin can revoke the AskVault app from Workspace settings > Apps & integrations. AskVault will detect the revocation and mark the channel disconnected. No data is left behind in Slack; conversations remain in your AskVault dashboard.

How do I escalate from bot to a human in Slack?

Enable the escalate_to_human skill. When triggered, the bot pings a designated channel (or a specific user) and stops auto-responding to that thread. A human takes over. The conversation continues in-thread; your agent's messages go straight from Slack to the customer. Growth+

Was this page helpful?