Work snippet
GoHighLevel lead routing into ServiceM8 jobs and Xero invoices
Concept DesignIllustrative integration walkthrough. Business details, figures and records are worked examples.
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.
| ID | Finding | Evidence | Risk if left |
|---|---|---|---|
| F1 | No assignment rule; leads claimed by hand | Median 2 h 40 min to first contact | Leads go cold, or go to a competitor |
| F2 | Jobs re-typed from GoHighLevel into ServiceM8 | 100% manual, 6% with typos in phone or address | Wrong address on the day |
| F3 | No shared id across the three systems | Opportunities matched to jobs by name | Revenue by campaign impossible |
| F4 | Opportunities never moved past Booked | 71% of paid jobs still Booked in GHL | Pipeline overstates open work |
| F5 | Duplicate contacts from forms and calls | 9% of contacts | Double contact, annoyed customers |
| F6 | Out-of-zone leads assigned anyway | 14 in two months | Wasted 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
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.
Won now means paid. The value on the card is the Xero invoice total.
Data store · routing_rules
| Service | Zone | Crew lead | Hours | Fallback |
|---|---|---|---|---|
| Drains | North | Crew A | 07:00-17:00 | Office |
| Drains | South | Crew B | 07:00-17:00 | Office |
| Hot water | Any | Crew C | 07:00-18:00 | Crew A |
| Leaks | East | Crew C | 07:00-17:00 | Office |
| Any | Out of zone | None | Decline template | |
| After hours | Any | On-call | 17:00-07:00 | Office next day |
Edited by the office. The router reads it on every lead, so a change applies to the next lead.
Job card
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.
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 AShared id
The GoHighLevel opportunity id is stored on the ServiceM8 job and in the Xero invoice reference.
- Module BDedupe on entry
Contacts are matched by phone and email before an opportunity is created.
- Module CRouting table
Service, zone, hours, crew lead and fallback in a Make data store the office can edit.
- Module DBooking to job
A booked appointment creates one ServiceM8 job, checked against the id so a rebook updates, not duplicates.
- Module EPaid write-back
A Xero payment on an invoice with a GHL reference moves the opportunity to Won with the paid value.
- 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.
| GoHighLevel | ServiceM8 | Xero | Rule |
|---|---|---|---|
| Opportunity id | Job custom field: GHL id | Invoice reference prefix | Required on every job |
| Contact name, phone, email | Company and contact | Contact (via sync) | GHL owns until the job exists |
| Service (custom field) | Job category | Line item | Fixed list of 8 services |
| Zone (from postcode list) | Job queue | Tracking: zone | Routing table |
| Appointment time | Job scheduled time | None | Rebook updates the job |
| Stage | Status | Invoice status | Status map below |
| GoHighLevel stage | ServiceM8 | Xero |
|---|---|---|
| New lead | None | None |
| Booked | Scheduled | None |
| Job done | Completed | Invoice sent |
| Won, paid | Completed | Paid |
| Lost | Cancelled | Voided if raised |
Worked figures
Walkthrough arithmetic for one month of leads through the rebuilt flow.
Funnel, one month
Minutes to first contact, by week
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
| Area | Included |
|---|---|
| Discovery | Two months of opportunities, jobs and invoices matched, workflows reviewed, written findings |
| Routing | Make router and an editable routing table, with watchdog and alerts |
| Booking | Appointment to one ServiceM8 job, rebooks update |
| Closed loop | Xero payment back to the GoHighLevel opportunity |
| Dedupe | Phone and email match on entry; existing duplicates merged |
| Reporting | Funnel from lead to paid, by campaign and crew |
| Not included | Ad campaign management, GoHighLevel funnel or website design, SMS costs, or Make and GoHighLevel plan costs |
Milestones, week by week
- Week 1
Discovery and design
- Two-month match
- Routing table drafted
- Status map signed
- Week 2
Routing live
- Router and dedupe on test leads
- Watchdog and alerts
- Live for new leads
- Week 3
Booking to job
- Appointment to ServiceM8
- Rebook and cancel cases
- Week 4
Closed loop
- Xero payment to Won
- Funnel report
- Week 5
Handover
- SOP and walkthrough
- Routing table guide
- 14 days of fixes
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.