Adding knowledge sources

Everything SalesGhost says on a call is grounded in the knowledge you give it. This page covers the mechanics of getting knowledge in (and out). For what to add, read what makes answers good — curation matters more than volume.

All of this lives in Settings → Knowledge Base.

Upload documents

SalesGhost accepts PDF, DOCX, TXT, and Markdown. Drop in the documents that don't live anywhere public: pricing sheets, internal FAQs, security overviews, competitor one-pagers. Once processed, a document's content is available to live answers on your next call.

When a document changes — new pricing, updated terms — remove the old version and upload the new one. The knowledge base is only as current as what's in it.

Scrape your website

Give SalesGhost a root URL — your marketing site, help docs, changelog — and it processes the pages for you. This is the fastest way to cover everything you've already published without uploading it piece by piece.

Re-run a scrape after significant site updates so answers reflect what's live, not what was live when you first connected.

Connect Slack

Connecting Slack brings in the knowledge that never makes it into documents — how your team actually answers the hard questions. It's the best source for tribal knowledge: the deal-desk answer to a discount ask, the real story on a roadmap item.

Company context

Separate from documents, the free-text company context field in Settings is where you describe your company in your own words: who you sell to, how you position, what tone you use. It's read on every call and shapes how suggestions are phrased. Five minutes writing it well pays off on every call after.

Personal vs organization scope

Every source has a scope:

• Personal — only your calls can draw on it. Good for your own notes, your territory's quirks, experiments you're not ready to share.
• Organization — shared with everyone on your team. This is where the canonical stuff belongs: the pricing sheet, the security overview, the approved competitive positioning.

If you're on a team, prefer organization scope for anything a teammate would also want mid-call. One well-maintained org knowledge base beats ten diverging personal ones.

Tip for admins: treat the org knowledge base like a product. Assign an owner, keep it lean, and refresh it quarterly. Stale or conflicting sources produce hedged answers for the whole team.

Removing sources

Remove any source from Settings → Knowledge Base — its content stops being used for answers. Do this proactively when documents go stale: two sources that disagree (an old pricing sheet next to a new one) make answers worse, not more thorough. When in doubt, delete the older one.