trigger-based-outbound
Use this when a fresh account change may create a credible reason to start or resume a conversation. Produce a ranked decision and a reviewable message task; do not treat a detected event as automatic permission to send.
Qualify the trigger
- Capture the event, source, observed date, account, and exact evidence. Prefer primary evidence over summaries.
- Verify freshness against the date the event occurred, not the date an aggregator surfaced it.
- Translate the event into a plausible operational implication. A job posting matters only when the role, seniority, volume, or language connects to the problem being solved.
- Compare the account with the ICP and exclusion rules. Record why the signal changes priority now.
- Check recent activity, open opportunities, suppression rules, customer status, and previous replies before deciding to engage.
Score the event using references/signal-rubric.md. A high event score cannot rescue poor fit or missing contact access.
Resolve the person
Start with the account, then identify the person whose responsibility is closest to the observed change. Confirm that the contact belongs to the account and that the role evidence is current. Prefer an existing relationship or known stakeholder over a newly found senior title.
If the signal exists only at domain level and no appropriate person is verified, return “acquire or research contact” rather than drafting a send. If several stakeholders are relevant, name a primary contact and a distinct reason for involving each additional contact. Do not send the same message to an entire buying group.