Project 04 / Demonstration build
A service business, fully built in GoHighLevel
A fictional HVAC company uses GoHighLevel to answer web inquiries within a minute, book jobs, send reminders, follow up until the lead replies, and hold back a review request when a customer complains.
Category: Home services · Designed outcomes, not measured client results.
Who this is for
HVAC, plumbing, electrical, cleaning, and solar businesses that need inquiries, appointments, and follow-up in one platform.
The problem
Example client brief
“I am on a roof when a lead comes in. By the time I get back to them they have booked someone else. I know I should ask for reviews but I forget, and the last thing I want is to ask an unhappy customer for one.”
- Web inquiry
- Text within a minute, email if it fails
- Booking, reminders, follow-up and review request
Designed outcome
A one-truck HVAC company that answers every inquiry within a minute and never chases a booking or a review by hand.
The demonstration business
The company is made up. Everything behind it is real and running: the website form, the booking calendar, the sending domain, and the follow-up. The example follows leads from a web inquiry through booking, the job, and the review request.
What the workflow does
- A homeowner fills out the form on the website. The system texts them within a minute, the lead lands in the pipeline, and the owner gets an email about it.
- If the text fails, the same message goes out by email instead. In this demo the number is not registered for business texting, so the email path is the one you see. Texts fail in real life too, so the fallback is part of the build.
- If the lead has not booked after an hour, they get a link to pick a time. A booking sends a confirmation, moves the lead to Booked, and puts the appointment on the owner's Google Calendar.
- Reminders go out the day before and two hours before the appointment.
- A lead who never books gets three follow-up messages over five days. Any reply stops the sequence for good.
- Two hours after a job is marked done, a review request goes out. If the customer has replied with a complaint before then, the request is cancelled and the owner gets an email instead.
- Mail sends from a dedicated sending domain with SPF, DKIM, and DMARC set up, so confirmations land in the inbox and not in spam.
Handover boundary
Workflows stay native to GoHighLevel. Business texting registration and the sending domain are set up for each business and are part of the scope. Neither guarantees that every message is delivered, which is why the email fallback exists.
Failure handling
When it breaks
The text to a new lead fails to deliver.
Within a minute the same message goes out by email. The lead is still in the pipeline and the owner still gets the new-lead email.
A lead in the follow-up sequence replies that they already found someone.
The sequence stops. Not paused, stopped. No more messages go out to that lead.
A customer complains before their review request goes out.
The review request is cancelled and the owner gets an email with the reply, so a person handles it.