Our own product — pilot programAI sales order automation
Complexity level: MediumReplaces: Someone in sales or operations manually types every order that arrives by email, PDF, Excel, or WhatsApp, checking customer, items, prices, and availability before creating it in the ERP.
The AI: Extracts the order data (customer, items, quantities, prices) with evidence for where each field came from, and validates it deterministically against the ERP’s master data: customer, SKU, price, credit limit, and stock.
Human control: Orders that pass validation are created in the ERP; the ones that do not fall into an exceptions inbox for human review, with a full audit trail of each decision during the pilot program.
Data needed: Historical example orders (email, PDF, Excel, WhatsApp) and read access to the ERP’s master data (customers, SKUs, prices, credit, stock).
Integrates with: Email, WhatsApp, spreadsheets, and the ERP.
Related terms: Agentic AI
See pilot details
Classification of claims and request documents
Complexity level: MediumReplaces: An analyst opens each claim or request, reads the attached document, and manually decides the case type and which queue it belongs to.
The AI: Classifies the document by claim or request type and extracts the relevant data to pre-fill the case file.
Human control: The assigned analyst confirms the classification and makes the final decision on the case; the model never approves or rejects a claim.
Data needed: Already-classified claims or requests as examples and the process’s current categories.
Integrates with: Case or policy management system, email, and document repository.
Related terms: SLM
Anomaly alerts on inventory and cold-chain sensor data
Complexity level: HighReplaces: The team periodically checks reports or dashboards to notice if something went out of range (temperature, stock, consumption), sometimes too late.
The AI: Monitors inventory or sensor readings and generates an alert when a value falls outside the expected range, with the relevant context.
Human control: The alert reaches a responsible person who decides the action; the system does not intervene physically or close the case on its own.
Data needed: Historical series of the relevant readings and the process’s normal ranges or thresholds.
Integrates with: IoT sensors or a monitoring system, inventory/ERP, and an alert channel (email, WhatsApp, Slack).
Drafting responses for approval in back-office
Complexity level: MediumReplaces: Drafting every response to a customer or third party (status update, request, collections communication) takes time even though the content is similar each time.
The AI: Drafts a reply based on the case and the current template, using the data from the corresponding file.
Human control: No response goes out without a person reviewing it, editing it if needed, and approving it.
Data needed: Current response templates and the case or file data.
Integrates with: Case management system, email, and CRM.