#236 · "quick question" is killing your cold email

youtube ↗AI & Automation

What is the elegant way to build a proper knowledge base?

It depends on your purpose – you don’t need a knowledge base for everything, but it’s useful for letting an AI answer business‑specific questions that would otherwise require a database query. For example, I would feed all publicly available information about me, my company (Left Click Software), and our major case studies into the system. I’d host the chatbot on a platform like Botpress or NLU and connect it directly to Claude via API. The system prompt would contain a simple template with a few conversation routes to keep answers constrained. All the data would be embedded in a vector store such as Pinecone, and Claude would query Pinecone for the top five to ten matches before responding. This is standard RAG: each incoming message triggers the system prompt, a Pinecone similarity search, injection of the results into the prompt, and then the answer. The key is to be specific – you can’t feed everything – and to consider security, since exposing internal data through a public model can leak sensitive information.

knowledge baseragai

Related answers

youtube ↗AI & Automation

How would you build a totally autonomous reply bot for a cold email campaign that sends over 10,000 emails a day?

Here’s how I’d build a fully autonomous reply bot for a cold‑email campaign that sends 10 000+ messages a day. I’d start with a cheap inference platform such as N8N and create an AI agent inside it. The agent would have access to a knowledge base about the company and a library of proven reply templates collected from the past few months. When a new inbound email arrives, a workflow would trigger that (1) pulls the entire conversation history with that prospect, (2) checks the knowledge base to confirm the company context, and (3) scans the template library to find the closest match for the desired outcome (e.g., booking a meeting). The selected template would be populated with any dynamic details, and the AI would generate the final reply while staying as close to the template as possible to avoid sounding overly AI‑generated. The idea is to give the AI minimal freedom—just enough to fill in variables—so you retain control over tone and quality. I originally built this in N8N, but once you scale to 100 000 emails per day you can replace the visual builder with lightweight Python scripts running on a serverless platform like Modal, listening to webhook events from your email service.

reply botcold emailautomationn8n
youtube ↗AI & Automation

What should I learn first when building chat bots, and how should I position myself when selling them (e.g., as a chatbot expert or AI lead ops)?

When selling chatbots, emphasize the outcome they deliver rather than the fact that they chat in a human‑like way. Position yourself as selling speed‑to‑lead systems that, on average, double a client’s top of funnel or generate about $15,000 for businesses earning $50,000‑$100,000 in the digital‑agency space. This avoids the commodity race to the bottom where chatbots sell for $10/month. For learning chatbots today, it’s all about prompting. You don’t need RAG or retrieval‑augmented generation. Simply take a model like GPT‑4.1 Mini (million‑token context), load the client’s entire knowledge base—articles, PDFs, OCR‑converted text—into the prompt, compress if necessary by telling the AI to remove whitespace and superfluous words, and you can fit roughly thirty books of content in a single prompt.

chatbotpositioningprompting
youtube ↗Cold Email

How can I deeply research prospects and personalize cold emails when I find it hard to get information? How deep should research go, and can you give a quick guide?

Don't personalize the whole email—personalize only small snippets using enhanced variables. For example, use a template like 'Hey {first name}, love {thing we have in common}, fun to see you mention that on {platform} where I got it.' Then continue that vein to your offer. If AI writes the whole email, it will likely produce something stupid and obvious as AI‑generated. Keep the AI constrained everywhere and feed it only small variables (enhanced variables) with examples, letting it spin the initial info into a tightly woven, human‑sounding message. For research, use Claude to look up the person, compile company info, and grab all social media profiles; if you can't, use scrapers or similar tools.

cold emailpersonalizationresearch