The CRM is where the follow-up lives. These are the builds that decide who gets
messaged, who gets left alone, and who is worth interrupting you for. Each one below is a real build, drawn step by step
as it runs. Click any one to see it full size.
When someone fills in a form
3 workflows
01
Purchase Delivery
Someone buys. They stop being a lead, become a customer, the deal moves, and the confirmation goes out.
Worth noticing. The lead tag comes OFF before the customer tag goes on. Left on, a paying customer keeps receiving the emails written for people who have not bought.
7 steps
02
Form Submission-Create Quotation
A quote request comes in, the numbers are built in Make.com, and the quote is emailed back.
Worth noticing. GoHighLevel hands the pricing to Make.com and takes the answer back. One job per tool, so neither becomes the thing nobody dares change.
7 steps
03
Email Nurture Sequence
Six emails over days, in a fixed order, and then it stops.
Worth noticing. It ends on the objections email. A sequence with no end is spam with a schedule.
16 steps
When a call is booked
1 workflow
04
Booked Appointment + Reminders
A confirmed booking is tagged, taken out of the chase, and reminded four times before the call.
Worth noticing. Remove from Workflow is the step that matters. Without it the person who just booked keeps getting messages asking them to book.
15 steps
When someone comments
2 workflows
05
"REFER" FB Responder
Someone comments on a Facebook post. It answers in public, then opens a private message with a referral offer.
Worth noticing. It waits before replying. An instant answer to a comment reads as a machine, and the pause costs nothing.
11 steps
06
"Headshots" event IG Responder
An Instagram comment or DM about the headshots event gets answered on whichever channel it arrived on, and ends in an RSVP.
Worth noticing. A comment and a DM are the same question arriving two ways. The build splits on which one it was and answers each properly.
13 steps
The two AI conversation engines
9 workflows
07
2.6) Calendar Link Sent
When the AI conversation produces a booking link, the contact is tagged, the deal is created and you are told.
Worth noticing. Everything past 'Do They Qualify?' is worth your attention. The None branch ends silently, which is the right answer most of the time.
10 steps
08
2.7) DND After "Quit" Reply
The customer replies quit. Messaging stops, and they are pulled out of all five Defibrillator conversations.
Worth noticing. Three separate triggers watch for Quit, QUIT and quit, because a person who wants out will not check their capital letters first.
10 steps
09
1.7) DND After "Quit" Reply
The same exit, built again for the Speed To Lead side. Five conversations, all switched off.
Worth noticing. It exists twice on purpose, once per engine. A person left in one of five conversations is worse off than one who was never in any.
10 steps
10
Test Webhook - Defibrillator
Takes the AI's reply back from outside GoHighLevel and writes it onto the contact.
4 steps
11
Test Webhook - Speed2Lead
The same hand-off, on the Speed To Lead side.
4 steps
12
1.1) Speed To Lead AI Convo Starter
A brand new lead gets a text within moments, and the AI holds the first stage of the conversation.
About this drawing. Screenshotted at 20% zoom because of its size, so the node text is not legible in the source. Shown as the structure it is: a long branching conversation, every reply routed to its own follow-up.
5 steps
13
1.3) Speed To Lead Convo 3
The third stage of the same conversation, once the lead is still talking.
About this drawing. Screenshotted at 28% zoom, so the node text is not legible in the source. Same branching shape as the other stages.
5 steps
14
2.1) Defibrillator AI Convo Start
Re-opens a lead that went cold months ago, by text, and holds the first stage of that conversation.
About this drawing. Screenshotted at 20% zoom, so the node text is not legible in the source. Shown as the structure it is.
5 steps
15
2.5) Defibrillator AI Convo 5
The last stage before the calendar link is considered.
About this drawing. Screenshotted at 28% zoom, so the node text is not legible in the source.
5 steps
When to interrupt a human
1 workflow
16
WF 001: Email Marketing + Call
An email campaign where the people who engage get queued for a phone call instead of another email.
About this drawing. The largest of them, screenshotted at 20% zoom, so the node text is not legible in the source. Dozens of branches on what the contact did.
5 steps
Read off the builder itself. Client names are withheld throughout, and where a workflow was too large to screenshot legibly the drawing says so rather than inventing the steps.