Order entry: two minutes, still checked
Avant Tecno makes compact loaders in Finland, with about 435 staff. Customer orders arrived as email and PDF files, each in the customer's own layout, and staff keyed them by hand. Supplier confirmations got the same hand treatment. The firm built two agents. One reads a customer order into the ERP. One reads a supplier confirmation. The model proposes the fields, fixed rules decide price, date and quantity, and a field the agent is unsure of stays blank, not a guess.
Start with one job only. Fill in the three lines. Keep the bot on that job.
The one job this bot does: ______________________________
What it may do on its own: ______________________________
What it must ask me first: ______________________________
Two lines from this case, side by side. No new figures.
Avant Tecno makes compact loaders in Finland, with about 435 staff. Customer orders arrived as email and PDF files, each in the customer's own layout, and staff keyed them by hand. Supplier confirmations got the same hand treatment. The firm built two agents. One reads a customer order into the ERP. One reads a supplier confirmation. The model proposes the fields, fixed rules decide price, date and quantity, and a field the agent is unsure of stays blank, not a guess.
Order entry now takes two minutes, check included. The firm reports up to 80% efficiency gain on customer-order processing. No before-time is given, so the two minutes has no baseline, and the 80% is the company's own public figure. No order enters the ERP without an expert check.
The after line is the source's claim, not our measurement.
smalloffice.space · Get a case like this in your inbox each morning. Subscribe free
Read this case on your phone now, and keep it for later. Type your email. We send this case to that address, and you get the next cases each morning too.