Manaz Afzal Book a consultation

Work snippet

GoHighLevel lead routing into ServiceM8 jobs and Xero invoices

For a multi-crew business that markets in GoHighLevel and runs jobs in ServiceM8. A Make router assigns each new lead by service and area, a booked appointment opens one ServiceM8 job, the completed job raises the Xero invoice, and payment marks the opportunity won, so marketing, operations and finance count the same thing.

The problemLeads wait unassigned, jobs are retyped, and marketing, operations and finance count different numbers.

What changesLeads routed by rule, one job per booking, and paid status back on the opportunity.

Area
Lead to cash
Tools
GoHighLevel · ServiceM8 · Xero · Make · Slack
Typical scope
US$2,400-4,200
Timeline
About 5 weeks · fixed milestones

The situation and what was breaking

Marketing reported leads from GoHighLevel, the office reported jobs from ServiceM8 and the accountant reported invoices from Xero, and the three totals never agreed.

Leads arrived from ads, the website and missed-call text back. They sat in a shared GoHighLevel pipeline until someone picked them up, and the crew lead who took the call typed the job into ServiceM8 by hand. Invoices went to Xero through the native ServiceM8 sync, but nothing told GoHighLevel the job was done or paid.

Campaign reports showed booked appointments, not paid jobs, so spend went to campaigns that booked well and paid poorly.

  • Leads waiting hours for someone to claim them
  • Jobs typed twice, once in each system
  • Opportunities left open after the job was paid
  • Two crews contacting the same lead
  • Campaign reports with no paid revenue in them

What good looks likeEvery lead to the right crew within minutes, and a pipeline that ends at paid, not booked.

Discovery findings

What a read-only review checks first: two months of GoHighLevel opportunities, ServiceM8 jobs and Xero invoices, and the existing workflows.

What a read-only review checks firstWeek 1
IDFindingEvidenceRisk if left
F1No assignment rule; leads claimed by handMedian 2 h 40 min to first contactLeads go cold, or go to a competitor
F2Jobs re-typed from GoHighLevel into ServiceM8100% manual, 6% with typos in phone or addressWrong address on the day
F3No shared id across the three systemsOpportunities matched to jobs by nameRevenue by campaign impossible
F4Opportunities never moved past Booked71% of paid jobs still Booked in GHLPipeline overstates open work
F5Duplicate contacts from forms and calls9% of contactsDouble contact, annoyed customers
F6Out-of-zone leads assigned anyway14 in two monthsWasted travel, cancelled jobs

Architecture: GoHighLevel ServiceM8 integration

GoHighLevel stays the front door. Make routes leads by service and zone, creates the ServiceM8 job when an appointment is booked, and listens for the Xero payment to close the loop. One opportunity id travels the whole way.

Scroll sideways to see the full drawing

Lead to cash architectureGoHighLevel leads go to a Make router that assigns by service and zone; booked appointments create ServiceM8 jobs; completed jobs invoice in Xero; payments write back to the GoHighLevel opportunity; exceptions alert in Slack.020040060080new leadappointmentno rule matchedcreate jobnative syncpaidassign ownerA · FRONT DOORGoHighLevelForms, calls,opportunitiesB · ROUTERMake routingService + zoneto crew leadC · BOOKEDMake bookingAppointment toone jobD · OPERATIONSServiceM8Job with GHL id,completed statusE · FINANCEXeroInvoice, paymentF · CLOSED LOOPOpportunity WonPaid value writtenback to GHLG · ALERTSSlack #leadsUnassigned 15 min,out of zonethe opportunity id is written tothe job and the invoice referencerouting rules are a table,not buried in workflow stepsLEAD TO CASH · WEBHOOKSManaz Afzal
One opportunity id from first contact to paid invoiceSolid: live data path · Dashed: exception path

The screens your team will use

Crew leads work from the GoHighLevel pipeline and the ServiceM8 job card. The routing table is the one place the office changes when zones or crews change.

GoHighLevel · Opportunities · Service pipeline49 open
New lead
Blocked drain, Unit 4Ads · Zone North · Crew A
Hot water quoteWeb · Zone East · Crew C
Booked
Leak detectionTue 9:00 · Job 31207
Job done
Tap and mixer swapJob 31188 · INV-8820 sent
Won, paid
Drain camera and clear$680.00 paid 14 Oct

Won now means paid. The value on the card is the Xero invoice total.

Make · Routing table6 rules

Data store · routing_rules

ServiceZoneCrew leadHoursFallback
DrainsNorthCrew A07:00-17:00Office
DrainsSouthCrew B07:00-17:00Office
Hot waterAnyCrew C07:00-18:00Crew A
LeaksEastCrew C07:00-17:00Office
AnyOut of zoneNoneDecline template
After hoursAnyOn-call17:00-07:00Office next day

Edited by the office. The router reads it on every lead, so a change applies to the next lead.

ServiceM8 · Job 31207Live

Job card

SourceGoHighLevel opp 7f2c…
CrewCrew C
BookedTue 9:00
AddressChecked against GHL contact
Xero referenceGHL-7f2c / 31207
StatusScheduled

Lead to cash

  • Lead routed to Crew C
  • First contact, booked
  • Job created from appointment
  • Completed, invoice synced
  • Paid, opportunity Won

The job carries the opportunity id, so the payment can find its way back to GoHighLevel.

Make · Scenario · New lead routerLive
matchedout of zoneno matchGHLWebhookcontact created386DUPFind contactphone / emailTBLRouting tableservice + zone?Router3 routesOWNAssign ownerGHL opportunity361TXTDecline textout of zone14#Alertno rule11⏱Watchdog15 min check

