Can I point the AI SDR at a docs URL instead of pasting entries?
Whether you can point the AI SDR at a docs URL instead of pasting entries, plus the safest next step.
The Knowledge Base is a text field you paste into, not a crawler. There's no way to point it at a documentation URL and have it keep itself in sync. You have to copy in the content you want the AI to reference, and update it manually when your docs change.
Why people expect URL ingestion
Products like Intercom's Fin and Notion AI pull from a docs URL automatically. Acquisity's AI SDR doesn't — its KB is deliberately smaller and hand-curated, tuned for the kind of conversational context a sales rep needs rather than a full product manual.
Workaround that actually works
Treat your docs URL as the source and the KB as a curated subset.
- Identify the 5–15 most frequently asked questions in your prospect conversations.
- Find the answer to each in your docs.
- Paste a condensed, Q&A-formatted version of each answer into the KB — not the full doc, just the essential facts.
- When your docs change meaningfully, re-check the KB and update the affected entries.
The KB is not meant to hold your whole product manual — it's meant to hold the context the AI needs for the first 80% of conversations. Longer, deeper explanations should come from a human on a call.
What to include vs leave out
| Include in the KB | Leave in your docs only |
|---|---|
| Pricing ballpark | Full pricing calculator / custom quotes |
| Core feature list | Deep technical specs / API docs |
| Company basics (name, location, CEO) | Team bios |
| Standard timelines / delivery promises | Individual project case studies |
| Common objection responses | Long-form thought leadership |
Short entries beat long ones
KB entries are selected as context for each reply. A 10,000-word paste gets chopped and may miss the relevant part. Ten focused 50-word entries outperform one giant dump every time.