Forklift Lead Desk
A sales system for one forklift sales agent in the Philippines. Messenger inquiries, calls and a landing-page quote form all land in one GoHighLevel pipeline, and six workflows handle the follow-up that used to depend on his memory. I designed the landing page, set up the CRM and built the workflows.
- 63 inquiries and 12 quotes in the first 6 days
- 1–2 min to the first reply on Messenger and the quote form
- 3 ways in: Messenger, calls and the quote form
- 0 prices in the system; every quote is his
The problem
A buyer messages at 9 PM. Who answers?
A forklift sale starts with a short message and takes weeks: a demo or site inspection, a quote, a few follow-ups, then the turnover. Inquiries arrive on Facebook Messenger, by call or text, and through a quote form. The sales agent works Monday to Saturday, 8 AM to 5 PM, and talks to buyers in English, Tagalog and Taglish.
Without a system, the first reply waits until he is free, quotes go quiet after he sends them, and a buyer who already bought is never contacted again, even though a forklift needs servicing by the hours it works. The build covers the whole life of a deal, from first message to maintenance reminder.
The front door
A one-person sales page that feeds the pipeline
The system needed somewhere for web buyers to start, so I designed and built a landing page for the sales agent himself rather than the company. It opens on what a buyer needs to decide: a load picker (3, 5, 10 or 12+ tons), diesel or electric, and a call button. He asked for it to stay simple, because many of his buyers aren’t comfortable online.
The quote form checks every field before it sends: a required name, a Philippine mobile number, an optional email, forklift type, load, site, job details and an explicit consent box. A hidden field catches bots. On submit it sends one payload to the first workflow, and tells the buyer in plain words whether it was sent.
A working copy with the company, brand and contact details blurred. The form checks everything but sends nothing.
What I built
Six workflows, one job each
One branch of the quote follow-up, at a readable size. If the deal has left Quote sent, the nudges stop. All six workflows are in full behind the button below. Captured during testing, when the waits were set to minutes; live, they run in hours and days.
Show all six workflows in fullHide them
Alerts
Nothing goes quiet
Rejected is never silent
A submission that fails the checks emails an alert with what was missing. If the form ever renames a field, the first lost lead shows up as an email instead of vanishing.
Every path ends somewhere
A buyer with no email gets a call task. A reply creates a task. No branch ends without an action or a person being told.
Platform errors reach an admin
GoHighLevel’s workflow error emails are on for the whole account, with a Needs Review list of what broke.
GoHighLevel already emails workflow errors. A bad form entry isn’t an error to it, so I added an email for that.
Key decisions
Built around the platform’s limits
Only one message goes by Messenger
Meta allows automated replies within 24 hours of the buyer’s last message. Everything later goes by email, so each template was written for the channel it uses.
Every wait is documented
Each wait in the six workflows is listed with its real value, so the timing can be changed in one pass without opening every workflow.
Branches don’t rejoin
GoHighLevel branches end where they split, so shared steps are reached with a Go To instead of copies.
The quote form is custom, not GoHighLevel’s
The landing page uses its own form, which sends each request to GoHighLevel by webhook. That webhook is billed per submission, junk included: the trade-off for keeping the form built into the page.
Prices stay with the sales agent
No catalogue prices live in the system. Every quote is written by him; the workflows only chase it.
In GoHighLevel
The account, set up from scratch
Show fields, tags, workflows and a test runHide them
Outcome
Where it stands
All six workflows are live in the sales agent’s own GoHighLevel account, after end-to-end tests with test inquiries. In its first six days live it handled 63 inquiries and 12 quotes, and the first reply to Messenger and form inquiries went out within 1–2 minutes.
The landing page’s quote form feeds the pipeline, alongside Messenger, calls and texts.
Next: the loop that sets each following maintenance date and repeats.
The screenshots come from test runs. No real buyer data is shown.
Following up on quotations was definitely something that could get overlooked when I was busy. Having a reminder to follow up makes a difference because at least I have something prompting me to check back with them instead of just leaving the conversation hanging.
Next project
Studio Operations Suite
Hiring, or have a process to automate?