The Owner's Morning Brief
One short list, before the board opens, of what is overdue, what failed and why, and the few things that genuinely need the owner. Assembled from what the other six systems actually did, not from what anyone reports.
- Tier
- Flagship
- Build order
- 7th of 7 for HVAC
- Shape of it
- 8 steps, 1 decision point, 1 escalation rule
- At launch
- Runs supervised, with you approving what goes out
The problem this solves
In a shop this size the owner is the escalation path by default. Everything routes to their phone eventually, and the things that reach them are the things somebody could not solve, which means they arrive late and already expensive.
The reporting that exists does not help. Platform dashboards show volume, not exceptions. A revenue number does not tell an owner that a member has been bumped twice, that four estimates over thirty thousand dollars have had no contact in three weeks, or that the failed-payment queue has not been opened since Thursday.
And the softest failure of all: people raise a problem when they are certain they cannot fix it. By then it is a week old.
How it works, step by step
Every wait, threshold and branch below is a value we set with you during the build, against your stages and your language. None of it is a default we impose.
- What starts it
- It decides something
- It escalates to a person
Step 1Trigger
Every morning, before dispatch, a single brief is assembled and sent.
Step 2
It is ordered by what needs a decision, not by category.
Step 3
Overdue: enquiries with no outcome, estimates past their next-contact date, maintenance visits moved more than once, agreements expiring inside thirty days with no contact.
Step 4
Failed, and why: messages that did not deliver, payments that declined, automations that errored, jobs that closed without required data. Each with the reason, not just the count.
Step 5Escalation
Needs a person: the specific items the rules deliberately escalate. High value estimates with no response, a second callback on the same system, a member bumped twice, any safety flag not acknowledged inside its window.
Step 6
Open estimate dollars by age band, which is the one number that changes how an owner spends their week.
Step 7
Nothing in the brief is self-reported. Every line traces to an event in a system, and every line links to the record.
Step 8Branch
If there is nothing to raise, the brief says so in one line rather than padding itself.
How it gets built
Built inside what you already run
- ServiceTitan
- Housecall Pro
- Jobber
- FieldEdge
- or whatever your office already runs on
Nothing to log into and nothing to license. If a system needs a record your platform does not hold, we add the field to your platform rather than starting a second one beside it.
This is the actual build order, in the phases its own steps fall into. It runs in supervised mode first, with you approving what goes out, until you are happy with the tone.
- 1
Agree
Agree with the owner what genuinely requires them, and be strict. A brief that lists everything gets skimmed, then ignored, then unsubscribed.
The thresholds, the wording and the names are yours. We write them down with you and get the consequential ones signed off.
- 2
Agree
Set the thresholds: the estimate value above which they are told, the number of times a member can be moved, the age at which an unanswered enquiry is raised.
- 3
Build
Build the exception queries against the system event data rather than against dashboards.
Built inside the software you already run, against your stages and your language.
- 4
Agree
Set the send time against when the owner actually reads, which in this trade is usually before six.
- 5
Prove
Review the brief with the owner weekly for the first month and cut every line they did not act on. The brief should get shorter, not longer.
It runs with a person approving what goes out until you are happy with the tone. Nothing sends unreviewed on day one.
What changes after it goes live
How it runs today
In a shop this size the owner is the escalation path by default. Everything routes to their phone eventually, and the things that reach them are the things somebody could not solve, which means they arrive late and already expensive.
After this one is live
Problems surface at a day old rather than a week old. The owner stops being the person who finds out last, and stops being the person who has to ask. And because it is assembled from events rather than from people, it does not depend on anyone being willing to raise something uncomfortable.
How to measure whether it worked
Your arithmeticRun with your numbers, not ours
This one does not have a revenue calculation and should not be given a fake one. It is the system that makes the other six trustworthy, and the honest way to value it is to ask the owner what one week of an unattended problem has cost the business in the past. They will have an example.
We agree the baseline before anything is built, and we do not take credit for things that were going to happen anyway. There is no figure on this page claiming what we have produced for somebody else, because there is no verified figure to publish.
What we will not do
This is from the same delivery document as everything above it. It is on the page because a supplier who has not thought about it will not tell you, and you would find out later.
Every system here sends automated messages to consumers in the United States, which puts all of them inside the TCPA and inside carrier A2P 10DLC registration. These are two different things and both apply. Registration is a carrier trust requirement; it does not create consent and does not make an unlawful message lawful. Unregistered application traffic gets filtered or blocked.
Classify every system before it sends. A service message is narrowly connected to an existing job: appointment confirmation, technician on the way, part arrived, invoice. A marketing message promotes something: a tune-up offer, a replacement promotion, a membership push, an estimate reactivation sequence. The standards of consent are different, and a promotional line inside a service template converts the whole message into marketing.
The minimum a compliant build has to do:
- Consent recorded per number with the date, the source, the exact wording shown, the sending brand, and whether it covers service, marketing, or both. Marketing needs prior express written consent with an unchecked opt-in, and consent cannot be a condition of purchase.
- A2P 10DLC registration of the brand, the numbers, and a campaign use case that matches the traffic actually sent. An appointment-reminder campaign does not quietly become a seasonal promotion campaign.
- Quiet hours of 8am to 9pm in the recipient's local time, not the office's, with queued sends held until the window opens. Apply the same gate to service messages by default and handle genuine emergencies as a named exception.
- Opt-out handling for STOP, UNSUBSCRIBE, CANCEL, END, QUIT, REVOKE and OPT OUT, and for free text like "stop texting me". Suppress immediately in practice rather than to the outer limit of the rule, cancel messages already queued rather than only future ones, and propagate the suppression to every sending number, system and platform the contractor controls.
- Replies routed to a monitored human queue, always. A reply that says the heat is off is not a marketing response.
- Human review before any sequence that would materially pressure a prospect, which in this playbook means System 4.
- Suppression reconciled across systems, so a customer cannot opt out in the field service platform and keep receiving messages from the marketing tool.
- Purchased or scraped lists are not messaged. Consent has to name the actual sender.
Nothing in this document is legal advice. State mini-TCPA statutes, carrier policy, and the exact dialling or sending technology can each add requirements, and the rules in this area have moved more than once recently. Every template that states a commercial term, a price, or a guarantee requires review by the contractor's own counsel before it goes live.
Nothing here is legal advice. Rules in this area have moved more than once recently, and every template that states a commercial term or a guarantee goes to your own counsel before it goes live.
Seven systems forHVAC.
We build one at a time and prove it moved before starting the next. The tiers are the dependency order, not a price list.
Tier 1Foundational
Nothing arrives late or unowned. These come first because everything above them assumes they are true.
- 1Multi-Channel Capture, Triage & Instant ResponseFastest visible result, and it is the one that survives the first heat wave, which is when the owner decides whether any of this was real.
- 2Dispatch Confirmation, Arrival Protection & Technician BriefProtects the capacity and the truck rolls already paid for.
Tier 2Growth
The recoverable money. These work the pools the foundational systems have made visible for the first time.
Tier 3Flagship
One connected system end to end, plus what the owner reads on a Monday. Only once the pieces are proven individually.
- 5The Complete Service-to-Install SystemThe flagship, once the pieces are proven individually.
- 6Service Agreement Renewal, Fulfilment & ReactivationCompounds everything above, and depends on the equipment data System 2 started collecting.
- 7The Owner's Morning Briefyou are hereOnly meaningful once there are systems to report on.
The tiers are the dependency order for HVAC, not a price list. Most firms do not start at the first one, because the order is a default and the call is where it gets changed.
A note on sequencing this trade
Do not build all seven at once.
Each stage is proven against its agreed measure before the next begins.
Season note. Build Tier 1 in the shoulder season and let it run through one peak before starting Tier 2. A contractor who sees System 1 hold on the first hot Saturday will build the rest without being sold again.
Back to the HVAC overview for the stage map and where these fit.
Is this the oneyou need first?
Often it is not. On the call we look at what is actually costing you most right now, which is frequently a different system from the one that brought you to this page. If there is nothing worth building yet, we will say so.