For a 12-person HVAC contractor, should a website quote request text the owner, create a tracked intake item, or go to a shared inbox?
Create a tracked intake item first, then alert the person who owns the callback. A 12-person HVAC contractor loses quote requests at the handoff, not at delivery: the form submits, the email lands, and nobody is named as the one who calls back by a set time. An owner alert or a shared inbox can sit on top of the tracked item, but neither one, used alone, tells you whether the customer actually got a call.
A quote request that sits for two days usually has a simple cause. Everyone saw the notification, everyone assumed someone else had it, and the homeowner with a dead furnace called the next company on the list. The lost job never shows up in a report, because a request nobody answered leaves no trace except the original email. Office staff then spend Monday morning reconstructing who was supposed to call whom, and the owner fields an annoyed follow-up call from a customer who already feels ignored. The fix starts with a site where every quote request reaches a named person with a callback time, not just an inbox.
Owner alert, tracked intake or shared inbox: which fits?
- Owner alert fits when the owner is explicitly on duty and personally records each request and callback; avoid it as the only mechanism, because the owner is often on a roof or under a house when the alert arrives.
- Tracked intake in an existing Planner basic plan, plus an alert, fits when the office and the owner both need an assignee, a due time and a done state; avoid it if your field-service or job-management software already gives you those same controls, since a second queue splits the truth.
- Shared inbox with a named duty person and a manual open-request register fits when the office already lives in Outlook and reliably assigns and reviews callbacks; avoid treating read or unread status as ownership, because an opened email is not a returned call.
Owner alerts deserve one caution. Microsoft's Power Automate documentation for Forms describes a custom email notification to someone other than the form owner, and the Teams connector posts Teams messages. Neither is an included text-message service, and neither proves anyone handled the request. Calling either one an SMS alert sets the wrong expectation.
Recommendation for a 12-person HVAC contractor
Keep the request as a record, assign a callback owner and an agreed due time, then alert that person. For most small contractors already on Microsoft 365, a Planner task created from each submission gives you the assignee, the due date and the completion state, and a Teams or email notice points the duty person at it. The alert is the nudge; the task is the intake record.
One condition changes the answer: if your job-management or field-service system already owns intake, send the website form there and skip Planner entirely. The same applies if nobody on staff actually watches Teams or Planner during the day. A queue that no one opens is worse than a shared inbox someone checks every hour.
Chrysis builds contractor websites where the quote form feeds a tracked handoff like this, using the Microsoft 365 tools the office already pays for rather than a new paid messaging service.
How the tracked handoff works under the hood
Identify the actual form technology before wiring anything. Microsoft's Power Automate scenario documentation (ms.date 2026-09-21) uses Microsoft Forms as its example, so a custom HTML form on your website is not automatically connected to Power Automate. Many contractor sites send form submissions as an email, and the first job is confirming exactly where those emails land today.
The Planner connector documentation (updated 2026-05-05) lists a Create a task action with fields including Assigned User Ids and Due Date Time, plus actions to update task progress. The same page states that the connector currently supports basic plans only, so a premium Planner plan will not work with this route.
Teams notifications through the Teams connector (documentation updated 2026-11-05) have an admin prerequisite: the Workflows app, formerly Power Automate, must be available and set to allow in the Teams admin center. If Teams messages never arrive, check that setting before rebuilding the flow.
Shared mailboxes carry their own rules. Microsoft's shared mailbox guidance (ms.date 2026-03-13) supports multiple people reading and sending from one mailbox, including on Outlook mobile, but staff open it through their own licensed accounts. Microsoft says to block direct sign-in for the shared mailbox account and keep it blocked, so a shared password on the office whiteboard is the wrong setup.
- Prerequisites: a Microsoft 365 tenant with Power Automate available, a Planner basic plan for quote requests, and a named duty person for each working day.
- Confirm today's route: submit a test quote from the live website and note which mailbox or form service receives it, and how long it takes.
- Create one flow that turns each submission into a Planner task with the customer's details, an assignee and a due time you have agreed internally.
- Add one notification, by email or Teams message, to the assignee that links to the task rather than repeating the whole request.
- Keep a manual fallback: once a day the duty person compares original submissions and the shared inbox against open Planner tasks, adds anything missing by hand and phones the customer.
- Test three failure cases before relying on the setup: the owner is away, the alert fails to send, and the same customer submits twice. Each case should end with one open callback task, not zero and not two.
Frequently asked
Can Microsoft 365 text the owner's phone directly when a quote comes in?
Microsoft documents email notifications and Teams messages for this, not an included SMS service, and a phone alert still does not record who called back.
Is a shared inbox enough for a small HVAC office?
A shared inbox works when a named duty person assigns and reviews every request, but read or unread status alone does not show who owns the callback.
Does Planner work with any website form?
Planner can hold the task, but you first need to confirm how your website form delivers submissions, since Microsoft's Power Automate example uses Microsoft Forms, not arbitrary HTML forms.
Do we need Planner if we already use field-service software?
No. If your job-management system already tracks intake with an assignee and due time, route the website form there instead of creating a second queue.
Are there date-specific changes forcing this decision now?
No vendor announcement or retirement drives this choice; the documentation cited here was checked on 2026-11-09.