Lapsed-proposal follow-up
Workflow design — not yet built
Prepare an owner task for an existing CRM contact with an evidenced lapsed proposal.
The workflow
- Buyer problem
- Old proposals lose attention, but renewed outreach may be inappropriate during an active deal or contact hold.
- Intended users
- Sales owners managing existing, permissioned CRM relationships.
- Inputs
- Fictional existing contacts, a documented proposal/lifecycle trigger, deal activity, owner, contact preferences, suppression, and last-contact context.
- Intended steps
- Validate the existing contact and trigger context.
- Check activity, ownership, permission, and contact cooldown.
- Prepare a specific task and suggested message from approved context.
- Leave acceptance, editing, or rejection to the sales owner.
- Intended output
- An intended owner-task preview with a supported follow-up reason, or a stop/review reason.
- Human review
- The sales owner reviews the timing and final wording. A draft or fixture approval does not authorize outreach.
- Limitations
- The distinct reactivation use case is still a buyer hypothesis. Live CRM reads, durable suppression, authenticated approval, task creation, and message delivery are pending.