Event lead-capture & nurture system, built end to end in GoHighLevel

The problem

Leads were being collected. Almost nothing was being done with them.

The business was collecting interest at live events but had nothing underneath it. Leads landed in an overcrowded CRM with thousands of inconsistent tags, no routing, and no follow-up. When I audited it, opportunities were just sitting at the entry stage with no owner and no nurture behind them.

The constraint was never lead volume. It was the missing layer underneath it. There was no reliable way to capture, gate consent, segment, route, and follow up at the speed an event demands, and it had to work for two different business models at once.

What I built

One architecture, two verticals, fully automated from scan to nurture

Each vertical runs in its own sub-account so the two never bleed into each other, but they share one architecture: QR-driven capture, consent logic, routing, pipelines, recommendation quizzes, lifecycle nurture, and reporting.

Capture & consent

A single workflow that captures, tags, routes, and gates consent

When someone submits the form, the workflow creates the opportunity, applies a precisely named event tag, sends a confirmation, then splits two ways. Discovery-call requests get flagged for a human to follow up, and an explicit consent check decides whether the lead enters email or gets suppressed.

Consent runs off a custom field instead of the platform's native element, because that native element isn't readable in action-level logic in this account. Leads who don't opt in are still captured and routed fully. They just get suppressed from marketing email through DND, which keeps the list clean.

Segmentation

Recommendation quizzes that route leads instead of just scoring them

Instead of letting people pick options that contradict each other, two quizzes work out the right path for them. The medical-tourism one is a recommendation engine, where interest plus experience preference resolve to a destination. I built it as chained conditional logic to get past the platform's per-node branch limit, with a catch-all so nobody falls through.

The retreat quiz scores people into one of four emotional themes. The platform wouldn't save the computed result to a field, so I routed off the strongest saved answer instead, matching on keywords rather than exact text. That sidesteps the punctuation mismatches that quietly break exact-match conditions.

Pipelines

Stage architecture mapped to two different customer journeys

The two business models need different funnels. The medical-tourism pipeline is a tight consult-to-booking journey. The retreat pipeline runs the whole lifecycle, from inquiry through discovery call, intake, payment milestones, pre-arrival, and post-retreat, because each stage kicks off a different operational touchpoint. There are no dead or parking stages. Every stage maps to something that actually happens.

Lifecycle nurture

Content matched to the relationship stage, not one template for everything

The nurture is a multi-email sequence that escalates its ask on purpose. It starts with a reply, then gives value, then a soft explore link, and only then asks for the booking. The early emails use a plain personal-note format, because for warm leads who just met the brand in person, something that reads like a real person wrote it beats a heavily designed template. Later, longer-term emails switch to branded design, since at that frequency pretending each one is personal would feel fake.

Measurement & data

Per-vertical dashboards and structured data on every lead

Each sub-account has its own dashboard tracking total leads, consent, discovery-call interest, and pipeline distribution. That turns the follow-up gap, which used to be invisible, into a number anyone can watch. Source attribution gets stamped at capture so it survives later tag edits.

Open pipeline reflects in-platform opportunity value, not closed revenue. Medical-tourism values shown are conservative platform defaults; real package values run considerably higher, so the medical pipeline is understated here.

Every lead lands as structured data: consistent tags, a stamped source, consent status, and quiz responses written to their own fields, all usable for routing, personalization, and segmentation.

The thinking

What made it hold up in production