Why this matters
Your AI tools are only as good as what they know. If they’re working from outdated website copy, last year’s deck, or whatever’s in the LLM’s training data, the output drifts in the same direction — away from your real customers. Putting your inside-out data into GetWhys makes sure the validation layer is grounded in what your team has actually heard, not in stale assumptions.The pattern that shows up most often: “What feature gaps are causing us to lose deals?” The useful answer combines win/loss interviews your team has run, sales call transcripts your reps have logged, and what GetWhys has heard from buyers in your category who chose someone else. You couldn’t get that from any single source alone.
What you can upload
GetWhys is built for unstructured text. Common uploads:- Sales call transcripts
- Win/loss interviews
- Customer Success calls
- Customer or prospect research interviews
- Research reports
- Product documentation
- Past PMM and GTM docs you want to reference
Supported file formats
.pdf.txt.docx
Need to upload something else? Convert PowerPoint files to PDF, or save CSV/Excel files as
.txt before uploading.How to upload
Open Organization Data in the left navigation (this may be labeled with your organization’s name, e.g. “Acme Data”) and choose an upload method:Direct file upload
Drag and drop files or pick from your computer.
Google Drive import
Connect Google Drive and pick files from there.
Gong integration
Auto-import call transcripts as they’re recorded.
How it shows up in answers
When you ask Chat a question, GetWhys searches the buyer signal database and your uploaded data in parallel. Both sources appear as citations in the answer, so you can see which insight came from which.Mentions
Type@ in any Chat input to reference a specific document. GetWhys will pull its full content into the prompt as context. Useful when you want Chat to read, review, or build on a specific file rather than search across everything.