Say you are at lunch, or stuck in a meeting, and an urgent email lands from a customer who needs certs before a truck leaves. Today, that email waits for you. When you get back, you read it, find the order, dig up the mill certs, and start assembling the packet while the truck idles.
Now run the same hour with an AI employee on the inbox. It reads the email, pulls the order and the mill certs, assembles a draft packet, and pings you. When you get back to your desk, the context is gathered and the first pass is waiting for your review. You still decide what goes out, but the request did not sit untouched while you ate.
The AI is most useful in the hours nobody is watching it, and those are the hours an owner is least comfortable letting it work.
1. AI moved out of the chat window
Most people picture AI as a chat window. You go to it, type a question, get an answer, and it waits until you come back. That is how most people met ChatGPT, and it is why many owners still file AI under "fancy search box."
The AI we build works more like a colleague who is always on. It has a role, a job description, and the standard operating procedures that go with it, the same things you give a new hire. So it does not wait to be asked. When a request comes in, it starts. When something is waiting on you, it nudges you before you go looking. We call this AI everywhere: an AI that does the first pass in the background and reaches out to a person when a decision is needed.
2. Requests wait while you are away
Every manufacturing office has what we call the away gap: the time between a request landing and the person who owns it starting on it. Lunch is part of it. So are meetings, a walk out to the floor, the evening, and the weekend.
The away gap rarely shows up on a report, because nobody is working during it. The cost shows up later, as a Monday morning that starts with a pile of unread mail, or a customer who waited all afternoon for an answer that took minutes to write.
An always-on AI closes most of that gap by working when people cannot. Email that arrives after hours or over the weekend still gets read, sorted, matched to its order, and drafted. It is also fast at the reading part. In one of our builds, the AI sorted and categorized 500 emails in under 8 seconds, because it works on many at once instead of one after another. No person can read at that pace, and nobody should have to.
For now, the colleague works in writing. It reads email and messages you. Voice is coming, but we do not deploy AI on phone calls today.
3. It reads, sorts, and drafts on its own
"Always on" worries owners, and it should, until they see where the lines are. We draw those lines before anything goes live. We sit with your team and map the job step by step: where the work goes, and where a person has to verify it. That map decides what the AI does alone.
In the lunch-hour example, the list of things it may do without asking is short:
- It reads incoming email in the queues it is allowed to see.
- It matches each request to an order and pulls the records that go with it, such as the job record and the mill certs.
- It drafts the document, in this case a cert packet, and saves it to a review queue.
- It flags anything that does not match, and pings the person who owns the request.
Every item on that list is reading, sorting, or drafting. None of it reaches a customer.
4. Sending, signing, and deciding wait for a person
The other list is just as clear. In the systems we build today, the AI does not send email. It can read an inbox and draft a reply, and a person sends it. A named person signs every cert packet, decides every price, and answers every customer who needs a real conversation.
The AI also works under its own login, and that login can see only the systems its job needs. An AI that drafts cert packets might read the order history and the mill certs and write only to a drafts folder. It cannot change a price or release an order if its login was never given that access, and for a drafting job it should not be.
When the AI is not sure, it stops. If the heat number on a mill cert does not match the receiving log, it does not guess. It flags the mismatch and asks the right person to confirm, and the draft waits with the flag attached.
5. The activity feed shows every step it took
A colleague who works while you are away is only useful if you can see what they did. So the AI employees we build keep an activity feed: a step-by-step record of everything it did, with the time and the source it used. When someone checks its work, they read the feed the way you would read the sign-off column on a traveler.
Read the last line of that feed again: nothing was sent. The AI did two minutes of reading, matching, and drafting, and it left the one decision that mattered for the quality lead. Leadership gets something it rarely has today, a plain record of what was done and what is waiting.
What to do this week
- The next time an urgent customer email arrives while its owner is away, note when it landed and when someone started on it. That is your away gap.
- Look at last week's email to one shared inbox and count how many requests arrived at lunch, after hours, or over the weekend.
- Pick the most common of those requests and write two lists: what an AI could do alone (read, match, draft, flag) and what must wait for a person (send, sign, decide).
- Name the person who should get the ping for that request, and decide how they want to receive it.
This essay comes from Manufacturing's ChatGPT Moment Hasn't Happened Yet: Why AI Fits Your Paperwork and How to Prepare. For the full rules on what an AI employee may do in a shared inbox, read How an AI Employee Works in Your Shared Inbox: It Reads and Drafts, Your People Send.
Questions people ask
Can an always-on AI send emails to customers while we are away?
Not in the systems we build today. It reads, sorts, and drafts, and a person sends every email. When a request is urgent, it pings the person who owns it, so the draft is ready when they get back.
How do I know what the AI did while nobody was watching?
Its activity feed lists every step with the time and the source: which email it read, which order it matched, what it flagged, and where it saved the draft.
Terms in this piece
- AI everywhere
- an always-on AI that does the first pass in the background and reaches out to a person when a decision is needed.
- Away gap
- the time between a request landing and the person who owns it starting on it, such as lunch, meetings, evenings, and weekends.
- First pass
- the draft the AI prepares, such as a cert packet or a quote, before a person checks it.
- Activity feed
- the step-by-step record of everything the AI did, with times and sources, that a reviewer can read.
- Permissions
- the rules for what an AI system is allowed to see and do, set on its own login.
