Yesterday in one page, by seven.
Produces daily executive briefings summarizing overnight activity, outstanding exceptions, operational risks, and leadership priorities. Your managers walk into the morning meeting having already read what the agents did overnight and what is still open.
- Covers
- Dispatch, jobs, quality, billing and messages
- Works in
- Executive Assistant ( Internal)
- Runs on
- Customer 360 and Workorder Management
- Setup
- Two choices: who receives it, and when
what it is for
Ten agents working, and no one page.
Once several agents are running, the work they do is spread across the places they do it. The dispatch board knows what was assigned, quality knows what failed, billing knows what was chased, and nobody holds the whole picture before the morning meeting. So a manager opens five screens, or asks five people, or walks in without the numbers and takes the first version of events offered.
AI Management Briefing is the one page that pulls them together. It reads the last day across every module you have switched on, counts what the agents completed on their own, and puts the open exceptions at the top: the SLA at risk, the shift still unfilled, the complaint nobody has answered. It reports. What to do about any of it stays with the manager reading it.
Tuesday, 7:00
One page, not five screens
Dispatch, jobs, quality, billing and messages arrive in one summary, in the same order every morning, so nothing is missed because it lived in another module.
Exceptions come first
SLA breaches, unfilled shifts, failed checks and open complaints sit at the top with their records attached, rather than buried under everything that went well.
The agents are visible
You can see what each agent did on its own and what it handed to a person, so running them stays a decision you keep making with evidence.
gather the day
It reads the last day across every module.
A briefing is only as good as its sources. The agent takes a fixed window (your day, in your time zone) and pulls from every module you have switched on, so the same period is covered the same way every morning.
The same cut-off each morning, in your time zone, so two briefings never overlap and nothing falls between them. Anything entered after the cut-off appears in the next day’s page and is marked as late.
If you are running three agents, the briefing covers three. It does not pad the page with empty sections for modules you have not connected or work your business does not do.
Actions the agents completed inside their approved lists are shown as counts rather than lines, so the page does not fill with a hundred entries that all went exactly as expected.
Multi-site operations get the page split the way the business is split, so a regional manager reads their own depots. Who sees which section follows the structure your teams already report in.
Sources and window
sort what matters
It separates what ran from what is stuck.
Most of a day goes as planned, and that part belongs in a count. What a manager needs by name is the small number of things still open, and the agent orders those by the rules you gave it, not by whatever happened most recently.
An SLA about to breach outranks one already missed, and a complaint outranks a late clock-in, because that is the order you set. The page does not rearrange itself around the freshest event.
Every exception carries the day it was raised and how many mornings it has now appeared on the page, so an item quietly rolling from one briefing to the next becomes obvious instead of invisible.
Each line opens the job, the invoice, the shift or the message it came from, so acting on the briefing does not start with searching for the thing the briefing mentioned.
Where an agent stopped and passed something to a person, the hand-over is named along with who received it, so nothing is assumed to be handled just because an agent touched it.
Open exceptions
report, not decide
It tells you what happened. You decide what next.
The briefing is the one place the agents are answerable, so it has to be honest and it has to stop at the edge of a decision. It names what is open. It does not close anything, reassign anything or rate anyone.
Email before the morning meeting and the same page on the dashboard, so it is read on a phone at seven or on a screen at half past, without anyone logging in somewhere new to find it.
An unfilled shift is reported, not filled. A breached SLA is reported, not explained away. The agent that could act on either is a different agent, working inside its own approved list.
It counts jobs, exceptions and hand-overs. It does not rank technicians or draw conclusions about why something was late. Where a name appears it is because a record has an owner, not because the agent formed a view.
Who receives it and when, and which exceptions they should see. There is no model to train and no report to build, because it reads the records your team is already keeping every day.
Approved actions
how it works
Four steps, then it hands on.
The same four run every morning, in the same order, so the page reads the same way whoever opens it first.
-
synthesizes
Aggregates data across dispatch, jobs, quality audits, billing, and communications over the preceding 24 hours.
-
tallies
Tallies automated actions completed without human intervention — quotes sent, rosters confirmed, payments matched.
-
isolates
Isolates outstanding exceptions — SLA breaches, unassigned shifts, customer complaints, and overdue invoices.
-
briefs
Compiles and delivers a crisp executive summary via dashboard widget and email ahead of the morning operations standup.
where the line sits
What it handles, and what it hands over.
Everything the briefing raises is handed somewhere, and the page names who, so nothing sits on it unowned.
| Item | What the agent does | Who finishes it |
|---|---|---|
| Routine agent action | Counts it with the others and shows the total, rather than listing a hundred expected lines. | Nobody, for information |
| SLA at risk | Names the job, the deadline and the time left, and links straight to the record. | Service manager |
| Unfilled shift | Reports the gap and how many mornings it has appeared. It does not fill it. | Dispatcher |
| Complaint still open | Carries it forward every morning until a person closes it, with the thread attached. | Service manager |
| Payment or invoice held | Shows the amount, why it was held and which invoice it belongs to. | Accounts team |
| Anything it cannot place | Reports it under exceptions as unclassified rather than leaving it off the page. | Named owner |
you set
Before it runs its first job, three things come from you.
- Management recipient list and preferred briefing delivery time.
- Key exception categories that warrant executive visibility.
- Benchmark operational targets for daily tracking.
None of it is a data migration. It reads the Executive Assistant ( Internal) records you already keep.
stays with your team
The briefing synthesizes operational facts and flags exceptions. It arms leadership with visibility; it does not replace executive business judgment.
Each line arrives with the record behind it, who it is waiting on and how long it has been open, so the meeting starts on decisions rather than questions.
rollout
Send it to one manager first.
Most teams do not switch every action on at once, and nothing here requires it. The usual order:
Watch first
Run it to a single inbox for a week, yours, with every section in it. You see what the page looks like before anyone else is asked to act on it.
Then the management list
Add the managers who need it and cut each section to the exceptions they actually own, so nobody scrolls past four other teams to find their own.
Then widen the sources
As you switch more agents on, their work joins the same page. There is no new report to build and no second screen to check.
works with
What it runs on, and what it hands to.
read next
Reading between the morning numbers.
before you switch it on
What teams ask about AI management briefing.
Only inside the rules you set. Anything outside them - listed under "you set" above - goes to a named person on your team, with the record attached. There is no state where it silently makes a judgement call you have not already approved.
Days, not months. It reads from the records you already keep in Executive Assistant ( Internal), so there is no separate data migration or new system for your team to learn before it can start.
Yes, instantly, and every action it took stays on the record so you can see exactly what it did and reverse it. Turning it off does not remove or hide anything it has already written.
No. It takes the routine, repeatable part of the job off their desk so they spend their time on the exceptions and judgement calls that actually need a person - the work listed under "stays with your team" above.
AI management briefing runs on your Executive Assistant ( Internal) records, alongside Customer 360 and Workorder Management, so nothing needs re-keying between systems.
Yes. The page is split the way your business is split, by site, region or crew, and each recipient gets the sections they own. The counts still add up across the whole operation, so a general manager can read the full page while a site manager reads one part of it.
A dashboard answers a question you thought to ask. The briefing arrives whether or not anyone thought to open it, in the same order every day, with the exceptions ranked by your rules. It is a short read before a meeting rather than a screen to interrogate, and it covers modules a single dashboard usually does not.
Yes, and the page stays honest about it. It covers the modules you have connected and leaves the rest out, rather than showing empty sections. Teams often start here, because a briefing on two agents is also the clearest way to see whether those two are worth widening.
See tomorrow’s briefing on your own day.
Book a demo
We will build one morning from your own records, with your modules and the exceptions your managers ask for.
Book a demoSee the other nine
AI management briefing is one of ten agents on one job record, from first enquiry to paid invoice.
All AI agentsSee the platform
The field service system underneath: scheduling, work orders, assets, invoicing and the field app.
AI Field Service Management