Manaz Afzal Book a consultation

Work snippet

Jotform and Typeform to a ServiceM8 job, with a hold queue

Concept DesignIllustrative integration walkthrough. Business details, figures and records are worked examples.

A field service business that takes work through Jotform and Typeform. A Make flow checks each submission, opens one ServiceM8 job when the required fields are there, saves the attachments to the job, and holds incomplete or repeated submissions for a person.

The problemForm submissions are retyped into ServiceM8, and incomplete ones get lost.

What changesComplete submissions become one job each; incomplete ones wait in a hold queue.

Area
Form intake to the job system
Tools
Jotform · Typeform · Make · ServiceM8
Typical scope
US$1,800-3,400
Timeline
About 4 weeks · fixed milestones

The problem

Submissions arrive as emails, someone retypes the job, the photos stay in the form tool, and a customer who presses submit twice gets two jobs.

  • Hours can pass before a job exists in ServiceM8
  • Required site fields are skipped, so the job cannot be scheduled
  • A double submit books a crew twice
  • Technicians do not have the photos the customer already sent

What discovery would examine

A review of website forms, the current email-to-job path, and one month of submissions for a field service business using Jotform and Typeform as the public intake.

Findings from the review
IDFindingEvidenceRisk if left
F1Submissions arrive as email, then someone types a ServiceM8 jobMedian 3 hours from submit to job, some next dayUrgent work is late, or typed twice
F2Required site fields are optional on one of the forms14 submissions in a month with no unit or suburbThe job cannot be scheduled without a call back
F3A double submit creates two jobsTwo jobs, same email, 40 seconds apartA crew is booked twice
F4Attachments are left in the form product, not on the jobPhotos of the asset sit in a form inboxThe technician arrives without the pictures
F5No hold queue for incomplete or after-hours submissionsAfter-hours forms sit until the morning, unsortedThe morning starts with a hunt through email

Approach

  1. Lock the webhook and the required fields

    Signed posts only, and a written list of what must be present.

  2. Create one job per submission id

    The same post cannot create a second job.

  3. Move the files with the job

    A failed fetch holds the item rather than pretending the file arrived.

  4. Give incomplete work a queue and an owner

    The flow does not write to the customer on its own.

Current state and future state

Form intake, current and future

Current state

Jotform / TypeformCustomer submits
EmailInbox of several people
ServiceM8Typed by hand
AttachmentsLeft in the form product

Future state

Jotform / TypeformWebhook
Make validationRequired fields and duplicates
ServiceM8 jobOr a hold queue
AttachmentsStored on the job

Future-state modules

Jotform / TypeformSigned webhookMakeValidate, map, keyServiceM8 jobComplete submissionsHold queueIncomplete or duplicate

How it is built

Module-level build
  1. Module AWebhook and signature

    Each form posts to Make with a verified signature, so a forged post is refused.

  2. Module BValidation

    Required fields, phone format, and a duplicate key of email + site + calendar day.

  3. Module CJob create

    A valid submission creates one ServiceM8 job, with the form name as the source.

  4. Module DAttachments

    Files are pulled and stored on the job, or the item is held if a file cannot be fetched.

  5. Module EHold queue

    Incomplete, duplicate or after-hours items (if that is the written rule) wait for a person, with a reason.

Field mapping

Field map, form to ServiceM8 job
Form fieldServiceM8 fieldRuleIf missing
Full name, email, mobileClient name, email, mobileMatch an existing client on email or mobile firstHold if both are blank
Site address, unit, suburbJob siteUnit is required for strata sitesHold, reason: incomplete site
Work descriptionJob descriptionCopied as submitted, not rewrittenHold if shorter than the written minimum
Preferred windowBooking requestA request, not a confirmed bookingThe job is unscheduled until a person confirms
Source form nameJob source / campaignJotform or Typeform, plus the form titleNever blank
File uploadJob attachmentFetched in the same run where possibleHold if the fetch fails after two retries
Submission idCustom field and idempotency keyOne job per submission idA replay does not create a second job

Worked exhibits

One month of form intake, walkthrough figures
Submissions168both forms
Jobs created the same run141
Held for a person19incomplete, duplicate, or file fetch
Duplicates blocked8same email, site and day
Attachments stored on the job124of 131 that included a file
Created same run141Held incomplete11Held duplicate8Held file fetch8
A held submission and a clean job
Make · hold queue
SubmissionJT-88341
FormBreakdown request
ReasonIncomplete site
MissingUnit number
OwnerReception
CustomerNot contacted by the flow
ServiceM8 · job 19012
SourceTypeform · new connection
SiteComplete, including unit
StatusUnscheduled
Attachment2 photos on the job
Submission idTF-22019

Exceptions and runbook

Exception runbook
CaseRuleWho actsFirst action
Incomplete site or contactHold, do not create a job, do not email the customer from the flowReceptionCall or email, complete the fields, then release
Duplicate of email + site + dayBlock the second job, attach the new text to the first submission where usefulReceptionCheck it is not a second, genuine job at a different unit
File fetch failsRetry twice, then hold with the file linkOperationsDownload by hand, attach, release
After-hours, if the written rule is to holdHold until 07:30, then create the job or keep holding if still incompleteFlow, then the morning ownerThe morning list is sorted by form time
Webhook signature failsRefuse the post, alert operationsOperationsCheck the form connection; do not accept an unsigned retry

How to read the exhibits

  1. The monthly figures show intake and holds across both form sources.
  2. The hold window shows that an incomplete address never becomes a scheduled job on its own.
  3. Jotform and Typeform are treated as two sources with one set of rules.

Test plan

PASS / FAIL checks
IDCheckMethodPASS whenFAIL when
T1Happy pathSubmit a complete Typeform and a complete JotformOne job each, source named, files attachedA missing source or file
T2DuplicateSubmit the same complete form twice in one dayOne job, second item marked duplicateTwo jobs
T3IncompleteOmit the unit on a strata addressHeld, no job, no customer email from the flowA job with a blank site
T4ReplayResend the same submission idNo second jobA duplicate job
T5Bad signaturePost without a valid signatureRefused, alert raisedA job is created
T6File failureForce a failed fetchTwo retries, then a hold with the linkThe job is created as if the file had arrived

Scope

AreaIncluded
DiscoveryExisting forms, email-to-job path and a month of submissions, with written findings
Webhooks and validationSigned posts, required fields and the duplicate key
ServiceM8 job createOne job per submission, source named
AttachmentsFetch, store, or hold
Hold queueReasons, owner and release steps
Test planThe PASS and FAIL checks in this write-up
Handover and supportSOPs, walkthrough, 14 days of fixes, optional monthly hour block
Not includedRedesigning the public form copy, or paid ads that drive the forms

Rollout, handover and monthly support

MilestoneDeliverableTimingShare of fee
M1 Discovery and rulesFindings, required fields and the duplicate keyWeek 125%
M2 Flow and attachmentsJobs created in a copy, files stored or heldWeek 235%
M3 Hold queue and testsQueue live, all checks passedWeek 325%
M4 HandoverSOPs, 14 days of fixesWeek 415%
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 hold queue, new form fields, and any change to the duplicate key 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$1,800-3,400

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