Illustrative workflow examples
3 Trade Admin Workflows: From Enquiry to Invoice
What does “less evening admin” look like in practice? These three worked examples show how customer details can move through a trade business without someone copying the same information at each stage.
Worked examples, not customer results
The starting point is the software you already have. Jobber documents quote and invoice follow-ups; Tradify links enquiries to later work; ServiceM8 Phone includes its own call and voicemail features. A useful setup builds around those capabilities and adds a connection where your actual handover needs it.
One customer, one record: a worked example
Fictional example: Alex at Example Plumbing receives a tap-repair enquiry from Sam. The references below are invented and contain no real customer data. This is a design illustration, not a live product screen or a customer result.
| Stage | What joins the record | Human check |
|---|---|---|
| Enquiry | The original message, contact route and job reference sit together. | Alex checks the customer match and confirms the job location. |
| Quote | Quote Q-031 links to job J-208 and customer C-104; the original message stays available. | Alex checks scope and price before sending. |
| Follow-up | The record shows when the quote was sent, who owns it and the agreed next action. | Check for a reply or existing reminder before contacting Sam. |
| Customer replies | Sam asks to change the visit date. The reply is attached and the old reminder is cancelled. | Alex confirms the change; uncertain matches go to review. |
| Job complete | Completion notes and the approved quote inform an invoice draft linked to the same job. | Review variations, amount and recipient before sending. |
The customer record answers who; the job record answers which piece of work. One customer can have several jobs, so combining everything into a single unstructured note can create a different kind of confusion. See how to keep customer and job records connected.
Try the handover test: could a colleague find the original request, current quote, latest reply and next action without asking Alex? Test with fictional records first and supported connections only.
1. A phone enquiry and photos become one piece of work
The situation: a plumbing business receives a repair enquiry by phone. The customer sends photos later. That evening, the owner searches the chat, copies the address into a quote and tries to remember what was agreed.
The design: keep the contact, job location and source messages beside one enquiry. An agreed intake route brings in each supported channel; a staff member can attach material from a channel that is not connected. Assign the next step to the person preparing the quote, with missing details visible.
The human check: confirm the customer and property. A matching number does not establish which of several addresses is the job location. The person responsible checks the scope and decides whether a site visit is needed before pricing.
Why the design is plausible: Tradify describes capturing enquiries and turning them into quotes, jobs and invoices. That supports a connected handover, but it does not mean every private chat automatically appears in every system.
What to measure: active time spent finding messages and re-entering details; how often staff ask again for information already supplied; and incorrect customer or address matches. Count the time needed to review and correct the record too.
Use the enquiry checklist to choose the fields, and the customer-record guide to agree where the history lives.
2. A sent quote gets a clear follow-up and stopping rule
The situation: an electrical contractor sends several quotes during the week. Follow-up depends on remembering which customers have replied, and another team member sometimes chases a quote after the customer has already answered.
The design: give the quote an owner and an agreed review date. Use the existing platform’s reminders where they fit. A staff reminder and a message sent to a customer are different actions; decide which is wanted. Keep the reply with the same enquiry and pause further chasing while someone handles it.
The human check: a question about scope needs a useful answer, not another reminder. A requested change may need a revised quote. Acceptance still needs the appropriate job and availability checks before anyone promises a visit.
Why the design is plausible: Jobber documents both internal quote reminders and plan-dependent customer follow-ups. Its automation options show that reminding people is already a native feature in some software. The custom work is making the actual reply and handover fit the team, rather than adding a second reminder sequence.
What to measure: time spent checking and chasing quotes; reminders sent after a reply; and quotes with no owner or next action. Track quote outcomes separately. A reminder sent is not evidence of a sale caused by the workflow.
Adapt the quote follow-up texts and emails. The wording should reflect a real conversation and a realistic next step.
3. Completed job details prepare an invoice for review
The situation: a small maintenance team completes a job, but notes about labour, materials and agreed extras are spread across messages. The owner spends the evening assembling the invoice and checking what the customer approved.
The design: agree what “ready for billing” means. Bring the relevant customer, payer, job reference and approved work into the invoice-preparation step. Keep missing information visible in a review queue. If the job system already creates the draft, use that route and focus the integration on the missing details or accounting handover.
The human check: confirm the payer, price, approved extras and billing details before sending. A completed visit does not by itself prove that every item is chargeable. Record an invoice reference so a repeated delivery cannot create another invoice for the same event.
Why the design is plausible: Tradify’s documentation explains a route from an enquiry through a job to quote or invoice templates. This illustrates why the way records connect matters. An invoice draft, its approval and its payment are separate states.
What to measure: active preparation time, time spent collecting missing details, corrections after review and the gap between billing readiness and sending. Measure payment timing separately; a customer may pay late for reasons unrelated to invoice preparation.
Keep the confirmed work and customer history together as described in the single customer record guide.
What the alternatives already do
| Platform | Relevant native feature | Question for your setup |
|---|---|---|
| Jobber | Quote and invoice follow-ups, with plan-dependent automation. | Does configuring the existing reminder solve the problem? |
| Tradify | Enquiries linked to quotes, jobs and invoices. | Which information is still being copied or gathered manually? |
| ServiceM8 Phone | Native phone and voicemail handling. | Is the gap message capture, or what the team does after receiving it? |
These products are alternatives and potential systems to work with; this is not a like-for-like ranking or a claim that MMD outperforms them. If a native feature solves the task, configuring it may be the right engagement. Custom integration is useful when a real gap remains between the tools or stages you use.
Test the idea against a normal working week
Choose one workflow and a small set of comparable enquiries, quotes or completed jobs. Record the current steps before changing them. Then record the same measures during the trial, including review, correction and extra information-gathering time. Keep owner estimates separate from timed observations.
- Define which events qualify and which do not before comparing results.
- Log the number of events, their complexity and the people doing the admin.
- Include correction and monitoring effort whoever performs it.
- Check for duplicate records, wrong matches and inappropriate messages.
- Ask whether the business actually keeps using the process.
Download the blank workflow observation sheet (CSV)
Use event references and redacted notes in the sheet; it does not need customer names or full transcripts. There are no pre-filled savings or conversion rates. A later case study should report the period, event count, measurement method, results and limitations, with permission to publish.
A useful result may be less evening work or an easier handover. It should not be presented as extra revenue unless the commercial effect has actually been established.
Where MMD fits
We help identify the repeated admin, configure suitable existing features and connect the handover around the client’s workflow. That can involve the CRM or job-management system you already use, with agreed ownership and a visible next action.
The public phone demo shows speech becoming text in a private session. The examples here describe workflows to discuss and scope. Enquiry & quote follow-up and Invoice & payment reminders are optional £19/month additions alongside the £49/month Callback package, plus one £49 standard setup fee, before any applicable VAT. The public demo does not include those additions. Custom connections are quoted separately and pilot availability is confirmed before payment.
Start with whether a CRM fits your business, or read the enquiry automation guide for the shared setup decisions.
Sources and review
Reviewed 17 October 2026. Jobber: customer follow-up automations · Jobber: internal quote and invoice reminders · Tradify: connected enquiry stages · Tradify: templates and job records · ServiceM8 Phone: existing phone and voicemail features.
These are MMD’s illustrative workflow designs, informed by published software features. They are not client case studies, measured savings or a claim that every connection is available in the public demo. Platform features and plan availability can change.
Plan the human follow-up too: use the free callback checklist and customer reply templates.
Before sending the next quote, check its job profit, including your labour and admin time.