Agents
What runs on its own, what it may never touch, and who can stop it.
2 of 2 agents are switched on, and 2 proposals are waiting for somebody to decide.
None of them writes on its own. Every one proposes, and a named person agrees it — that is the rule, not a setting, and it is why anything an agent touched carries “updated by Corto AI” and the name of whoever let it through.
Running today
2Each one serves somebody specific. What it may never write is part of what it is, not a permission somebody remembered to set.
Sales
Serves salespeople and their head
on1 waiting on a person
Logs what was said after a meeting, drafts the follow-up, and flags a deal that has gone quiet. The record stays current without anybody opening a CRM to type into it.
Operations
Serves coordinators, planners and delivery leads
on1 waiting on a person
Proposes a change to a promised date with the reason and who has to be told, and keeps the at-risk list honest. It never decides — it assembles the decision.
What ought to become one
4Patterns found in the conversations, in the order Anil put them. Each names the evidence it rests on, and where no hours can be claimed it says so rather than estimating.
You moved the transporter booking to the top. Nine people named it and you have heard it yourself. It is also the one that cannot be switched on yet.
- 1
Fill the transporter's booking form from the dispatch tracker
The same dispatch details are typed a second time into the transporter's own booking portal, every working day.
- How we know
- Named by 9 people across two functions as something that wastes time daily.
- Time saved
- Nothing records how often the form is filled or how long it takes, so no hours are claimed.
- How we would know it worked
- Bookings placed without a person re-typing them, as a share of bookings.
- 2
Send the nightly dispatch summary from the tracker
A summary is written by hand each evening from the dispatch tracker and sent to six people from the shared dispatch mailbox.
- How we know
- 61 sends in 63 working days, from dispatch@ to six people.
- Time saved
- 1.7 hours a week · Five sends a week — 61 in 63 working days — at the twenty minutes its writer says each one takes.
- How we would know it worked
- Sends that went out on time without a person writing them, and any evening the tracker and the summary disagree.
- Who approves
- The summary goes out only after the dispatch coordinator has released it, for the first month.
- 3
Record every enquiry as it lands
Enquiries arrive through the website form, the phone and the shared sales mailbox, and are written down nowhere.
- How we know
- One enquiry sent through the company's own contact form on 21 August was still unanswered four days later; no register exists to say how many others there were.
- Time saved
- This one does not save time. It creates a number that does not exist today — how many enquiries arrive, and how many become orders.
- How we would know it worked
- Enquiries recorded against enquiries known to have arrived, and the share answered within one working day.
- Who approves
- Nothing is answered automatically. The register captures; a person replies.
- 4
Assemble the GST filing pack before the date, not after it
The return is prepared at the last moment by one person, and has gone in late when the cash to pay it had not arrived.
- How we know
- Filing lateness is on the public record, month by month.
- Time saved
- The value here is the date being met, not the hours. How long the pack takes to assemble has never been measured.
- How we would know it worked
- Returns filed on or before the date, and the number of days between the pack being ready and the date.
- Who approves
- The pack is assembled and shown. Nothing is filed by Corto, ever.