Policies & Playbooks

Put the sales playbook in every rep's pocket

Objection handling and battlecards, retrieved mid-call.

The pain

Your enablement team maintains battlecards, objection-handling guides, and pricing playbooks — and reps still improvise on calls, because nobody scrolls a 40-slide deck while a prospect is talking. New reps ramp slowly; tenured reps run on memory of last year's playbook.

How BeforeQuery solves it

Index the playbook, battlecards, and win/loss notes as a restricted internal knowledge base. Reps ask in Slack mid-call — "how do we counter the Kapa comparison?" — and get the current, approved answer with a citation. Knowledge base permissions keep competitive material internal, and question analytics show enablement which plays reps actually need.

How it works

1Index the sales playbook, battlecards, objection-handling guides, and win/loss notes as a restricted internal knowledge base.
2Grant chat permission to the sales team; competitive material stays invisible to everyone else.
3Reps ask in Slack mid-call — "how do we counter the Kapa comparison?" — and get the current approved answer with a citation.
4Enablement updates the playbook; the next sync updates every answer.
5Question analytics show which plays and objections reps actually search for.

What you get

Reps use the current playbook instead of last year's memory of it.

New reps ramp with senior-quality answers from their first call.

Competitive material stays governed behind permissions and restricted visibility.

Enablement prioritizes content from real question data, not guesses.

Features that make it work

Restricted internal knowledge base

Slack bot

Knowledge base chat permissions

Question analytics for enablement

Frequently asked questions

Can we keep battlecards internal-only?

Yes. Mark the documents restricted and scope the knowledge base with per-knowledge-base chat permissions — only workspace members with access can query it, and it is never exposed through public widgets or client keys.

How do reps use this during a live call?

Most teams use the Slack bot: the rep asks in a private channel or DM and gets a cited answer in seconds without leaving the call. The internal Ask portal offers the same assistant in the dashboard.

How long does setup take?

Most teams are live the same day. You connect a source — a docs URL, GitHub repo, Notion workspace, or a file upload — and BeforeQuery crawls, normalizes, chunks, and embeds the content automatically. The website widget is a single script tag, and the Slack/Discord bots install in a few clicks. There is no model to fine-tune and no infrastructure to run.

Are answers backed by citations?

Yes. Every answer includes a structured citations list with the URL, title, and excerpt of each source used, and the answer text cites sources inline. Users can click through to verify any claim against the original document — which is what makes the answers trustworthy enough for support, sales, and internal use.

Is my content used to train AI models?

No. Your indexed content, embeddings, and conversations are isolated to your workspace and are only used to answer your own questions. Content is never shared across customers, and data is encrypted at rest and in transit. Enterprise plans add OIDC/SAML SSO, audit logs, and data-residency options.

Which knowledge sources can I connect?

18+ source types: websites, GitHub, GitLab, Notion, Confluence, Google Drive, SharePoint, Shopify, Zendesk, Jira, Linear, Salesforce, Slack, Discourse, Stack Overflow, YouTube, OpenAPI specs, and direct file uploads (PDF, Markdown, TXT, HTML). Sources sync on a schedule, and GitHub/GitLab can re-index automatically via webhooks on every push.

What happens when the AI is not confident in an answer?

Answers are confidence-scored. When retrieval confidence falls below your threshold, BeforeQuery returns a transparent, configurable fallback — typically pointing users to your support channel — instead of guessing. Those unanswered questions are logged in knowledge gap analytics so you can close the gap in your docs.

Does BeforeQuery work in languages other than English?

Yes. BeforeQuery answers in the language of the question while retrieving from your knowledge base, even if your docs are English-only, with citations back to the original pages. Workspace analytics break questions down by language so you can see which markets are asking what.