I Let an LLM Write Cold Emails but Never Decide Who Gets Them: Lessons From 678 Real Sends
说明与用途
使用LLM的自动化冷邮件系统被重新设计,使LLM仅生成文本,而所有关于收件人、发送和回复分类的决策由确定性、单元测试的函数处理。这降低了错误定位,防止了产品虚构,并限制了对同一公司的重复外联。
问题
Automated cold‑email pipelines can send messages to the wrong recipients, invent product details, or repeatedly contact the same company, causing reputational damage and wasted effort.
结果
The architecture reduced accidental mis‑targeting, prevented the LLM from inventing product details, and introduced robust reply classification, resulting in 678 real sends with controlled outreach and 129 second approaches held back.
工作流
- 1. Pull leads from Apollo.io with filtered industry names and closed‑set seniority/size values.
- 2. Enrich leads via Apollo person‑match, applying the acceptEnrichment guard to ensure correct email, domain, and surname match.
- 3. Generate email body with the LLM, constrained to approved template content and recipient website text.
- 4. Post‑process the LLM output: strip added sign‑offs, restore presentation links, and translate while preserving brand tokens.
- 5. Store a frozen copy of the final email to prevent silent template changes.
- 6. Schedule sending: one message per tick with ±50% jitter within a 07:00‑19:00 window.
- 7. Send via Microsoft Graph, then read replies and classify them using a deterministic rule set (bounce, auto‑reply, opt‑out, reply).
- 8. Update ownership and company stamps to prevent duplicate outreach.
- 9. Log results and human‑readable reasons for each classification.
证据
Connecting a contact database, an LLM and a company mail server is the easy part. A weekend gets you a pipeline that pulls a thousand leads, has GPT write to each one, and sends the result unattended.
The model writes prose and picks from lists. It never decides whether, when, or to whom a message is sent.
The identity guard: function acceptEnrichment(...) { … }
Result: 129 second approaches held back in nine weeks.
- 记录日期: 2026-10-10T11:56:03.275Z