What I’d start with
One form, one job list, one set of reply templates and one follow-up rule.

PLUMBERS & ELECTRICIANS
For a sole trader or small team whose new jobs arrive while everyone is out working. Give each website enquiry a place to go and a clear next step.
See the automation flowIllustrative example · a possible starting point for your business
THE PROBLEM
You’ve finished the last job, but the enquiries haven’t stopped. A kitchen tap to replace, a request for a quote, someone asking when you can come round. The details are scattered across messages and your memory.
THE SOLUTION
I’d start with your website enquiry form. Structured fields feed a job list, a reply template asks the right next question, and a task keeps the enquiry from disappearing.
Capture the customer, job description, postcode and preferred time.
Create one job record. Check the postcode against your service area and flag missing details.
Draft a reply from an agreed template and create a follow-up task.
Review the job and availability, edit the draft and send it when you’re ready.
WHEN SOMETHING NEEDS CHECKINGPostcode missing or outside your area?
Keep the enquiry flagged. Ask for the missing detail or prepare your agreed out-of-area reply; don’t promise a visit.
WHAT YOU GET
The useful bit is what’s waiting for you when you put the tools down. See the job, the unanswered questions and the next action without rereading the whole enquiry.
Illustrative record. The landing-page demo uses two sample messages to show this outcome. A first live version would use form fields; free-text extraction would be scoped and checked separately.
INTEGRATIONS & HOSTING
| Tool | Its part in the workflow |
|---|---|
| Website form | Provides named fields and a submission ID. I’d check that your form can pass those details to the workflow. |
| Microsoft Lists | Holds the job record, its status and a link to the original enquiry. |
| Outlook & Microsoft To Do | Hold the reply draft and follow-up task in tools you can open on your phone. |
For a business using Microsoft 365, I’d use Power Automate for the workflow, with fixed rules and reply templates. AI isn’t needed for structured form fields.
The flow would run in Microsoft’s cloud, in your Power Platform environment. I’d confirm its region, account ownership and connector costs before the build.
A SENSIBLE FIRST PROJECT
One form, one job list, one set of reply templates and one follow-up rule.
Compare the manual steps per enquiry and check how many enquiries still have no next action.
Drafts stay unsent. A repeat submission is checked by ID, and a failed run is flagged for follow-up.
Tell me how it works today. If we agree a suitable first automation, I’ll build it for free and give you 30 days to try it. We agree the ongoing monthly price and any software costs before starting.