Home / Case studies / GoHighLevel and AI build

Case study · GoHighLevel, AI and reporting

Turning a Sydney outbound agency's GoHighLevel CRM into a self-running sales system

The client books qualified meetings for Australian B2B companies through cold calling, email and LinkedIn. I rebuilt their GoHighLevel account from an empty sub-account into the master setup their SDR team now runs on every day, then added Claude-powered research, call summaries and automated client reporting.

19Production workflows
4Sector pipelines
3Claude AI features
4Personalised landing pages
Client
Outbound sales (SDR) agency, Sydney
Role
GHL architect and automation build
Timeline
November 2026
Built by
Jayson V. Entrina
01 · The brief

What the agency needed

The agency was moving its whole outbound operation into GoHighLevel. Its own sub-account had to become the master template that every future client sub-account is copied from. Their scope set out the problems clearly.

Where they were

  • A director built the client report by hand every week
  • Call outcomes did not move anything in the pipeline
  • Meetings were brokered by a director, not booked on the call
  • No way to capture or qualify inbound enquiries
  • No protected sending domain for email at volume
  • Bad list data reached the phones before anyone checked it

What success looked like

  • An SDR calls, records the outcome and books without leaving the record
  • Outcomes drive the pipeline automatically
  • The client report builds itself from live data
  • Email and SMS go out at campaign volume without landing in spam
  • A new client is a snapshot, not a rebuild
  • The agency can maintain it all without a specialist
02 · Approach

How I ran the GoHighLevel build

Native first

Everything GoHighLevel can do on its own runs in GHL workflows. External tools (Make and Claude) are used only where GHL has no native option, and each one is documented with its running cost.

Safe by default

Every workflow was built in Draft, tested on test contacts across every branch, then switched on in order. Nothing that messages prospects went live before the copy was approved.

Built for the snapshot

Sector tags, custom fields and ownership roles are generic, so the same build drops into each new client's sub-account with only that client's own settings changed.

Plain-English handover

Each part was written up for the directors in simple language, with the decisions that were theirs to make laid out clearly.

03 · What I built

The core sales engine

Picking a call outcome now does the admin. One click from the SDR sets off the whole chain.

SDR picks outcomeDisposition box after every call in the GHL dialer
Lead statusContact status updated to match
Pipeline stageMoved in the right sector pipeline, created if missing, never moved backwards
Next actionCall-back task, nurture date, or taken off outreach

CRM structure

Four sector pipelines, one per target industry plus the agency's own, each with written stage definitions. One disposition set mapped to stages. Five separate ownership roles (Lead Owner, Assigned SDR, Booked By, Assigned Meeting Owner, Opportunity Owner) filled in automatically. Saved smart lists for the SDR's day, and a before-and-after click count on the five most common actions.

Opt-outs and suppression

One suppression path for every way a prospect says no: a team member turning on Do Not Disturb, a Do Not Call outcome, or a reply asking to be removed. Replies are sorted by phrase (out of office, unsubscribe, wrong person, not interested, not now), and existing clients are protected from being blocked by mistake.

Booking flow

A five-minute correction hold before anything is sent, so a wrong time or owner can be fixed. Then the lead moves to Strategy Call Booked, leaves outreach, and the prospect gets a confirmation by email and SMS in their own time zone. The meeting owner gets a full brief with the SDR's call notes. Cancellations during the hold send nothing. After the meeting, the owner is prompted to mark Showed or No-show and log the next step.

Lead ownership and quiet leads

Ownership fields fill in whenever a lead is assigned. The original Lead Owner is never overwritten. Any open lead that sits still for seven days is flagged with a task and an email to its owner.

List quality

Every new contact is checked on arrival for a missing phone, email or company, a non-Australian number, no campaign list, or an existing client. Anything flagged lands in a "Fix Before Calling" list.

Follow-up sequences

New enquiry, post-meeting, no-show recovery and quiet-contact reactivation sequences. They send in Sydney business hours, stop on any reply, and have a per-contact hold so an SDR can pause one record.

04 · AI layer

Claude AI inside the GoHighLevel workflow

Three AI features run through Make and the Claude API. Each writes into GHL fields the team already uses, and none of them sends anything to a prospect on its own.

Company researchClaude Haiku, Sonnet fallback

Before an SDR calls, Claude researches the company from its website and the web and fills structured fields: what they do, sector fit, location, size, recent activity, likely decision makers and a suggested call opener. A confidence check sends uncertain matches (look-alike company names, email domains that don't match) to the stronger model, so the cheaper model handles the easy majority.

Match confidence rulesSources listedNever guesses

First-email drafts

The same research call writes a short, specific first email for the SDR to review and send. It opens with a real fact about the prospect's business and is tied to the research fields, so it can't contradict the call notes on a date or number.

Call summaries

GHL transcribes recorded calls. Any call over 45 seconds goes to Claude, which writes the outcome, a two to three line summary, objections, buying signals and the next step onto the contact. Short voicemails are filtered out first so they cost nothing. These objections feed the weekly client report.

Tested on a sample call, Claude picked up both objections and the agreed callback date, without adding anything that wasn't said.

05 · Reporting

A GoHighLevel client report that builds itself

GHL eventsEvery call outcome, meeting and pipeline change
Reporting workflowsThree GHL workflows write one row per event
Google SheetOwned by the client, one per sub-account
Looker StudioClient dashboard and internal SDR page

I chose GHL's native Google Sheets action over an API feed. It costs nothing extra to run, has no middleware to break when GHL's API changes, and copies cleanly into each new client's snapshot. The client page shows meetings booked and held, show rate, calls, conversations, deals won, accounts that moved, the week's meetings, calls by outcome and meetings by campaign, filtered to the weekly, fortnightly or monthly review.

06 · Inbound, deliverability and website

Everything around the CRM

Personalised landing pages

Four industry landing pages hosted on a subdomain inside GHL funnels. Each link carries the prospect's company name, which the page fills into the header and footer, alongside client case study videos and a booking link to the directors.

Email deliverability

A dedicated sending subdomain so the main business domain is never at risk, with SPF, DKIM and DMARC verified. Each SDR sends from their own address on that domain. I traced an "Unverified sender" warning in Outlook to a mistyped default sender address and fixed it at the source.

Website

Took over the company site from the previous developer (GitHub and Vercel), then shipped the directors' changes: updated wording across 19 pages, a rebuilt case studies page leading with each client's results, testimonial videos with a privacy-friendly player that only loads YouTube on click, a portrait founders video in a full-size pop-up, and founder photos.

Account hygiene

Reassigned 800+ contacts to the right SDR in one run without flooding their inboxes. Renamed and grouped workflows so the client's own builds stay separate from mine. Fixed a booking email error and a missed owner notification found in testing.

07 · Stack

Tools used

ToolUsed for
GoHighLevelCRM, pipelines, dialer, calendars, workflows, funnels, email and SMS
Claude APICompany research, first-email drafts, call summaries
MakeConnecting GHL to Claude, with error handling that tags any failed run
Google Sheets and Looker StudioClient reporting and the internal SDR dashboard
GitHub and VercelCompany website code and hosting
HTML, CSS and JavaScriptLanding pages, personalisation script, video player

Where it stands

The calling, booking, opt-out and AI features are live and in daily use by the agency's SDR team. Reporting is running on live data with the client page built, and the follow-up sequences are ready for the directors' sign-off.

Contact

Want a GoHighLevel build like this for your agency?

Onboarding, automation, AI integration, reporting or a full system rebuild. Tell me what you need.

← Back to portfolio