A second scenario checks every 15 minutes for opportunities with no first contact and alerts the office.

How it is built

Routing first, because it is the part customers feel. Then booking, then the closed loop back from Xero.

Module-level build6 modules
  1. Module AShared id

    The GoHighLevel opportunity id is stored on the ServiceM8 job and in the Xero invoice reference.

  2. Module BDedupe on entry

    Contacts are matched by phone and email before an opportunity is created.

  3. Module CRouting table

    Service, zone, hours, crew lead and fallback in a Make data store the office can edit.

  4. Module DBooking to job

    A booked appointment creates one ServiceM8 job, checked against the id so a rebook updates, not duplicates.

  5. Module EPaid write-back

    A Xero payment on an invoice with a GHL reference moves the opportunity to Won with the paid value.

  6. Module FWatchdog and alerts

    Unassigned after 15 minutes, out of zone, or no matching rule posts to Slack with the lead link.

Field mapping and rules

Three systems, one id. The mapping is short because each system keeps the fields it is best at.

Field mapping
GoHighLevelServiceM8XeroRule
Opportunity idJob custom field: GHL idInvoice reference prefixRequired on every job
Contact name, phone, emailCompany and contactContact (via sync)GHL owns until the job exists
Service (custom field)Job categoryLine itemFixed list of 8 services
Zone (from postcode list)Job queueTracking: zoneRouting table
Appointment timeJob scheduled timeNoneRebook updates the job
StageStatusInvoice statusStatus map below
Status map
GoHighLevel stageServiceM8Xero
New leadNoneNone
BookedScheduledNone
Job doneCompletedInvoice sent
Won, paidCompletedPaid
LostCancelledVoided if raised

Worked figures

Walkthrough arithmetic for one month of leads through the rebuilt flow.

One month, lead to cashWalkthrough figures
Leads386all sources
Routed by rule36193.5%
Out of zone, declined14template text
Unassigned after 15 min0watchdog
Booked jobs142one job each
Paid and Won124value from Xero

Funnel, one month

Leads386
Contacted371
Booked142
Completed136
Invoiced131
Paid124

Minutes to first contact, by week

W1W2W3W4W5W6

QA and testing checklist

Every check runs in a copy or on test records first, and each one is ticked with evidence before go-live.

  • T1RoutingA test lead for each service and zone lands with the right crew lead.
  • T2Out of zoneAn out-of-zone postcode gets the decline text and no owner.
  • T3No ruleA service not in the table alerts within one minute.
  • T4WatchdogA lead with no contact after 15 minutes alerts the office.
  • T5DuplicateA form and a call from the same phone make one contact and one opportunity.
  • T6BookingA booked appointment creates one ServiceM8 job with the GHL id.
  • T7RebookMoving the appointment updates the job time, not a second job.
  • T8PaidA Xero payment moves the opportunity to Won with the paid value.
  • T9LostA cancelled job moves the opportunity to Lost.
  • T10After hoursA 22:00 lead goes to on-call and the office next day.

Scope

AreaIncluded
DiscoveryTwo months of opportunities, jobs and invoices matched, workflows reviewed, written findings
RoutingMake router and an editable routing table, with watchdog and alerts
BookingAppointment to one ServiceM8 job, rebooks update
Closed loopXero payment back to the GoHighLevel opportunity
DedupePhone and email match on entry; existing duplicates merged
ReportingFunnel from lead to paid, by campaign and crew
Not includedAd campaign management, GoHighLevel funnel or website design, SMS costs, or Make and GoHighLevel plan costs

Milestones, week by week

  1. Week 1

    Discovery and design

    • Two-month match
    • Routing table drafted
    • Status map signed
    20% of the fee
  2. Week 2

    Routing live

    • Router and dedupe on test leads
    • Watchdog and alerts
    • Live for new leads
    25% of the fee
  3. Week 3

    Booking to job

    • Appointment to ServiceM8
    • Rebook and cancel cases
    25% of the fee
  4. Week 4

    Closed loop

    • Xero payment to Won
    • Funnel report
    20% of the fee
  5. Week 5

    Handover

    • SOP and walkthrough
    • Routing table guide
    • 14 days of fixes
    10% of the fee

Handover and keeping it running

Handover pack

  • Routing table guide how to add a crew, a zone or a service
  • Status map what each stage means in all three systems
  • Alert runbook what to do with each Slack alert
  • Recorded walkthrough pipeline, router, job card and the paid write-back
  • Ownership list GoHighLevel, Make, ServiceM8 and Xero connections in the business's name
  • 14 days of fixes for defects in the agreed scope

Keep it running

Routing drifts when crews change and nobody edits the table. The no-rule alert is the early warning: if it fires more than twice a week, the table needs a row.

  • Daily: #leads alerts cleared
  • Weekly: minutes to first contact under 15
  • Monthly: funnel from lead to paid by campaign
  • When crews or zones change: edit the routing table first
  • Optional support hours at US$35 per hour, agreed in writing

Typical scope for this kind of project: US$2,400-4,200

About 5 weeks · fixed milestones. The systems health check (US$150, fixed) comes first and confirms the scope. Extra hourly work is US$35 per hour, agreed before it starts. After handover, a set block of hours each month is available at the same rate, agreed in writing.

Discuss an engagement.

Outline the operational problem through the contact form. I respond with a recommended starting point, including whether the US$150 systems health check is the appropriate first step.

Related work snippets

Next step

Bring me the work that repeats.

I scope it in writing, test it against your current process on your own data and hand over everything I build.

Book a consultation