Use a record that survives the conversation
A list of email addresses loses the most important context: why you contacted the site. Save the specific article and section, proposed destination, relevant product fact, and any previous relationship.
We would rather maintain a small record that everyone understands than a large dashboard with inconsistent status labels.
Keep the stages separate
| Stage | What it means |
|---|---|
| Qualified | Someone checked the article and documented the fit |
| Drafted | A message exists but has not necessarily sent |
| Sent | The message was sent |
| Replied | A conversation exists; sentiment still matters |
| Confirmed | The article was checked and the update exists |
| Closed | No further action is appropriate |
These labels are an example workflow, not a list of statuses promised by every outreach tool.
Record what happens after publication
Keep the actual URL, check date, and surrounding text. If you use tagged referral links, use a consistent naming convention and consider whether the writer accepts them. Do not assume every visit or later purchase is fully attributable.
Track AI mentions separately with the question, platform, and observation date. A changed answer is a different observation from a confirmed article edit.
Review one practical bottleneck
If many prospects remain unqualified, improve the research brief. If drafts sit untouched, simplify review ownership. If replies wait for answers, assign responsibility before adding more sending capacity.
The purpose of the record is to make useful next actions obvious. A higher activity count means little if the team cannot tell which conversations need attention.