What this checklist solves
Sales follow-up automation can create noise if it sends messages too aggressively. The safer first version watches stale deals, missing owners, and absent next tasks, then creates internal tasks or alerts with enough context for a human to act.
Automation map
| Layer | What to define |
|---|---|
| Trigger | No activity for N days, no reply after N days, unassigned demo request, proposal without task, or lead score change. |
| Records | Deal stage, last activity date, owner, deal value, last email status, next task date, and lead source. |
| Follow-up rules | Manager alert for no owner, CRM task for stale deals, high-priority alert for high-value stale deals, and skip rules for existing tasks. |
| Task payload | CRM record URL, contact or deal name, owner, stage, value, days since activity, existing task date, suggested angle, and priority. |
| Failure paths | Missing owner, missing email, duplicate tasks, stale CRM sync, and unclear pipeline stage. |
Best-fit use cases
Use it for CRM follow-up automation, stale deal alerts, missed reply reminders, sales pipeline leakage, demo request routing, and B2B sales operations workflows.
Join the early list
Get the first free workflow pack and product updates.