Portfolio project
Sales Pipeline & Lead Routing SystemSales Pipeline at Lead Routing System
The client brief
CoolAir Cebu is a 3-rep aircon installation and repair company covering North, Central and South Cebu. Leads come from the website and Facebook. Each territory has its own rep, urgent repairs need a same-day callback, and the owner wants to know when deals stall.
Ang brief ng client
Ang CoolAir Cebu ay aircon installation at repair company na may 3 rep, sakop ang North, Central at South Cebu. Galing sa website at Facebook ang leads. May sariling rep ang bawat territory, kailangan ng same-day callback ang urgent repairs, at gustong malaman ng owner kapag natetengga ang deals.
The business problemAng problema ng business
Leads are forwarded by hand, urgent repairs wait as long as quotes, and deals quietly die in the quote stage with nobody noticing. Mano-manong fino-forward ang leads, kasing-tagal ng quotes maghintay ang urgent repairs, at tahimik na namamatay ang deals sa quote stage nang walang nakakapansin.
Requirements
What the client needs. Tick them off as you build — saved in this browser.Ang kailangan ng client. I-tsek habang nagbu-build ka — naka-save sa browser na 'to.
Skills you'll useMga skill na gagamitin mo
Stuck on a part? Each of these lessons covers one piece.Na-stuck sa isang parte? Isang piraso ang sakop ng bawat lesson dito.
- Custom Fields: Structuring Client DataCustom Fields: Pag-aayos ng Data ng Client
- Designing a Pipeline That Matches a Real Sales ProcessPagdisenyo ng Pipeline na Tugma sa Totoong Sales Process
- Workflow TriggersMga Workflow Trigger
- Filters and If/Else BranchesFilters at If/Else Branches
- Wait Steps and Getting Timing RightWait Steps at Pagtama ng Timing
- Testing a Workflow Before It Goes LivePag-test ng Workflow Bago I-live
Build requirements
Testing checklist
This is what separates a portfolio project from a tutorial. Don't call it done until every line is ticked.Ito ang naghihiwalay sa portfolio project at sa tutorial. Huwag sabihing tapos na hangga't hindi naka-tsek ang bawat linya.
Expected resultInaasahang resulta
A routing and pipeline system that sends every lead to the right person, treats urgent jobs urgently, and surfaces stalled deals — with a test matrix proving it. Routing at pipeline system na nagpapadala ng bawat lead sa tamang tao, tinatratong urgent ang urgent na trabaho, at inilalabas ang natetenggang deals — may test matrix na nagpapatunay nito.
Reflection
Answer these before you look at the suggested solution.Sagutin muna ang mga ito bago tingnan ang suggested solution.
- What happens when a rep goes on leave? How would you handle cover?
- Which edge case surprised you during testing?
- If the owner added a fourth territory, how many places would you need to change?
- Ano ang mangyayari kapag nag-leave ang isang rep? Paano mo hahandle ang pagsalo?
- Aling edge case ang ikinagulat mo habang nagte-test?
- Kung magdagdag ang owner ng pang-apat na territory, ilang lugar ang kailangan mong baguhin?
Reveal the suggested solutionIpakita ang suggested solution
Awaiting hands-on verification. The concepts here are sound, but the click-by-click steps have not yet been re-walked in a live GoHighLevel sub-account. GoHighLevel changes often, so a menu name or screen may differ from what you see. Flagged rather than presented as verified.
Suggested architecture
Pipeline: “Installations & repairs” New inquiry → Contacted → Site visit booked → Quote sent → Following up
Workflow 1 — “Inquiry → route + urgency”
- Trigger: form submitted
- Create opportunity in New inquiry
- If/Else on Service area: North / Central / South → assign + notify that rep; default → notify owner to assign
- If/Else on Request type: Urgent repair → SMS/notification to on-call tech now; Quote → normal follow-up
Workflow 2 — “Stalled quote → escalate”
- Trigger: pipeline stage changed to Quote sent
- Wait 4 days
- If/Else: is the opportunity still in Quote sent and still open?
- Yes → notify the owner with the deal name, value and rep
The test matrix
| Urgent repair | Quote | |
|---|---|---|
| North | ✓ | ✓ |
| Central | ✓ | ✓ |
| South | ✓ | ✓ |
| No territory | ✓ | ✓ |
Eight cases, plus the two stalled-deal tests. Include this table in your portfolio write-up — it shows you test like a professional.
Writing it up for your portfolio
“Practice project: built territory-based lead routing in GoHighLevel for a fictional 3-rep aircon company — automatic assignment and notification by area, urgent-repair alerts, and escalation for quotes that stall. Tested with an 8-case matrix.”
Suggested na architecture
Pipeline: “Installations & repairs” New inquiry → Contacted → Site visit booked → Quote sent → Following up
Workflow 1 — “Inquiry → route + urgency”
- Trigger: form submitted
- Create opportunity sa New inquiry
- If/Else sa Service area: North / Central / South → i-assign + i-notify ang rep na ‘yon; default → i-notify ang owner para mag-assign
- If/Else sa Request type: Urgent repair → SMS/notification sa on-call tech ngayon na; Quote → normal na follow-up
Workflow 2 — “Stalled quote → escalate”
- Trigger: naging Quote sent ang pipeline stage
- Maghintay ng 4 na araw
- If/Else: nasa Quote sent pa ba ang opportunity at open pa?
- Oo → i-notify ang owner kasama ang pangalan ng deal, value at rep
Ang test matrix
| Urgent repair | Quote | |
|---|---|---|
| North | ✓ | ✓ |
| Central | ✓ | ✓ |
| South | ✓ | ✓ |
| Walang territory | ✓ | ✓ |
Walong case, plus ang dalawang stalled-deal test. Isama ang table na ‘to sa portfolio write-up mo — pinapakita nitong nagte-test ka na parang professional.
Pagsulat nito para sa portfolio mo
“Practice project: gumawa ng territory-based lead routing sa GoHighLevel para sa kathang-isip na aircon company na may 3 rep — automatic na assignment at notification ayon sa area, urgent-repair alerts, at escalation para sa quotes na natetengga. Tinest gamit ang 8-case matrix.”