Work snippet
Jotform and Typeform to a ServiceM8 job, with a hold queue
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
Discovery findings
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.
| ID | Finding | Evidence | Risk if left |
|---|---|---|---|
| F1 | Submissions arrive as email, then someone types a ServiceM8 job | Median 3 hours from submit to job, some next day | Urgent work is late, or typed twice |
| F2 | Required site fields are optional on one of the forms | 14 submissions in a month with no unit or suburb | The job cannot be scheduled without a call back |
| F3 | A double submit creates two jobs | Two jobs, same email, 40 seconds apart | A crew is booked twice |
| F4 | Attachments are left in the form product, not on the job | Photos of the asset sit in a form inbox | The technician arrives without the pictures |
| F5 | No hold queue for incomplete or after-hours submissions | After-hours forms sit until the morning, unsorted | The morning starts with a hunt through email |
Approach
- Lock the webhook and the required fields
Signed posts only, and a written list of what must be present.
- Create one job per submission id
The same post cannot create a second job.
- Move the files with the job
A failed fetch holds the item rather than pretending the file arrived.
- Give incomplete work a queue and an owner
The flow does not write to the customer on its own.
Current state and future state
Current state
Future state
Future-state modules
How it is built
- Module AWebhook and signature
Each form posts to Make with a verified signature, so a forged post is refused.
- Module BValidation
Required fields, phone format, and a duplicate key of email + site + calendar day.
- Module CJob create
A valid submission creates one ServiceM8 job, with the form name as the source.
- Module DAttachments
Files are pulled and stored on the job, or the item is held if a file cannot be fetched.
- Module EHold queue
Incomplete, duplicate or after-hours items (if that is the written rule) wait for a person, with a reason.
Field mapping
| Form field | ServiceM8 field | Rule | If missing |
|---|---|---|---|
| Full name, email, mobile | Client name, email, mobile | Match an existing client on email or mobile first | Hold if both are blank |
| Site address, unit, suburb | Job site | Unit is required for strata sites | Hold, reason: incomplete site |
| Work description | Job description | Copied as submitted, not rewritten | Hold if shorter than the written minimum |
| Preferred window | Booking request | A request, not a confirmed booking | The job is unscheduled until a person confirms |
| Source form name | Job source / campaign | Jotform or Typeform, plus the form title | Never blank |
| File upload | Job attachment | Fetched in the same run where possible | Hold if the fetch fails after two retries |
| Submission id | Custom field and idempotency key | One job per submission id | A replay does not create a second job |
Worked exhibits
Exceptions and runbook
| Case | Rule | Who acts | First action |
|---|---|---|---|
| Incomplete site or contact | Hold, do not create a job, do not email the customer from the flow | Reception | Call or email, complete the fields, then release |
| Duplicate of email + site + day | Block the second job, attach the new text to the first submission where useful | Reception | Check it is not a second, genuine job at a different unit |
| File fetch fails | Retry twice, then hold with the file link | Operations | Download by hand, attach, release |
| After-hours, if the written rule is to hold | Hold until 07:30, then create the job or keep holding if still incomplete | Flow, then the morning owner | The morning list is sorted by form time |
| Webhook signature fails | Refuse the post, alert operations | Operations | Check the form connection; do not accept an unsigned retry |
How to read the exhibits
- The monthly figures show intake and holds across both form sources.
- The hold window shows that an incomplete address never becomes a scheduled job on its own.
- Jotform and Typeform are treated as two sources with one set of rules.
Test plan
| ID | Check | Method | PASS when | FAIL when |
|---|---|---|---|---|
| T1 | Happy path | Submit a complete Typeform and a complete Jotform | One job each, source named, files attached | A missing source or file |
| T2 | Duplicate | Submit the same complete form twice in one day | One job, second item marked duplicate | Two jobs |
| T3 | Incomplete | Omit the unit on a strata address | Held, no job, no customer email from the flow | A job with a blank site |
| T4 | Replay | Resend the same submission id | No second job | A duplicate job |
| T5 | Bad signature | Post without a valid signature | Refused, alert raised | A job is created |
| T6 | File failure | Force a failed fetch | Two retries, then a hold with the link | The job is created as if the file had arrived |
Scope
| Area | Included |
|---|---|
| Discovery | Existing forms, email-to-job path and a month of submissions, with written findings |
| Webhooks and validation | Signed posts, required fields and the duplicate key |
| ServiceM8 job create | One job per submission, source named |
| Attachments | Fetch, store, or hold |
| Hold queue | Reasons, owner and release steps |
| Test plan | The PASS and FAIL checks in this write-up |
| Handover and support | SOPs, walkthrough, 14 days of fixes, optional monthly hour block |
| Not included | Redesigning the public form copy, or paid ads that drive the forms |
Rollout, handover and monthly support
| Milestone | Deliverable | Timing | Share of fee |
|---|---|---|---|
| M1 Discovery and rules | Findings, required fields and the duplicate key | Week 1 | 25% |
| M2 Flow and attachments | Jobs created in a copy, files stored or held | Week 2 | 35% |
| M3 Hold queue and tests | Queue live, all checks passed | Week 3 | 25% |
| M4 Handover | SOPs, 14 days of fixes | Week 4 | 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 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.