Agent cost keeps growing with volume
Every order line is typed by a person, so cost rises with every new customer and every new order.
For example: ~250 hours a month · 5,000 orders × 3 minutes of manual capture
Stop typing orders. Start fulfilling them.
Every order email, in your ERP and confirmed in under a minute. Consnet AI reads every order your team receives, whether it is a PDF purchase order, a line in the email body or a photo of a handwritten list. It checks the order against your ERP data, validates the prices and creates the sales order. Your agents only handle the exceptions.
Example order feedorders@ mailbox · today
- PDF · PO 7781204 · Highveld Build Supply · 5 lines · Order 4500182211 · Created
- IMG · Handwritten list · Rustenburg Hardware · 8 lines · Order 4500182212 · Created
- TXT · “Please send 40 bags…” · J. Naidoo (rep) · 3 lines · Order 4500182213 · Created
- PDF · PO 7781207 · Highveld Build Supply · 11 lines · Order 4500182214 · Created
- PDF · PO 33-0912 · Coastal Interiors · Line 20 price differs · Price query
- XLS · Weekly order · Vaal Ceilings · 6 lines · Order 4500182215 · Created
- PDF · PO 90412 · Polokwane Timber · 9 lines · Order 4500182216 · Created
- TXT · Repeat order · Garden Route Build · 4 lines · Order 4500182217 · Created
- PDF · PO 2026-1187 · Free State Roofing · 12 lines · Order 4500182218 · Created
- TXT · Statement request · Karoo Builders · Not an order · Agent inbox
- IMG · Photo of order · East Rand Paints · 7 lines · Order 4500182219 · Created
- PDF · PO 66120 · Durban Drywall Co. · 10 lines · Order 4500182220 · Created
- PDF · PO 55821 · Mpumalanga Drywall · Ship-to not found · With agent
Example figures
- Created automatically
- 231
- Sent to an agent
- 15
- Email to confirmation
- < 1 min
Thousands of order emails a day, typed in by hand.
Orders arrive from customers and sales reps in every format. Most organisations run a contact centre that re-keys each one into the ERP, and every order must be captured accurately before the cut-off.
Capture errors reach your customers
An average order has multiple lines. A wrong material, quantity or price flows straight into delivery and invoicing.
Morning peaks miss the cut-off
Orders queue up when volumes spike, and late orders move to the next delivery run.
For example: Cut-off 12:00 · two orders slip a delivery day
Customers wait for a confirmation
Slow confirmations lead to follow-up calls and emails, which add even more work for the same team.
Pick an email and watch it become an order.
These five sample emails cover the main paths: a clean PDF, a handwritten list, a price mismatch, missing information and a query that isn't an order. Choose one and press Process email.
Order mailbox5 new
Scenario: Clean PDF purchase order
Incoming email
From Highveld Build Supply <procurement@highveldbuild.example>Subject Purchase Order 7781204
Good morning, Please find our PO attached for delivery to the Midrand branch. Regards, Thandi
| Ln | Product | Qty | Unit price |
|---|---|---|---|
| 10 | Gypsum board 12mm 1200×2700 | 120 | R142.80 |
| 20 | Ceiling tile 600×600 white | 400 | R41.20 |
| 30 | Drywall screws 25mm (1000) | 15 | R219.00 |
| 40 | Jointing compound 20kg | 30 | R268.50 |
| 50 | Corner bead 3m | 80 | R34.90 |
Attachment: PO_7781204.pdf
Automation pipeline
- ReceivePicked up by the mail pollerWaiting
- ClassifyIs this an order request?Waiting
- ReadExtract order detailsWaiting
- CheckMandatory fields presentWaiting
- MatchCustomer and products in your ERPWaiting
- Simulate + price checkERP prices vs PO pricesWaiting
- Create orderSales order in your ERPWaiting
- ConfirmReply to the customerWaiting
Press Process email to run this email through the pipeline.
Connects to any ERP system.
Your mailboxes stay in Microsoft 365 and the AI runs in your AWS account. Orders are created in your ERP through its standard order interfaces, whether it runs in the cloud or on-premise. Exceptions go to the agents you already have.
Customer
- Email + POPDF, body text, image
- Order confirmationReply in the same thread
- Price queryLists the lines to correct
Microsoft 365
- Order mailboxesOne or many shared inboxes
- Mailbox connectorPicks up new emails as they arrive
Consnet AI on AWS
- Email classifierOrder request or not
- AI extractionRead and map to the order structure
- Reference-data matchingCustomers, products, units
- Price validationERP prices vs PO prices
- Order logOutcome recorded on every order
ERP and agents
- Your ERP systemSimulate first, then create
- Agent inboxContact Centre solution
- Microsoft 365
- AWS
- Secure link
- Your ERP
Data stays in your tenant and your AWS account.
Prices are checked before any order reaches your ERP.
Automation should never create an order your customer did not agree to. Each order is priced in your ERP first, and every line is compared with the customer's PO.
When prices differ, the customer is asked first
The order is not created. A draft email lists the lines that do not match, ready to send in the customer's thread. When the corrected PO comes back, it runs through the pipeline again.
Tolerance rules per customer or product group. Outcome recorded on the order for reporting.
Exceptions go to an agent with the reason attached
When information is missing or unclear, such as an unknown ship-to or a product that matches three items, the order is routed to an agent by email. The agent replies and processing continues automatically.
Agents work in the tools they already use. Every case states the reason for the exception. Emails that aren't orders go straight to the agent inbox. Every outcome is logged, so recurring exceptions can be fixed.
Estimate the capture time you could release.
Move the sliders to match your operation. The figures are illustrative. A live pilot measures your real automation rate.
Gross annual value of released time
R540 000
- Hours released / month
- 450
- Gross value / month
- R45 000
- FTE capacity equivalent
- 2.6
- Order lines captured / month
- 100 000
Automated · 9 000 ordersAgent-handled · 1 000 orders
Illustrative only. These figures show released processing capacity, not a forecast of headcount reduction. Gross values exclude the cost of the solution. FTE assumes about 173 working hours per month.
Prove the automation rate on your live email first.
Phase 1 connects your live mailbox to a QA environment, so the automation rate is measured on real traffic. You make the go-live decision with that evidence in hand.
Phase 2 · optional
AI-led customer interaction. When an order needs clarification, AI can ask the customer directly and resolve the query before an agent is involved.
Integrations and formats
Email and agents
Microsoft 365, Outlook shared mailboxes, Power Automate, Contact Centre solution.
ERP
Any ERP system, cloud or on-premise. Standard order APIs, order simulation and a secure site-to-site link.
Order formats
PDF PO, email body, scanned image, handwriting, Excel attachment and rep forwards.
Common questions
Any ERP system. The solution creates orders through your ERP's standard order interfaces and uses your existing customer and product data, whether the ERP runs in the cloud or on-premise.
Ready to automate your order desk?
In a 30-minute demo we take you through the full flow, from order email to sales order in the ERP, including exceptions and price checks. We also cover rollout and a business case for your volumes.