Skip to content
AskVault Docs
Try Free →

How to connect Slack to AskVault

Written by Joseph Russo, Principal Architect, Networks and Tech, AskVault · Reviewed by Allison Chan
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 Channels > 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 these scopes: commands (reserved for slash commands, which AskVault does not offer yet), chat:write (send messages), app_mentions:read (listen for @-mentions), channels:read (list channels the bot is in), channels:history and channels:join (read and join channels for context), im:history, im:read, and im:write (direct messages), and users:read (resolve user IDs to names for analytics).
  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

Two 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 same channel.

Slash commands such as /ask aren't supported yet. Use a DM or an @-mention instead.

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).

One AskVault workspace, Internal sources. All content lives in one AskVault workspace. Set HR documents to Internal so they stay out of public channels. This is the pattern that works today.

One Slack workspace connects to one AskVault workspace. Every message from a Slack workspace is answered by a single AskVault workspace, so installing AskVault into the same Slack workspace from a second AskVault workspace doesn't give you a second bot: only one of them would ever answer. To move a Slack workspace to a different AskVault workspace, disconnect it in the old one first. If you no longer have access to the old one, email [email protected].

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.

AskVault does not map Slack user groups to per-team content scopes. A knowledge source's Audience is public or internal and nothing else: to give different teams different content, use a separate AskVault workspace for each team, each connected to its own Slack workspace.

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 message quota is exhausted (check Billing > Usage).

Bot responds in some channels but not others. The bot answers in channels it has been invited to. Invite it with /invite @YourBot in the channels where it should answer, and remove it from those where it should not.

Slash command doesn't work. AskVault doesn't support slash commands yet. Send the bot a DM, or @-mention it in a channel it has been invited to.

"Slack wasn't connected" after approving. Finish the install in the same browser where you clicked Install Slack App. Don't forward Slack's approval link to someone else: if a Slack admin has to approve the app, they approve your request inside Slack, and then you click Install Slack App again yourself. This stops anyone from connecting their AskVault agent to your Slack by getting you to approve a link they sent.

Two people connected the same Slack workspace. Only one AskVault workspace answers a given Slack workspace, so the second connection does not give you a second bot. Disconnect the one you do not want.

FAQ

Does this work with Slack Enterprise Grid?

AskVault installs per Slack workspace. Org-level installation across an Enterprise Grid is not supported today, so install it in each workspace that needs it.

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

Not through the bot, which only replies when someone messages or mentions it. For alerts in Slack, add a Slack incoming-webhook URL as an AskVault webhook endpoint; AskVault formats events such as knowledge.gap_detected for Slack. For frustrated-customer alerts, use sentiment_router.

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 Inbox > Chat History 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. The bot stops answering; disconnect the channel in AskVault too so its status is accurate. No data is left behind in Slack; conversations remain in your AskVault dashboard.

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

The escalate_to_human skill works in Slack, but replies typed in the AskVault Help Desk inbox are not sent back to Slack today. If the handoff goes through, the AI stops answering that thread and the conversation appears in the Help Desk. Reply to the person in Slack directly. The skill does not ping a channel or user. Growth+

Was this page helpful?