Work snippet
HubSpot to ServiceM8: enquiry to booked job
Concept DesignIllustrative integration walkthrough. Business details, figures and records are worked examples.
Twenty electricians, three ways in for new work: the website form, email and phone. Every enquiry opens a single HubSpot deal, qualifying it books the matching ServiceM8 job, and the deal carries the job number and its scheduling status so sales can see what actually got booked.
The problemEnquiries are retyped from HubSpot into ServiceM8, and sales cannot see what was booked.
What changesOne deal books one job, and the deal shows whether it is scheduled.
- Area
- CRM to job-system pipeline
- Tools
- HubSpot · ServiceM8 · Zapier
- Typical scope
- US$2,200-3,800
- Timeline
- About 5 weeks · fixed milestones
The problem
The office retyped each enquiry from HubSpot into ServiceM8. Some never made it, deals went stale at stage one, and a returning customer often became a new contact.
- The same person appears twice in HubSpot and again in ServiceM8
- A booked job has no deal behind it, so sales cannot see the pipeline
- Follow-up emails go out unreviewed, or not at all
- Nobody can say which sources actually become booked jobs
What discovery would examine
A review of the HubSpot pipeline, ServiceM8 job creation, and two weeks of website, email and phone enquiries for a 20-tech electrical business.
| ID | Finding | Evidence | Risk if left |
|---|---|---|---|
| F1 | The same email produced two HubSpot contacts and two ServiceM8 clients in one month | Duplicate report on email match | Split history; a booked job the sales lead cannot see |
| F2 | Quoted jobs are typed into ServiceM8 by hand, after the deal is already "won" | Time stamps: job created 4-19 hours after the deal moved | Jobs are missed on busy days |
| F3 | Follow-up emails go from a personal mailbox, or not at all | No SLA field, no queue | Response time cannot be managed |
| F4 | A lost deal can still be pushed into ServiceM8 if someone reruns the current Zapier zap | Two lost deals had jobs | Work is booked after the customer has declined |
| F5 | Lead source is dropped when the job is created | ServiceM8 jobs have a blank campaign field | The pipeline cannot say which sources become booked jobs |
Approach
- Agree the stages and the owner of each field
What Qualified, Booked and Lost mean, and which system may change them.
- Match the contact first
Email and phone rules, with a short list of close matches for a person to confirm.
- Build the booking flow
A qualified deal creates one job, and the job writes status back.
- Add the SLA queue
A follow-up task is raised for a person, never sent on its own.
Current state and future state
Current state
Future state
Future-state modules
How it is built
- Module AContact match
Email, then mobile, then a short list of close matches for a person to confirm.
- Module BOne deal
A new enquiry on an existing contact opens a new deal, not a new contact, when the site is new.
- Module CBooking flow
A qualified deal creates one ServiceM8 job, with the site, the requested window and the HubSpot deal id.
- Module DSLA queue
If a new enquiry is untouched after 2 hours in business time, a follow-up task is raised for a person, never sent on its own.
- Module EWrite-back
Job number, scheduled window and job status are written back. A lost deal cannot create a job.
Field mapping
| HubSpot field | ServiceM8 field | Direction | Rule |
|---|---|---|---|
| Contact email, phone, name | Client email, phone, name | HubSpot to ServiceM8 | Match first; do not create a second client |
| Deal id | Job custom field: HubSpot deal | HubSpot to ServiceM8 | Required; used as the idempotency key |
| Site address and unit | Job site address | HubSpot to ServiceM8 | A new site on the same contact is allowed |
| Requested window | Job booking window | HubSpot to ServiceM8 | Copied, then ServiceM8 owns later changes |
| Lead source | Job campaign / source | HubSpot to ServiceM8 | Must not be dropped |
| Deal stage | (write-back only) | ServiceM8 to HubSpot | Booked, On site, Done; Lost is owned by HubSpot |
| Job number, scheduled time, status | Deal properties | ServiceM8 to HubSpot | Written back after each status change |
Worked exhibits
Exceptions and runbook
| Case | Rule | Who acts | First action |
|---|---|---|---|
| Close match on phone, email differs | Park in a match queue, do not auto-merge | Sales admin | Confirm or reject within one working day |
| Lost deal, booking event arrives late | Refuse to create a job; alert operations | Operations | Check the deal; only a person can reopen it |
| After-hours enquiry | SLA clock starts at 07:30 the next working morning | Flow | The morning queue lists anything still untouched |
| Write-back fails | Retry twice, then park with the job number | Operations | Enter the job number on the deal by hand, then replay |
| Second form submit, same email, same day, same site | Update the existing deal, do not open a second | Flow | Idempotency key: email + site + day |
How to read the exhibits
- The month of figures is about response and booking, not revenue.
- The two windows should carry the same deal id and the same scheduled window.
- The field map is what stops a second job being created from a lost deal.
Test plan
| ID | Check | Method | PASS when | FAIL when |
|---|---|---|---|---|
| T1 | Known email | Submit the form with an existing email | One contact, one new deal, one job after Qualified | A second contact is created |
| T2 | New email | Submit with a new email | New contact, new deal, job after Qualified | No deal, or a job before Qualified |
| T3 | Lost deal | Move to Lost, then replay the booking event | No ServiceM8 job | A job is created |
| T4 | SLA task | Leave a new deal untouched past two business hours | A follow-up task is raised, no email sent | An email goes out, or no task |
| T5 | Write-back | Schedule the job in ServiceM8 | Deal shows job number and window | The deal stage never moves |
| T6 | Idempotent booking | Fire the booking event twice | One ServiceM8 job | A second job |
| T7 | Source preserved | Create from each intake path | Lead source is present on the job | A blank source |
Scope
| Area | Included |
|---|---|
| Discovery | HubSpot pipeline, ServiceM8 job creation, and the current inbox-to-job path, with written findings |
| Rules | Stage meanings, contact matching, field ownership and the SLA clock, agreed in writing |
| Flows | Enquiry to deal, qualified deal to ServiceM8 job, and status write-back, with idempotent keys |
| SLA queue | A follow-up task for a person when the clock runs out |
| Report | Enquiries and booked jobs by source, plus untouched deals |
| Test plan | The PASS and FAIL checks in this write-up |
| Handover and support | SOPs, a recorded walkthrough, 14 days of fixes, and an optional monthly hour block |
| Not included | Paid advertising, call-centre staffing, or rewriting the website form copy |
Rollout, handover and monthly support
| Milestone | Deliverable | Timing | Share of fee |
|---|---|---|---|
| M1 Discovery and rules | Findings, stages, ownership and contact rules | Week 1 | 25% |
| M2 Booking flow | Deal to job and write-back, tested on scripted cases | Weeks 2 to 3 | 35% |
| M3 SLA and report | Follow-up queue and source report | Week 4 | 25% |
| M4 Handover | SOPs, walkthrough, 14 days of fixes | Week 5 | 15% |
Handover
- Written operating procedures for the happy path and each exception in the runbook
- A recorded walkthrough of the architecture, the queue and how to replay an item
- A credentials and ownership list, with every connection in your name
- Fourteen days of fixes after go-live, for defects in the agreed scope
Monthly support
A set block of hours each month, at US$35 per hour, agreed in writing before it starts. Typical use of the block: the match queue, SLA tasks, and any change to stage meanings or business hours
- Review of the exception queue and the weekly digest
- Small mapping or rule changes, agreed before they are made
- A short written note on what was done and what is still open
Typical scope for this kind of project: US$2,200-3,800
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, to watch the flows, handle changes and work the exception queue.
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.