DEV Community

aiFetchly
aiFetchly

Posted on

Build Your Own Local Knowledge Base So an AI Agent Can Write Client Emails That Sound Like You

#ai

Disclosure: I am from the aiFetchly team.

Most generic AI emails fail for a simple reason: the model does not know your business. It does not know how you describe a service, which cases you accept, what you never promise, or how you follow up. A local knowledge base fixes that — not by adding more prompts, but by giving the agent a small, curated source of truth to draw on.

1. Start with your own documents, not the whole internet

Collect the material you already trust: service pages, FAQs, proposal templates, past replies you were happy with, pricing notes, and objection-handling answers. Keep it in one place and prune ruthlessly. If a document is outdated, remove it or mark it superseded. A knowledge base with 30 accurate pages beats one with 300 stale ones.

A practical structure that works well:

  • What we do / do not do: one page per service, with scope and limits.
  • Voice and tone: 5–10 approved examples, plus phrases to avoid.
  • Proof points: case summaries, timelines, and common questions, written in your words.
  • Follow-up rules: when to wait, when to nudge, and when to stop.

2. Keep the knowledge base fresh

Set a monthly 20-minute review. Check three things: prices or offers that changed, services you no longer offer, and replies that needed correction. Update the source document, not just the last email. If your agent keeps quoting an old offer, the problem is almost always an un-updated source, not the model.

Version your notes simply: add a date at the top of each page, and retire pages instead of leaving competing versions side by side.

3. Use it as context, not as a script

When drafting outreach, let the agent retrieve only the relevant pages for that prospect — their industry, problem, and stage — and then write in your voice. Ask it to stay close to your approved wording for claims, and to leave anything uncertain as a bracketed question for you, rather than inventing a detail.

A useful checklist before you send:

  1. Does this email reference something specific about this prospect, not just their company name?
  2. Is every claim traceable to a document in the knowledge base?
  3. Would you be comfortable if the prospect replied and asked for detail?

4. Deduplicate before you send

Duplicate outreach is one of the fastest ways to look automated. Before a campaign goes out, deduplicate by domain and contact, merge contacts from the same company where appropriate, and filter out people you have already contacted recently or who already replied. Keep a simple activity log — who was contacted, when, and about what — so a second campaign does not restart a conversation from zero.

5. Keep a human in the loop

For important prospects, review the draft, edit one or two sentences to make it yours, and only then send. For larger lists, review a sample from each segment, fix recurring mistakes at the source document level, and resend only the corrected segment. Automation should save drafting time; it should not remove judgement.

A short workflow you can copy

  1. Gather and prune your own documents into a local knowledge base.
  2. Write one voice guide with approved examples.
  3. Draft with retrieved context, not from memory.
  4. Deduplicate, filter, and check recent activity.
  5. Human-review the important drafts, fix the source, then schedule sending via SMTP on a timed workflow.

This is the approach we built aiFetchly around: multi-engine lead research, organising publicly available contact details, using your own documents and knowledge base as context for personalised emails, and SMTP scheduled sending with deduplication, filtering, and activity management, plus cron-based timed workflows and plugins for business knowledge. A short demo of a local knowledge base / private memory in action is here: https://www.youtube.com/watch?v=FTGsQ27HsfA — and the official site is https://www.aifetchly.com .

On pricing, for transparency: a free Community version is available, Plus starts at $10/month, and AI Content Assistant is Plus Only. Start with the free Community version to test whether a small, well-kept knowledge base improves your replies before you pay for anything.

What is the one document in your business that, if an AI agent always had it to hand, would most improve your emails?

Top comments (0)