CRM Lifecycle Automation
CRM Proposal and Payment Follow-up
Conditional follow-up, reply handling, agreement status, and payment handoffs in GoHighLevel.
Sanitized evidence and reconstructed architecture
Workflow context
Proposal, agreement, and invoice follow-up need different stop conditions. A positive reply should pause proposal chase, while signed and paid events need their own state changes and handoffs.
My implementation role
Implementation of the CRM follow-up and event-handling workflows shown in the supplied builder captures, including pause conditions and invoice-paid handoff.
Architecture and connected systems
- Proposal chase entry
- Wait and check
- Reminder email
Verified system behavior
- Proposal reminder cadence with acceptance checks
- Positive-reply pause and internal notification
- Accepted-proposal task creation
- Agreement reminder and signed-event handling
- Invoice reminders with paid and terminal checks
- Invoice-paid removal from chase and onboarding handoff
- Separate abandoned-booking recovery workflow
Technologies
GoHighLevel, Webhooks, CRM Workflows
Evidence note
These are separate CRM workflows presented together by purpose. Only visible inter-workflow actions are shown as connections. Proposal acceptance creates a task in the supplied capture; automatic agreement delivery is not established. The May sales pipeline is separate related work.
