AI SDR Knowledge Base

The AI SDR Knowledge Base is the plain-text information the AI SDR uses when a prospect asks a question. Think of it as the briefing notes you would hand a helpful assistant before they answer your emails.

If the answer is in the notes, the AI SDR has a much better chance of replying well. If it is missing, unclear, or out of date, the AI may answer vaguely or move the thread to Needs Attention for you to review.

Where to Find It

1. Click Settings in the left sidebar.
2. Click AI SDR Agent.
3. Scroll to Knowledge Base.
4. Paste your information into the text box.
5. Click Save Settings.

The Knowledge Base is different from Resources. The Knowledge Base is the text the AI reads. Resources are approved links, like videos, PDFs, podcast pages, or case studies, that the AI can attach to follow-up emails.

Two Things to Know Before You Write It

These two facts explain why a good Knowledge Base looks the way it does.

• The AI uses it as facts, not as a rulebook. The AI reads your Knowledge Base for information: what your offer is, what your podcast is, whether it is free. Lines like "always do this" or "never do that" are read as soft context, not enforced commands. So write facts and short answers, not instructions.
• It is read by the reply step, not the whole system. When a prospect replies, the AI runs several steps (work out what they want, find a calendar slot, write the reply, plan follow-ups). The Knowledge Base is read by the steps that write the reply and answer questions. Scheduling, escalation, and opt-out detection do not read it, so you cannot change those by writing about them here.

Keep It Short

This is the most important editing rule. Your Knowledge Base is placed near the top of the AI's working notes, ahead of the live conversation and booking details. A long, rambling Knowledge Base makes those details harder for the AI to weigh, so shorter is usually more reliable.

If you are past the recommended maximum, trim repeated claims, pasted website copy, and anything prospects rarely ask about. A dense, well-organised Knowledge Base beats a long one.

Answer What Prospects Ask Before They Say Yes

This is the most important content rule. The questions that most often stall a reply are usually about proof, money, logistics, and trust. Make sure these are covered.

If You Have No Public Proof Yet

Many campaigns invite people to a podcast that has not published episodes yet. Do not leave the proof answer blank, because a blank answer makes the AI sound vague at the exact moment a prospect wants reassurance. Write a simple, honest line instead, for example:

What the Knowledge Base Can and Cannot Change

Knowing this saves a lot of frustration.

The Knowledge Base can influence (as facts the reply step uses):

• The facts the AI states: your offer, your podcast, pricing, proof points, who you help.
• Answers to common prospect questions.
• Your approved positioning and preferred phrasing.
• Campaign-specific facts, if you label them clearly (see below). This is best-effort, not guaranteed.

The Knowledge Base cannot change (these are built into the system):

• Whether the AI books the call itself or sends a booking link. The AI books into your connected calendar automatically. If no calendar is connected, it asks the prospect for their availability. It cannot be told to send a Calendly or booking link instead from the Knowledge Base. If you need that, contact your Acquisity team as a feature request.
• When a thread goes to a human. Escalation is handled by a step that does not read the Knowledge Base, so writing "flag this for review when..." has no effect. Use the Inbox → Needs Attention workflow for manual review, and contact your Acquisity team if you need custom escalation behaviour.
• Opt-out detection, intent routing, and which time slots are offered. All handled by steps that do not read the Knowledge Base.

Running More Than One Campaign

There is one Knowledge Base per workspace, shared across all of that workspace's campaigns. This is the most common cause of the AI mixing up two campaigns.

• Most reliable: one workspace per offer. If two offers, niches, or clients are genuinely separate, give each its own workspace. One workspace, one Knowledge Base, one clean story.
• If you must share a workspace: label each campaign's facts clearly. The reply step can usually use the campaign name to pick the right facts, but treat this as best-effort, not guaranteed.

## Campaign: [Exact campaign name in Acquisity]
Show / offer: ...
Proof: ...

## Campaign: [Exact campaign name in Acquisity]
Show / offer: ...
Proof: ...

Use the exact campaign name as it appears in Acquisity. Even so, separate workspaces remain the reliable option for genuinely separate offers.

Resources Are Separate From the Knowledge Base

Resources are approved links the AI can attach to follow-ups, set up in Settings → AI SDR Agent → Resources, not in the Knowledge Base text. Use the follow-up number to control sequencing, for example proof on follow-up 1 and a useful gift on follow-up 2.

Copy-and-Paste Template

Copy this into Settings → AI SDR Agent → Knowledge Base, then replace each bracket with one or two plain lines. Delete any section you do not need, and remove every bracket before saving. Keep the whole thing tight.

# Knowledge Base: [Company]

## Identity
Company: [name] | Website: [url] | Based in: [city/country]
What we do: [one plain sentence]
Who we help: [your best-fit customer]
Who sends the emails: [name, role]
Who runs or attends the call: [name, role, LinkedIn]  (may or may not be the sender)

