Enrichment That Doesn't Poison the CRM

به چه درد می‌خورد

غنی‌سازی را آخر انجام بده نه اول. هر ردیف بی‌دامنه که پیش از غنی‌سازی حذف کنی هم اعتبار نگه می‌دارد و هم یک رکورد بد را از CRM دور می‌کند. این اسکیل ترتیب کار و قانون بازنویسی را می‌دهد: روی فیلدی که انسان پر کرده ننویس، منبع و تاریخ را مهر بزن، و اول ده ردیفی را بسنج که جوابشان را از قبل می‌دانی.

خود اسکیل کپی

Enrich last, not first. Every bad row you remove beforehand is credits you
keep and a bad record the CRM never sees.

Order of operations:
1. Collect the raw list with the source URL on every row.
2. Drop rows with no company domain and no profile URL. They cannot be
   enriched, only guessed at.
3. Check the remaining rows against the CRM by domain or email. Accounts you
   already have do not need re-enriching.
4. Only now spend anything on enrichment.

Rules for writing back:
- Put enriched values in their own columns and keep the raw scraped value
  beside them. When a record looks wrong you need to see which layer invented
  it.
- Never overwrite a field a human filled in. Write to an empty field, or to a
  parallel "suggested" field somebody reviews.
- Stamp every enriched row with its source and the date. A contact detail with
  no provenance is a rumour.
- Send anything the enrichment flagged as uncertain to a review list, not
  straight into the CRM.

Prove the error rate before you scale:
- Take ten rows whose answers you already know and enrich only those.
- Count how many come back wrong. That number is your error rate for the
  other nine hundred, and you will not get a better estimate later.
- Push those ten to the CRM and open one record by hand.

The failure this prevents: a thousand contacts with plausible, unverifiable
email addresses, a bounce rate that gets your sending domain flagged, and no
way to tell which records were machine-written.

نصبش چطور است کپی

1. Open the tool and start a new conversation, project or template.
2. Paste the text below wherever the tool keeps standing instructions
   — usually called system prompt, instructions, or persona.
3. Save it so it applies to every run rather than a single message.

برای تو جواب داد؟

از کجا آمده