Manaz Afzal Book a consultation

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.

Findings from the review
IDFindingEvidenceRisk if left
F1The same email produced two HubSpot contacts and two ServiceM8 clients in one monthDuplicate report on email matchSplit history; a booked job the sales lead cannot see
F2Quoted jobs are typed into ServiceM8 by hand, after the deal is already "won"Time stamps: job created 4-19 hours after the deal movedJobs are missed on busy days
F3Follow-up emails go from a personal mailbox, or not at allNo SLA field, no queueResponse time cannot be managed
F4A lost deal can still be pushed into ServiceM8 if someone reruns the current Zapier zapTwo lost deals had jobsWork is booked after the customer has declined
F5Lead source is dropped when the job is createdServiceM8 jobs have a blank campaign fieldThe pipeline cannot say which sources become booked jobs

Approach

  1. Agree the stages and the owner of each field

    What Qualified, Booked and Lost mean, and which system may change them.

  2. Match the contact first

    Email and phone rules, with a short list of close matches for a person to confirm.

  3. Build the booking flow

    A qualified deal creates one job, and the job writes status back.

  4. Add the SLA queue

    A follow-up task is raised for a person, never sent on its own.

Current state and future state

Enquiry path, current and future

Current state

EnquiryForm, email, phone
Inbox and HubSpotSometimes both
DealOften a second contact
ServiceM8 jobTyped by hand

Future state

EnquiryOne intake path
Match contactThen one deal
Qualify + SLAClock starts
ServiceM8 jobCreated, then write-back

Future-state modules

IntakeForm, email, phoneHubSpotContact and dealSLA queueTask for a personServiceM8One jobWrite-backJob no. and stage

How it is built

Module-level build
  1. Module AContact match

    Email, then mobile, then a short list of close matches for a person to confirm.

  2. Module BOne deal

    A new enquiry on an existing contact opens a new deal, not a new contact, when the site is new.

  3. Module CBooking flow

    A qualified deal creates one ServiceM8 job, with the site, the requested window and the HubSpot deal id.

  4. 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.

  5. Module EWrite-back

    Job number, scheduled window and job status are written back. A lost deal cannot create a job.

Field mapping

Field map, HubSpot deal to ServiceM8 job
HubSpot fieldServiceM8 fieldDirectionRule
Contact email, phone, nameClient email, phone, nameHubSpot to ServiceM8Match first; do not create a second client
Deal idJob custom field: HubSpot dealHubSpot to ServiceM8Required; used as the idempotency key
Site address and unitJob site addressHubSpot to ServiceM8A new site on the same contact is allowed
Requested windowJob booking windowHubSpot to ServiceM8Copied, then ServiceM8 owns later changes
Lead sourceJob campaign / sourceHubSpot to ServiceM8Must not be dropped
Deal stage(write-back only)ServiceM8 to HubSpotBooked, On site, Done; Lost is owned by HubSpot
Job number, scheduled time, statusDeal propertiesServiceM8 to HubSpotWritten back after each status change

Worked exhibits

SLA and booking, one month of walkthrough figures
Enquiries214website, email, phone logged
Booked jobs12759.3% of enquiries
Touched inside 2 hours20193.9%
Follow-ups waiting on a person8none sent unapproved
Duplicate deals0after matching rules
Website form58% bookedReferral74% bookedPaid search41% bookedRepeat customer81% booked
What both systems show for one enquiry
HubSpot · deal D-3381
ContactMatched on email to an existing record
SourceWebsite form
StageBooked
SLATouched in 27 minutes
ServiceM8 jobJOB-18442
ScheduledTue 08:00-10:00
ServiceM8 · job 18442
SiteUnit 3, one street address
DescriptionFrom HubSpot deal D-3381
StatusScheduled
WindowTue 08:00-10:00
HubSpot idD-3381
Created byThe booking flow, not keyed twice

Exceptions and runbook

Exception runbook
CaseRuleWho actsFirst action
Close match on phone, email differsPark in a match queue, do not auto-mergeSales adminConfirm or reject within one working day
Lost deal, booking event arrives lateRefuse to create a job; alert operationsOperationsCheck the deal; only a person can reopen it
After-hours enquirySLA clock starts at 07:30 the next working morningFlowThe morning queue lists anything still untouched
Write-back failsRetry twice, then park with the job numberOperationsEnter the job number on the deal by hand, then replay
Second form submit, same email, same day, same siteUpdate the existing deal, do not open a secondFlowIdempotency key: email + site + day

How to read the exhibits

  1. The month of figures is about response and booking, not revenue.
  2. The two windows should carry the same deal id and the same scheduled window.
  3. The field map is what stops a second job being created from a lost deal.

Test plan

PASS / FAIL checks
IDCheckMethodPASS whenFAIL when
T1Known emailSubmit the form with an existing emailOne contact, one new deal, one job after QualifiedA second contact is created
T2New emailSubmit with a new emailNew contact, new deal, job after QualifiedNo deal, or a job before Qualified
T3Lost dealMove to Lost, then replay the booking eventNo ServiceM8 jobA job is created
T4SLA taskLeave a new deal untouched past two business hoursA follow-up task is raised, no email sentAn email goes out, or no task
T5Write-backSchedule the job in ServiceM8Deal shows job number and windowThe deal stage never moves
T6Idempotent bookingFire the booking event twiceOne ServiceM8 jobA second job
T7Source preservedCreate from each intake pathLead source is present on the jobA blank source

Scope

AreaIncluded
DiscoveryHubSpot pipeline, ServiceM8 job creation, and the current inbox-to-job path, with written findings
RulesStage meanings, contact matching, field ownership and the SLA clock, agreed in writing
FlowsEnquiry to deal, qualified deal to ServiceM8 job, and status write-back, with idempotent keys
SLA queueA follow-up task for a person when the clock runs out
ReportEnquiries and booked jobs by source, plus untouched deals
Test planThe PASS and FAIL checks in this write-up
Handover and supportSOPs, a recorded walkthrough, 14 days of fixes, and an optional monthly hour block
Not includedPaid advertising, call-centre staffing, or rewriting the website form copy

Rollout, handover and monthly support

MilestoneDeliverableTimingShare of fee
M1 Discovery and rulesFindings, stages, ownership and contact rulesWeek 125%
M2 Booking flowDeal to job and write-back, tested on scripted casesWeeks 2 to 335%
M3 SLA and reportFollow-up queue and source reportWeek 425%
M4 HandoverSOPs, walkthrough, 14 days of fixesWeek 515%
Handover and monthly support

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.

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