## This campaign
Campaign: [exact campaign name in Acquisity]
Method: [podcast / interview / audit / offer]
Who we contact and why they are relevant: [one line]

## The offer
What the prospect gets: [one or two lines]

## Proof   (most-asked question, so do not leave blank)
Past episodes / examples: [links]   OR   "Recording our first season, episodes not public yet."
Audience / reach: [numbers, or an honest reach plan]
Notable guests / clients: [2-3 names, if any]
How to verify us: [LinkedIn / website]

## Money (answer both sides)
Is it free / what is the catch: [plain answer]
Do you pay guests / is there a cost to me: [plain answer]

## Logistics
Intro call: [purpose] | [length] | who attends: [name/role] | on: [Zoom/Meet/etc.]
Recording, if any: [length] | [format] | prep: [questions in advance? yes/no] | edit/approval: [policy]
After they say yes: [what happens next, e.g. you send a calendar invite]
(Do not add booking-link instructions here. The AI books your connected calendar, or asks for times if no calendar is connected.)

## Top questions (only the ones you really get; 1-3 sentences each)
Q: What is this about?       A: [answer]
Q: Why did you contact me?   A: [answer]
Q: Is this a sales pitch?    A: [answer]
Q: [add others you actually get]  A: [answer]

## Objections
Not a fit: [honest, no pressure]
Busy / bad timing: [short, flexible]
Already have a provider: [the real difference, if you have an approved answer]

## Approved answers
The facts above are the only approved details (links, prices, names, results).
If a prospect asks about something not listed, the approved answer is:
"Happy to confirm that on the call."  (or your own approved fallback)

Let an AI Write It for You

If you would rather not start from a blank page, paste the prompt below into Claude or ChatGPT. It asks you a short set of questions and then writes your Knowledge Base in the format above.

You are helping me write a "Knowledge Base" for an AI SDR (an AI that replies to
cold-email prospects and books calls on my behalf). I will paste the result into the
tool's Knowledge Base box. Follow these rules exactly.

HOW THE KNOWLEDGE BASE IS USED:
- It is read as FACTS the AI can use when answering a prospect, not as commands. Do not
  write rules like "always" or "never"; write facts and short answers.
- It must be short. Aim for 250-600 words (about 1,500-3,500 characters); do not exceed
  about 6,000 characters.
- It cannot control whether the AI books the call itself vs sends a booking link, when a
  human steps in, or which time slots are offered. Do not write instructions about those.

WHAT TO PRIORITISE (what prospects ask before saying yes):
1. PROOF: past episodes/examples/results, audience size, notable guests or clients, and an
   easy way to verify me. If I have no public proof yet, write an honest pre-launch line.
2. MONEY: is it free for them, and do I pay them or charge them. Answer both sides.
3. IDENTITY: company and podcast/show name, location, who sends the email, and who runs the call.
4. LOGISTICS: intro-call purpose, length, who attends, platform, and what happens next.
5. TRUST: a calm answer to "is this genuine / how did you get my details," with a way to verify me.

HOW TO RUN THIS:
- Ask me ONE compact round of questions covering the items above. Plain language.
- Then ask AT MOST ONE follow-up round, only for proof, money, logistics, and separating
  multiple campaigns. Never exceed two rounds of questions.
- If I run more than one campaign from this workspace, ask for each campaign and label them.

THEN WRITE THE KNOWLEDGE BASE:
- Use clear ## section headers and short lines. Put Identity, This campaign, Offer, Proof,
  and Money near the top.
- Facts and short answers only (1-3 sentences). No long sales copy. No fluff like
  "world-class" or "cutting-edge."
- Use what I gave you. Do not invent details. If an optional field is still unknown after
  two rounds, leave it out. Do NOT leave any [brackets] or TODOs inside the Knowledge Base.
- Keep the total under about 3,500 characters. If it gets long, cut, do not pad.
- AFTER the Knowledge Base, add a clearly separated block titled
  "NOTES: do not paste into the tool" with the character count and anything I should verify.

Start by asking me your first round of questions.

Quick Quality Check

Before you save, check:

• Is it within the recommended size (about 1,500 to 3,500 characters)?
• Are there any unfinished [brackets] or TODOs left in? Remove every one. Half-finished placeholders confuse the AI.
• Is the proof answer filled in (real links or the pre-launch line)?
• Is the money question answered on both sides (free for them, and do you pay or charge)?
• Are the company or show name and location stated in plain single lines?
• If you switched niche or offer, did you delete the old details?

When to Update It

Update the Knowledge Base whenever you change niche, offer, campaign method, pricing, show name, or host.

For the first week of any new campaign, check Inbox → Needs Attention every day. If the same prospect question shows up twice, add the answer to the Knowledge Base. After launch week, review it about once a month. This is the simplest way to make the AI SDR steadily better at answering your prospects.

Related

• Settings
• Follow-Up Resources