Path B — CRM & Automation

Systems that keep leads, payments, and members moving without anyone chasing them by hand.

Built and maintained for a US-based membership & online education client — a full GoHighLevel automation stack covering lead engagement, checkout, membership billing, and a 90-day activation program. I run similar systems on an ongoing retainer for a second US-based client in professional services.

Role
Automation & CRM builder
Platform
GoHighLevel
Client type
US membership & education platform
Systems shown
4 core workflows
01 — Problem

Leads and payments falling through cracks

Multiple entry points — LinkedIn forms, SMS replies, email replies, tag triggers — with no single place deciding what should happen next for each lead or member.

02 — Build

Condition-based routing, end to end

Every workflow branches on a real condition — channel, payment status, plan type — then routes to the right CRM action: tag, opportunity, task, notification, or removal.

03 — Result

Zero manual triage

New leads, checkouts, billing failures, and membership tiers are handled automatically — billing and mentorship teams only see what actually needs a human.

Four systems, one account

The actual workflow builds.

These are live automations from the GoHighLevel workspace — not templates or diagrams made for this page.

1. Lead Source & Engagement Workflow

Routes every incoming lead by its actual channel — form submission, SMS reply, email reply, or contact tag — through a single condition block, updates the contact record, and checks the CRM for a matching opportunity before deciding what happens next.

TriggerContact Tag Added
TriggerEmail Reply
TriggerSMS Reply
TriggerForm Submitted
ConditionWhich channel?
Tag match
Form
Email
SMS
No match
Update Contact Field
Find Opportunity
Found
Not found

2. Membership Continuation Logic

Listens for payment success, payment failure, and subscription cancellation on the client's product. A failed payment gets flagged and routed to billing with an internal Slack alert; a cancellation gets tagged and cleanly removed from active workflows — no manual account review needed.

TriggerPayment Failed
TriggerSubscription Canceled
TriggerPayment Success
ConditionWhich outcome?
Success
Add Paid Member Tag
Remove from Reset Workflow
Failed
Add Tag
Slack Alert to Billing
Canceled
Add Tag
Remove from Workflow

3. Order Submitted: Checkout & Onboarding

Fires the moment a checkout completes, creates the contact and CRM opportunity, sends onboarding email and SMS, then branches by payment plan — monthly, 30-day free trial, or 7-day free trial — tagging and assigning each member to billing and mentorship correctly from the first minute.

TriggerOrder — Plan A
TriggerOrder — Plan B
TriggerOrder — Plan C
Create Contact
Onboarding Email
Onboarding SMS
Create / Update Opportunity
ConditionWhich plan?
Monthly
Assign Billing & Mentorship
30-day trial
Assign Billing & Mentorship
7-day trial
Assign Billing & Mentorship

4. 90-Day Activation Program

Handles three membership tiers — Full, 2-Pay, and 3-Pay — in parallel. Each tier creates or updates its own CRM opportunity, assigns billing and mentorship staff, fires an internal notification, and opens dedicated onboarding tasks for both teams.

TierFull Pay Member
Tier2-Pay Member
Tier3-Pay Member
Find / Create Opportunity
Assign Billing & Mentorship
Internal Notification
Add Tasks — Billing + Mentorship
Find / Create Opportunity
Assign Billing & Mentorship
Internal Notification
Add Tasks — Billing + Mentorship
Find / Create Opportunity
Assign Billing & Mentorship
Internal Notification
Add Tasks — Billing + Mentorship
Walkthroughs

Loom recordings of these builds.

Drop in your Loom share links here and they'll embed directly — recorded walkthroughs land better with clients than static screenshots alone.

Loom embed placeholder — paste share link for "Lead Nurturing & Email Workflow" walkthrough
Loom embed placeholder — paste share link for "Membership & Checkout" walkthrough

Got a CRM that's fighting you?

Tell me what's breaking down and I'll map out how I'd fix it before you commit to anything.

Email Isaac →