Receiving the order
Every e-mail in the Microsoft 365 orders mailbox is recorded in the log. The agent separates orders from other e-mails, takes the text and attachments (PDFs, Excel files, photos) and starts processing without anyone stepping in.
Customer orders arrive in Outlook as e-mails, PDFs and Excel attachments in different formats, and a sales rep retypes each one into Business Central, SAP Business One or Monitor ERP by hand. The agent extracts codes, quantities and deadlines, checks them against the price list and contract and creates a draft order in the ERP, which the sales rep approves with one click.
Built for ISO 27001NIS2 DORA
In a manufacturing company, a sales rep's day starts in the orders mailbox in Outlook: one customer writes free text, another attaches their own purchase order PDF with their own codes, a third sends an Excel sheet whose columns differ every time. The rep opens each one, finds your item code in the Business Central, SAP Business One or Monitor ERP item list from the customer's code, checks the price against the contract, keys the sales order into the ERP and only then can answer about the delivery date. At peak times this runs until evening, and a mistake in a quantity or code is noticed only in production or the warehouse, when fixing it is already expensive.
We implement a Claude agent through the API with an integration into your ERP. The agent watches the orders mailbox in Microsoft 365 and extracts item codes, quantities, requested date, delivery address and terms from the e-mail text, PDFs and Excel attachments. It matches customer codes to your item list in Business Central or SAP Business One using previously approved mappings, checks prices against the customer contract and the valid price list in the ERP, and quantities against minimum lot sizes and packaging. Then it creates a draft sales order in the ERP with the status "awaiting approval" and flags the open points: an unknown code, a price that does not match the contract, a date shorter than your production cycle. The sales rep sees the prepared order in Business Central, SAP Business One or Monitor ERP with the flagged spots and a link to the original e-mail, corrects it if needed and approves it with one click, and the customer receives a confirmation with the date within the same hour. The agent never approves orders on its own and never writes to the customer without a person's approval. The model runs on the Anthropic API or Amazon Bedrock in an EU region, your price lists and contracts are not used to train the model, and every order and its source are kept in a log.
Four steps from input to a record in your system, with human approval wherever there is risk.
Every e-mail in the Microsoft 365 orders mailbox is recorded in the log. The agent separates orders from other e-mails, takes the text and attachments (PDFs, Excel files, photos) and starts processing without anyone stepping in.
Claude extracts the line items, matches customer codes to your item list in Business Central, SAP Business One or Monitor ERP, prices to the customer contract and the ERP price list, quantities to packaging and minimum lot sizes, and the date to the production cycle. Every mismatch is flagged on the specific line.
The agent creates a draft sales order in Business Central, SAP Business One or Monitor ERP with the status "awaiting approval", the flagged spots and a link to the original e-mail. The sales rep checks, corrects and approves it, and then the confirmation with the date goes to the customer. Without approval, the order does not reach production.
When the sales rep approves a new customer code mapping, it is saved for later orders and, if you want, written to the customer item code table in the ERP. Every week we review the e-mails that were not recognised and adapt the agent to new customer formats.
Draft sales orders created in Business Central, SAP Business One or Monitor ERP, reading customer, item list and contract data through the API or import files, adapted to your version.
A database of mappings between customer item codes and your ERP item list, which fills up from the sales rep's approvals.
The prepared order in the ERP with the status "awaiting approval", flagged open points, the original Outlook e-mail and one-click approval, after which the confirmation goes out to the customer.
The path of every order from e-mail to ERP record, and our support when customers change formats, Business Central is updated to a new version or new customers appear.
A Claude agent through the API + an Outlook mailbox in your Microsoft 365 tenant + a Business Central, SAP Business One or Monitor ERP integration. We connect through the ERP API, import files or a staging table, depending on your version. See the service page for details and limits.
We connect Business Central through its API and Power Automate connectors, SAP Business One through its API or import files, depending on the version, and Monitor ERP through its API or an import, according to your implementation partner's setup. Any other ERP, international or local, we connect through an API, a file export or an e-mail flow. We choose the integration method after a check in the first conversation, and we do not claim an official partnership with these vendors.
It suggests the closest match from the ERP item list based on the name and earlier orders, but flags the line for checking. The sales rep approves or corrects it in the Business Central or SAP Business One draft, and the mapping is saved for next time.
The confirmation to the customer is sent by your ERP or by the sales rep from Outlook after approval, as before. If you like, we can add a note about automated processing, but what the customer sees is a faster confirmation.
An operator looks for the process sheet in a SharePoint folder by the machine, or asks the foreman, who gives the same answer for the tenth time…
Every material shipment arrives with an invoice, a delivery note and a declaration of conformity, the purchase order sits in Business Central, SAP…
Maintenance logs are kept in SharePoint or Excel, and Teltonika and PLC counters track operating hours, but nobody reads them until a machine stops.
Nonconformance reports arrive from Microsoft Forms, shift logs and e-mails, and the quality manager retypes them into Excel to see trends.
This service is delivered by specialists with valid international certifications. Their expertise is confirmed by independent organisations, not by us.
AI systems are deployed with protection against data leakage and model abuse.
The AI security programme and its controls are managed following the ISACA methodology.
AI risks are identified and managed like any other IT risk.
We reply within 1 business day