From interest to decision
- New Lead
- Contacted
- Qualified
- Meeting / Discovery
- Proposal Sent
- Follow-up
Won / Lost native statuses
GOHIGHLEVEL / CRM & AUTOMATION
Demo GHL
GoHighLevel.
From lead to onboarding.
A connected sales process: an enquiry enters the CRM, a booking changes its stage, and a won sale starts onboarding. Built and tested in a separate sub-account with fictional data.
VIDEO WALKTHROUGH
See the implementation, step by step.
A walkthrough of the HighLevel process: from the form and pipeline to onboarding and execution checks.
4 min 43 sec · Romanian narration · Fictional data
- Connected pipelines
- 02
- Published workflows
- 07
- Native form + calendar
- 01 + 01
- Fictional test contacts
- 09
Sales pipeline / Intake and qualification
01 / ARCHITECTURE
One enquiry.
A clear path through delivery.
The modeled problem: scattered enquiries, unclear next steps and informal handover after a sale. I organised the process into two pipelines connected by specific events.
Won
New opportunity
+ onboarding task
From handover to review
- Client Onboarding
- Delivery In Progress
- Review Request
- Complete
Zero value. Sales history stays separate.
The sale stays Won.
Two pipelines separate sales progress from delivery. Onboarding gets its own opportunity without reopening the sale or counting its value twice.
Follow-up checks the state.
Before each note, If/Else checks replies, bookings and Won/Lost outcomes. Silence never automatically marks a contact Lost.
A person approves the handover.
Qualification, proposals, completed onboarding and delivery acceptance remain explicit decisions. Automation continues after the appropriate signal.
02 / IMPLEMENTATION
The components work together.
01
Form → contact → opportunity
The form captures service interest and business need. Lead Intake sets qualification to Pending, adds the demo tag, creates the opportunity and assigns a task. An in-app notification gives the owner a next step.
Project Inquiry
Lead Intake
02
Booking updates the sales context
The native calendar confirms a booking in the configured time zone. Meeting Booked updates the existing opportunity and adds the tag that stops follow-up at the next check.
Confirmed booking
Meeting / Discovery
03
Follow-up with exit conditions
Two one-minute waits make the scenario quick to demonstrate. After each wait, If/Else checks reply, booking, Won and Lost again. Only the branch without these signals receives an internal follow-up note.
No-Response Follow-Up
04
Won → onboarding → review preparation
A Won outcome creates separate delivery work. After the checklist, the operator applies the completion tag; the workflow finds the opportunity before updating it. Review preparation requires the correct stage and both eligibility conditions.
Client Delivery
03 / AUTOMATION LOGIC
Seven workflows.
Each with a clear job.
Open a workflow to inspect its trigger and implemented behavior.
01 · Lead Intake
Trigger Form Submitted, filtered to the demo form.
Execution Adds demo-data, sets qualification to Pending, creates a New Lead opportunity, assigns a task and sends an in-app notification.
02 · Meeting Booked
Trigger Appointment Status = Confirmed, on the demo calendar.
Execution Adds the booking tag and updates the existing sales opportunity to Meeting / Discovery. Adds preparation notes.
03 · No-Response Follow-Up
Trigger Contact Tag = demo-data.
Execution Wait 1 minute → check reply, booking, Won or Lost. Any of these states ends the branch. Otherwise, add an internal note. After another 1-minute wait, repeat the checks before adding a second note.
04 · Won to Onboarding
Trigger Opportunity Status Changed = Won, in Sales Pipeline.
Execution Adds demo-won, creates a separate Client Delivery / Client Onboarding opportunity and assigns an onboarding checklist.
05 · Onboarding Complete
Trigger Contact Tag = demo-onboarding-complete.
Execution If/Else checks demo-won. Find Opportunity looks up the delivery opportunity; only the Found branch updates it to Delivery In Progress.
06 · Review Request Preparation
Trigger Pipeline Stage Changed = Review Request, in Client Delivery, status Open.
Execution Wait 1 minute → require both demo-won and demo-onboarding-complete. Eligible contacts receive an internal review-preparation task; the ineligible branch ends.
07 · Lost Outcome
Trigger Opportunity Status Changed = Lost, in Sales Pipeline.
Execution Adds demo-lost. The follow-up workflow checks this tag at its next condition.
04 / VERIFICATION
Tested scenarios.
Verified results.
I checked what each scenario created or updated, including the branch that should stop. Validation performed on 24 September 2026.
Form → CRM
Nine fictional contacts submitted through the form; resulting fields, tags and opportunities checked.
Booking → same opportunity
A confirmed booking moved the existing opportunity to Meeting / Discovery.
Waits and follow-up exits
Internal notes were created after waits; the booked contact exited through the stop branch.
Won → delivery
Separate onboarding opportunities and assigned tasks were created.
Onboarding → Update
The workflow found the delivery opportunity and updated its stage after the completion tag.
Review: eligible and ineligible
Logs confirm task creation for the eligible contact and branch termination for the ineligible contact.
Testing review preparation
YOUR NEXT PROJECT
What would you like to build?
Tell me what you want to launch or improve. We’ll work out the right place to start.