Which documents can it answer from?
When the buyer asks something technical, hit Answer. The answer comes from what you and your company have loaded.
PDF, Word, text and Markdown files: product docs, security pages, battle cards.
Up to 2,000 pages of your own help site can become searchable docs for answers.
Documents your company uploads once reach every rep's app.
It all runs in the desktop app beside Zoom, Teams, Google Meet or Webex, on Windows and Mac. No bot joins the meeting, and you confirm you have consent to record before every call.
What happens when your docs don't have the answer?
It tells you your docs don't cover it, instead of guessing. On a technical call, a confident wrong answer comes back to you in the security review.
- Each answer names the files it used, so you can see where a line came from.
- Numbers it can't find in a source are removed before the card shows.
- When your docs don't cover it, it says so instead of guessing.
- It never tells you to defer. No "let me loop in my SE" and a week of waiting.
What should you load first?
Start with the questions buyers ask on every technical call, and load the file that answers each one.
For what to ask a technical buyer once you've answered, see questions to ask a technical buyer.
