About

Hi, I’m Hanzla.
I build GoHighLevel systems.

I’m a GoHighLevel and marketing automation specialist based in Mian Channu, Punjab, Pakistan. I work remotely with agencies and businesses, in English and Urdu.

Hanzla Amjad
Hanzla Amjad · Mian Channu, Pakistan

What I actually do

Most of my work sits between tools. A lead fills in a form, and then something has to happen: a contact gets created in the right GoHighLevel sub-account, a pipeline stage changes, a text goes out, a calendar gets booked, somebody on the team gets told. When those steps are connected properly, nobody has to think about them. When they aren’t, leads slip through and people end up copying data between tabs.

So I set up GHL accounts, build workflows, connect GoHighLevel to Make.com, Zapier, n8n and APIs, and put AI agents like Conversation AI and Retell AI in front of calendars. I also do a lot of A2P 10DLC registration work in the GHL Trust Center, which is less glamorous but decides whether your SMS gets delivered at all.

Where I’ve worked

I’ve worked with five teams on GoHighLevel and automation, each with a slightly different focus:

  • Wingman — tech support: account setup, snapshot creation and deployment, domain verification, Mailgun and Twilio.
  • Auto Nurture — GHL expert: websites, funnels, survey integration and system integration.
  • Top Lion Marketing — GHL tech support: client onboarding, snapshots, domains, Typeform and Google Sheets connections.
  • Auto Nurture Speedy.ai — GHL SaaS developer: SaaS setup, integration development and backend workflows.
  • Remote Clean Academy — onboarding specialist: Zapier, Booking Kola, QuickBooks, chat widgets and funnels.

Alongside client work I’m studying for a BS in Data Science at Emerson University. The two fit together well: a lot of automation is really about getting clean data from one place to another without losing anything on the way.

How I run a project

I don’t start building on day one. First I want to see the account, the tools and the real problem, because the request (“we need a workflow”) is often not the thing that’s broken. Then I map the logic, agree the scope with you in writing, build, and test it with realistic records before anything goes live. You get written updates as I go and a handover that explains how the system works.

You talk to me directly. There’s no account manager in between, and I’m on Pakistan time (UTC+5), so we agree overlap hours at the start.

Why this blog exists

Some questions come up on almost every project: why did A2P get rejected, what does a snapshot carry over, should this be in Make or inside a GHL workflow. The blog is where I write up the answers, using screenshots from the real projects.