GoHighLevel · Automation · Remote, Philippines
I find the missing trigger,
then I write down why it was missing.
I build and repair GoHighLevel sub-accounts: lead intake, speed-to-lead, nurture, booking and handoff. Each build is tested with a real test lead against a written checklist and documented so the next person doesn't have to guess.
How I work
Audit before touching anything.
What I find is the scope. "Done" is written down before the build starts, and it doesn't move.
Audit
Workflows (published or draft), triggers, forms, pipelines, calendars, phone and A2P, sending domain, integrations. Each account labelled ready · small · medium · complex · blocked.
Scope
A written task, an hour cap and an acceptance checklist per account. Missing assets and client dependencies listed up front.
Build & test
Every path gets fired with a test contact. Pass means the execution log, the contact record and the phone all agree.
Document
What changed, why, and how to re-test it. The account is handed back cleaner than it came in.
Work
Two builds, one step apart.
Both use a first-time-homebuyer mortgage lead from Meta ads as the example. Both were built in a demo sub-account, and both are labelled as demos.
Speed-to-lead: first touch in under a minute
A Meta lead form lands in GHL, and the lead gets a text and an email while they're still on their phone. The loan officer is alerted and the pipeline card opens itself.
- 1 workflow, 9 steps
- Consent, DND and quiet-hours guards
- 8-point acceptance checklist
First-time buyer lead system, intake to handoff
Four connected workflows cover intake, a 14-day nurture that stops the moment someone replies, booking reminders with no-show recovery, and a clean handoff to the loan officer.
- 4 workflows, 8-stage pipeline, tag taxonomy
- Duplicate, STOP and mid-nurture booking handling
- 10-scenario test matrix
Field note · Real client account
A bug nobody assigned me.
Client work · 2026
"Verified" in GHL, unprotected in the inbox
While setting up a client's dedicated sending domain, GHL showed every record green. I checked DNS myself anyway.
GHL creates DMARC only on the sending subdomain. Receivers check DMARC at the organisational (root) domain, so every workflow email sent "From @clientdomain.com" had no DMARC policy at all.
Fix: added a root _dmarc record with relaxed DKIM alignment (adkim=r), because GHL signs on the subdomain and strict alignment would fail every message.
Test: I wrote a PowerShell checker that queries 1.1.1.1 directly (to skip stale local DNS cache) and prints pass/fail for root SPF, subdomain SPF, DKIM, both DMARC records and MX, then confirmed dmarc=pass in real message headers. It's now a step in my onboarding checklist for every new sub-account.
Why it matters for lead gen: a nurture sequence that lands in spam looks exactly like a lead who went cold.
Toolkit
What I bring to an account.
GoHighLevel
Workflows, triggers and filters, pipelines, custom fields and values, calendars, forms, sending domains, AI Studio sites, snapshots.
Around GHL
n8n (self-hosted), webhooks, Cloudflare DNS, email authentication, lead-list scraping and CSV import mapping.
LLM as a working tool
Claude daily for reading workflow exports and error logs, drafting SOPs and test plans, and scripting checks. I can show it live.
Contact
Ryan Tolentino
Independent contractor, Philippines.
- ryantolentino1982@gmail.com
- Hours
- 9pm–5am PHT · 9am–5pm US Eastern