The short version: A Power Automate flow catches the enquiry the moment it lands on your contact form, sends the customer an automatic message so they know it arrived, and puts it in front of whoever is free rather than one inbox. Built on Forms and Outlook you already pay for, it works the same at 11pm as it does at 11am.
The form fires a flow, not just an email
Most small business contact forms do exactly one thing: email whoever set them up, years ago, possibly someone who has since left. Point the form at a Power Automate flow instead, and the same submission can write a row into a shared list, post into a Teams channel the whole team watches, and send the customer an automatic acknowledgement, all at once, all built on Forms and Outlook connectors that are already inside the Microsoft 365 you pay for. Nothing here needs a premium licence: this is the standard-connector territory the Power Automate pricing post covers.
The shared list matters more than the acknowledgement email does. An enquiry sitting in a Teams channel gets picked up by whoever finishes a call first; an enquiry sitting in one person's inbox gets picked up when that person happens to check it, which on a job site can mean tomorrow.
After hours and while you are on a job
A flow does not know or care what time it is. A form submitted at 9pm on a Sunday triggers exactly the same sequence as one submitted at 10am on a Tuesday: the acknowledgement goes out, the notification lands in Teams, and it is sitting there, visible, waiting for the office to open. That alone fixes the after-hours gap, because the customer gets something the moment they send it, and you get an accurate list of what is waiting rather than a guess based on what you remember checking.
While you are on a job, the same mechanism means you never have to touch your phone for the acknowledgement to go out. A text or Teams notification tells you an enquiry landed, and you look at it on your own time, at smoko or on the drive between jobs, rather than mid-task. A second, scheduled flow can check for anything still unmarked after a working day and nudge you again, so a quiet form does not just stay quiet.
When it is not worth building
If you already answer every enquiry off your phone the moment it buzzes, this is solving a problem you do not have, and the ten minutes it takes to set up would be better spent elsewhere. Build it once enquiries genuinely sit for hours, once a second person needs to see what is waiting, or once "I'll get to it" has cost you a job you can point to.
Common questions
What happens to enquiries that come in after hours on my contact form?
The same flow fires whatever time it is. The automatic acknowledgement and the internal notification both go out immediately, whether that is 11am or 11pm; the only thing that changes is when you personally get back to them.
How do I stop website enquiries getting missed in my inbox?
Route the form to a shared list or a Teams channel everyone can see, not one person's personal inbox where it can sit unread over a weekend. Visibility, not speed, is what actually stops enquiries getting lost.
What's a good way to auto-reply to enquiries while I'm on a job?
An automatic acknowledgement goes out the moment the form is submitted, with no one touching a phone, and a Teams or text notification lets you see the actual detail on your own time rather than mid-job.
Enquiries sitting in an inbox nobody watches?
Tell me where your form sends things now. Book a free 30-minute call and I will scope the flow that catches it properly.