What makes live answers good

Updated 8 July 2026

SalesGhost's live answers are retrieved from your knowledge base — it quotes your documents rather than improvising. That means answer quality is mostly a function of what you feed it. Ten minutes of curation beats a hundred uploaded files.

The three sources that matter most

  1. A pricing document. Tiers, what's included, discount posture, contract terms. Pricing questions are the most common mid-call moment, and a precise answer ("Teams is £50 a seat, monthly, no platform fee") lands far better than a vague one.
  2. A security/compliance overview. SOC 2 status, data handling, hosting region, DPA availability. These questions stall deals when reps say "I'll check with the team" — and they're pure recall, perfect for a copilot.
  3. Your product's hard numbers. API limits, integrations list, implementation timelines, supported platforms. Anything a technical buyer asks that has an exact answer.

What to upload vs scrape vs connect

  • Upload (PDF, DOCX, TXT, Markdown): documents that don't live on your website — pricing sheets, internal FAQs, one-pagers, competitor positioning.
  • Scrape: your public website, help docs, and changelog. SalesGhost reads the pages so answers reflect what you've published. Re-run a scrape after big site updates.
  • Connect Slack / CRM: for the tribal knowledge — how your team actually answers things, and account context (via HubSpot or Salesforce) for who you're talking to.

Set your company context

In Settings, the company context field is where you tell SalesGhost your ICP, positioning, and tone in a few paragraphs. It's read on every call and keeps suggestions on-message — worth five minutes to write properly.

Signs your knowledge base needs work

  • Answers are generic. The retrieval found nothing specific, so the suggestion hedges. Add the missing document.
  • Answers are outdated. You changed pricing but not the uploaded sheet. The knowledge base is only as current as its sources — put a quarterly refresh in your calendar.
  • Two documents disagree. Delete the stale one; conflicting sources produce hedged answers.

What not to add

Long marketing decks, blog archives, and meeting notes mostly add noise. If a document doesn't contain answers you'd want spoken on a live call, leave it out. Quality of retrieval beats quantity of content — a lean, current knowledge base is the single highest-leverage setup investment in the product.