Shared inbox
Urgent work looks like every other message.
- Hold sits beside routine mail
- Context stays in the thread
- Someone has to dig before acting
Operational email OS
Built now for logistics teams · Other industries welcome
Email in. Finished work out.
InboxOS turns inbound freight email into structured, prioritised work. You choose which low-risk workflows may auto-advance; uncertain and high-impact work stays with people.
One email. Four controlled stages.
Fast enough for operators. Clear enough for review.
- IntakeEmail + documents
- UnderstoodIntent + fields
- RoutedPriority + risk
- ApprovedA person sends
The idea
A chatbot helps a person answer email. InboxOS helps an organisation finish the work the email is about.
Email is the front door. Completed work is the product. That is controlled autonomy: you decide which workflows may advance automatically, while every external reply stays under your authority.
Say it in one line Chatbots answer mail. InboxOS completes the work.
Before and after
Same customs hold.
A different day for the team.
One familiar freight exception. Left: buried in the shared inbox. Right: raised as work, with a draft waiting for a person.
Work queue
The same hold rises as owned work.
- Exception rises with priority and risk
- Fields and draft wait together
- Authority stays with your team
Noise becomes owned work. A person stays on every customer send.
- email in
- work out
- human approval
- governed autonomy
Attention where it counts
We save your attention.
InboxOS separates noise from the signals and actions that need you, matched to your level in the organisation. Priority goes to moments that affect customers, risk and service levels.
Noise falls back
Spam, promotions, clutter
Duplicates, newsletters, spam, irrelevant promotions and automated notifications stay out of the work queue that needs a person.
Customer signals rise
What actually needs action
Customs holds, missing documents, customer dissatisfaction, SLA risk, blocked approvals, escalations and silence where action was expected.
By your level
The right lens for each role
- Operators see action required, waiting work and what is due soon.
- Supervisors see escalations, SLA risk and unassigned work.
- Leaders see exceptions, approvals and customer risk at a glance.
The product
See the work
as the queue sees it.
Real views from the current offline demo on sample logistics records. A private walkthrough shows the queue, ticket and review path on sample data.
Product demo · about 95 seconds
Walkthrough of the offline demo on sample logistics records.
See what needs attention
One queue, already sorted.
Customer signals rise. Noise falls back. Priority and risk come from pack rules, tone and follow-up, so the team starts with context.
- SignalWhat · urgency · care
- StatusReview state visible
- TeamShared freight work
Open the work
Context gathered. Draft waiting.
Fields, gaps and a ready-to-review reply sit together so judgment goes where it matters.
- GapsFlagged with evidence
- DraftReady to approve
- SendHuman gate always
Explain what happened
A path you can look back on.
When operations, auditors or a handover asks why, the record is already there.
- HistoryStep by step
- ChecksTraining · audit
- TrustShow the path
What changes
A better day
for the team.
Faster first attention, clearer ownership and governed replies. Outcomes the team can feel.
We save your attention
Noise and promotions fall back. Customer signals and the actions that need you rise first, by role, so judgment starts on work that moves customers and risk.
Urgent exceptions stop hiding
Priority rises from pack rules, tone and urgency, and follow-up signals. High-impact work surfaces while there is still time to act.
Replies are ready when your people are
Drafts wait for a person to decide. You keep speed without giving up authority.
You can always explain what happened
Clear history for operations, checks and handovers. Trust grows when you can look back and show the path.
Also in the product: one queue for bookings, quotes, holds, updates and invoice questions · words freight teams already use · a private sample demo before any real inbox.
Why InboxOS
Built for finished
work.
Others help you write faster. InboxOS helps the organisation complete the job the message represents, with your people still in charge.
AI email responders
Usual fit
Fast drafts from a prompt or a short summary of the thread.
InboxOS
Clear work: what the email is about, what is missing, how urgent it is, and a draft waiting for a person to approve.
Outlook or Gmail with AI
Usual fit
Personal help inside the inbox you already use every day.
InboxOS
A work queue that sits beside Outlook or Gmail. Urgent holds rise as owned work with priority, risk and review state.
Shared inbox tools
Usual fit
Team sorting of conversations and who owns the reply.
InboxOS
Words freight teams already use, time-critical holds, and a path you can look back on when someone asks why.
Build-it-yourself automation
Usual fit
Connecting tools with rules someone has to build and keep running.
InboxOS
It already understands freight work, with people still in the path when commitment is made.
Buyer’s field guide
Four tools. Four different jobs.
Use the category that matches the work you need to change. InboxOS is for operational email that must become owned, reviewable work.
| What matters | Shared inbox | Helpdesk | Chatbot / agent | InboxOS |
|---|---|---|---|---|
| Primary job | Assign conversations | Manage support tickets | Answer or draft | Finish operational work |
| Understands freight work | Manual setup | Generic taxonomy | Prompt dependent | Built into the workflow |
| Missing fields + risk | Team checks | Rules and forms | Varies by prompt | Surfaced with the ticket |
| Approval before send | Possible | Possible | Not the control plane | Required by design |
| Reconstructable path | Conversation history | Ticket history | Model transcript | Work + review trail |
They help you write faster. We help your team finish the job with control still in your hands.
Trust
Where your data stays.
Who stays in control.
You choose the eligible workflows, autonomy thresholds and review boundaries. Routine low-risk work may auto-advance; uncertain, high-impact and outbound actions stay visibly under human control.
Questions buyers ask first
Clear answers before a security call.
Can we choose how much is automated?
Yes. You set the autonomy dial. Choose which workflows are eligible and set the confidence and risk thresholds. Routine low-risk work may auto-advance; uncertain and high-impact work stays in human review. Autonomous Queue is optional and can be switched off where regional policy or your preference requires it.
Can Autonomous Queue be switched off?
Yes. If regional policy does not allow autonomous advancement, or your organisation prefers fully human-reviewed progression, Autonomous Queue can be disabled. Classification, extraction, drafting and human approval before send remain available.
How hard is it to start, and can we change the rules later?
Start light, then grow on the same core. Discovery begins with a past-mail sample you choose; your live inbox password stays with you and there is no hard cutover of the tools your team already uses. Your industry pack carries how work is judged. As evidence builds, we refine those rules with you and open more workflow types without replacing InboxOS.
What is the default Autonomous Queue rule?
Confidence at least 7 and low intent risk. That is the shipping default for work that may advance without manual handling. You can tighten or open those thresholds, or switch Autonomous Queue off. Autonomous means internal routing, not unsupervised customer send.
How does priority get decided?
From pack rules plus live signals. Priority rises when the industry pack marks the request as high priority, when tone and urgency look strained, or when the thread looks like a follow-up. Separately, intent risk comes from the pack rules for that request type.
Will AI write to customers without us?
Human approval is required. A person must approve every reply that reaches a customer before it sends.
Will our mail sit with other companies?
One organisation, one setup. Your deployment stays dedicated to your company.
Do we hand over the live inbox to see it?
Sample first, then your history. The private demo uses offline sample mail for invited people. Discovery uses a past-mail sample you choose, while your live password stays with you.
Can we explain what the system did?
Yes. Work leaves a step-by-step trail operations and auditors can follow when someone asks why.
Who can approve and send?
Your people. Review stays under roles you control. Help moves work forward; authority stays with your team.
Do you claim SOC 2 or ISO already?
Contract-specific claims. The Security Overview states current posture. SOC 2 or ISO appear only when a contract includes them.
Where data stays
Your organisation.
Your own setup.
- Single tenantOne setup per organisation
- Your placeInbox and history you control
- Private demoSample data · invited only
- DiscoveryPast sample · password stays yours
- SecurityContract-specific claims
Configurable autonomy
You decide how far
each workflow can go.
- WorkflowsYou choose eligibility
- OptionalAutonomous Queue can switch off
- PriorityPack · tone · follow-up
- RiskPack request rules
- SendUnder your authority
- Trace · rolesPath you can show
Autonomous Queue is optional and can be switched off where regional policy or your preference requires every item to stay in human review.
Need something to share with security or leadership? Open the public security overview Request the detailed pack
Documents
Share the detail
internally.
Security Overview first for most buyers, plus capability and executive packs for leadership. Ask with your demo note and we will send it.
Insights
Notes for operators who still live in email.
Practical reading on freight teams, governed automation and honest capacity sizing. Share with IT and finance when the conversation gets serious.
Why freight operations still run on email
Treat the inbox as intake, not the system of record.
ReadHuman-in-the-loop email automation for logistics teams
Why approval before send is the control plane.
ReadFrom inbox to work queue: digitising freight operations
What real digitisation changes on day one.
ReadWhat enterprise email automation should mean
A buyer checklist that survives internal review.
ReadSizing capacity without fake ROI
Ranges and assumptions instead of one invented percentage.
ReadBuilt for freight
Ocean, air and road.
The lanes your teams already run.
Container yards, uplift windows and the long haul on asphalt. InboxOS is built for the inbound mail that moves work across these modes.
- Ocean
- Air
- Road
Scroll · the lanes open
Who we serve
We are building with
logistics teams first.
Right now our focus is freight and logistics: bookings, quotes, customs holds, status updates and invoice questions. That is the operation we are designing for and demonstrating today.
If you run operations in wealth management, hotels, insurance, or another email-heavy operation, we still want to hear from you. Reach out. Tell us your inbox. We will say honestly whether InboxOS is a fit now or later.
Register interest in your industryFrom the founder
Built for trust
at the moment of action.
AI that writes is becoming common. Trusted action is still rare. InboxOS exists so freight teams can move faster without giving up the judgment that protects customers and the company.
Banking data
Turning complex information into decisions.
Large-scale customer and transaction work made one lesson clear: intelligence matters only when people can act on it responsibly.
Enterprise controls
Working where evidence and accountability matter.
Banking, compliance and consulting shaped the insistence on approval boundaries, traceability and explainable operations.
AI systems
Designing for trusted execution, not novelty.
InboxOS brings workflow intelligence, agent orchestration and human judgment together at the moment work moves.
- your dial
- your sample
- your trail
- your send
Begin
A clear path.
Evidence at every step.
We size the work from your mail and your labour costs. Then you prove one workflow, choose its autonomy and review boundaries, and expand only when the evidence and your team are ready.
What we use
A sample of your past email
What is actually in the inbox: how much mail, what kinds, and the work that matters.
Your labour costs
Time and labour numbers from operations and finance. You bring the numbers.
What you get
A labour range, plus an operating case
Hours you can size from labour inputs, framed next to visibility, control, exception handling and auditability. Discovery grounds the labour slice in your sample.
How you buy
-
01
See InboxOS
This page and a private sample demo.
Your data Offline sample walkthrough on demo records.
-
02
Discovery
Easy to begin: a past-mail sample you choose. No hard cutover. Capacity sized from your composition and labour costs.
Your data Historical sample you choose. Live password stays with you.
-
03
Pilot
One type of work, locked for the trial. Review boundaries stay under your control.
Your data Real inbox you allow, after a safe test first.
-
04
Annual
Ongoing use when the team is ready.
Your data Your own private setup we run for you, or in your cloud when you are ready for production.
Discovery sizes the labour range on your sample. InboxOS measures recovered capacity in live use. Service, risk and control outcomes are judged in pilot evidence. Fees follow that conversation.
One measurable slice
Labour hours are the easy number. The operating case is larger.
Use the calculator for released capacity only. The fuller return is digitising inbound work into a governed operating rhythm: visibility, control, speed on exceptions and a path you can defend.
Labour proxy
Three buckets
Conservative to upside
Grade C until Discovery
01
Your team
Team, volume and handle time
02
Work mix
How much mail is real work
- 55% Actionable
- 27% Awareness
- 18% Noise
03
Landed cost
Loaded ops hour for your geography
Out
What you could get back
Conservative to upside on your inputs
Today
-
-
Released / month
-
- h / year
Expected labour capacity released
- FTE
A labour proxy from your inputs. It does not price risk avoided, service lift or operating control.
Annual labour value of that capacity
-
Before platform fees. One cost lens only: avoided hiring, overtime, contractors or room for higher throughput.
First step
Start with a private demo.
Private sample demo on logistics mail, offline. Name your industry in the form if you are outside freight.
- Review boundaries you choose
- Your company alone on the system
- Commercial terms when you are ready
Demo access
Tell us about your operation.
Your request is ready.
We copied the details to your clipboard. Send them to the AutonomeX team, or open your email app below.