Role
Automate dispatch and scheduling.
Dispatch turns demand, stock, dates and capacity into the next step: replenish, schedule, or place a change on the right job. The details arrive by email, in spreadsheets and from the ERP, and they change along the way. An AI coworker collects them and prepares a proposal your team can check. Capacity, purchasing and release of the plan stay with your team.
Book a demoAt the desk
What the AI coworker takes on in this role.
Collect demand
It reads the agreed mailboxes, spreadsheets and order changes. Item, quantity, date and reference are brought into one form. A change without a clear reference stays open, with the message beside it. It is not attached to a job only because the sender is known.
Set stock beside it
Demand is placed beside stock and beside open purchases, where you allow those extracts for dispatch. The coworker calculates only with values that are in the source. It does not fill in a missing stock figure, and it does not present an old extract as the stock position of today.
Prepare replenishment
When stock falls through the rule you set, it prepares the purchase proposal: item, quantity, supplier, and the link to the order or to the reorder point. The purchase is sent only after a person in purchasing or dispatch releases it.
Prepare the schedule
For transport and allocation it assembles times, places and references into a plan that can be checked. A gap, such as a missing time window or an unclear place, stays visible as an open question. It does not commit the job, and it does not move a route on its own.
Place a change
A new time, a different quantity or a changed place is matched to the existing case when the reference holds. Uncertain matches are not rebooked in silence. Dispatch or inside sales receives the case with the source and with the previous state.
Hold the exception
A conflict between email, spreadsheet and ERP, or a rule that requires approval, stops the case. The coworker names which details collide. The decision on capacity, purchasing and the plan belongs to your team, not to the prepared proposal.
Inside the ERP you already run
Dispatch reads the order and the stock from the ERP and files the agreed proposal back there. That applies to Abacus, Opacc, Bexio and SAP Business One, in the scope the system and the permissions allow. An interface, a file or a tightly bounded pass through the screens is settled before the start, including login and two-factor authentication where you use it. There is no promise for every scheduling screen. If dispatch sits in Microsoft Dynamics, access is checked the same way. The ERP stays the system of record.
Data handling
Orders, the stock extracts you allow, purchase proposals and the emails that carry a change. The Robotjoy runtime is isolated for each company and operated in Switzerland. For dispatch we record which data moves where. Your data stays exportable.
Clear boundaries
Capacity, sending a purchase, promising a date, and any change that affects a route or a customer, stay with your team. Preparing a proposal is not the same as releasing it. Changes that affect capacity, or that you treat as safety-relevant, do not proceed without the agreed approval.
Questions from the work
Short answers.
What does an AI coworker prepare in dispatch?
It collects demand from email and spreadsheets, places it beside stock and open purchases, and prepares replenishment and the schedule as a proposal your team can check.
Does it release purchases and jobs?
No. Purchasing, capacity and release of the plan stay with your team. Preparing a proposal is not the same as sending it or promising a date.
How does it treat a change with no reference?
The change stays open, with the message beside it. It is not attached to a job only because the sender is known. A person places it.
Does dispatch work in the existing ERP?
Yes. Order and stock come from Abacus, Opacc, Bexio or SAP Business One, within the permissions. The proposal is filed back there. There is no promise for every scheduling screen.
What happens when the details conflict?
The case stops. The coworker names which details from email, spreadsheet and ERP collide. Your team decides on capacity and on the plan.