Three agents for the places where SAP meets a human being: the phone that rings about an order, the mailbox full of customer POs, and the question finance needs answered before the meeting. No connector project. No basis window.
SAP holds the data and posts the document. Everything around it — answering the customer, retyping the order, finding the number — is still done by hand. That is where these agents work.
Answers the calls that exist only because a customer cannot see your SAP: where is my order, when does it ship, is that part in stock, I need to raise a warranty claim. It picks up on the first ring, in the caller's language.
Customers order by email, in their format, with the PO as a PDF. The agent reads it, validates it against your master data, creates the sales order and replies in the same thread. What fails a check is held, never guessed.
Point it at the folder of exports your team already downloads. Ask in plain language. Get the number, the chart and the file it came from — or an honest refusal when the data cannot answer it.
These are live demos. Each one runs in your browser, takes about a minute, and answers the way it would answer your customer.
The single most common inbound call at a B2B manufacturer. Order number in, current stage and realistic date out.
Hear this demo →
Part number, machine serial or a description of the broken thing. It identifies the part, confirms availability and takes the order.
Hear this demo →
First-touch intake with the serial, the fault and the photos requested on the spot, so the claim arrives complete instead of half-filled.
Hear this demo →
Takes the breakdown call, captures the asset and symptom, and routes to the right engineer with the context already written down.
Hear this demo →
A dealer in Coimbatore and a buyer in Ludhiana get the same agent, each in their own language, switching mid-call when they do.
Hear this demo →
Each call leaves a structured record: who called, what they asked, what was promised, what needs a human. Your team reads outcomes, not recordings.
Most AI for SAP stalls in the same meeting: basis says no live connection this quarter. So the agents are built to earn their keep without one, and to get better when you grant one.
Scheduled exports into a folder. Nothing is installed in SAP, nothing changes, no transport is needed. Most pilots never go further than this.
An OData or RFC endpoint, or whatever your middleware already exposes, gives the agent live status instead of this morning's picture.
Creating a sales order is the one write most teams want. It stays behind validation, and anything that fails is held for a person.
Every query path is read-only, row-capped and killed on timeout. A badly phrased question cannot touch your data or your bill.
The agents attach to a mailbox, a file drop or a service. That is why the release you are on does not decide whether this works.
Still the reality in most plants. Exports and RFC both work, and nothing here pushes you toward a migration you had not planned.
On-premise or private cloud. Where OData services are already published, the agents use them and answers get fresher.
Smaller landscapes get the same three agents without the enterprise programme around them.
Can an AI voice agent really work with SAP?
Yes. It answers the call and reads or writes through the access your landscape allows: a service, middleware, or a scheduled export. The caller gets an answer either way.
Do we need an integration project first?
No. Reporting runs on exports, order entry runs on the mailbox. A live connection is an upgrade, not a prerequisite.
ECC or S/4HANA?
Both, and Business One. The integration point is a service, a mailbox or a file, never a screen, so the release does not matter.
Which processes are covered?
Order entry from customer POs, order status and ETA, spare parts, warranty intake, and questions on FI, SD and MM reporting data.
How do you stop it inventing a number?
The copilot never writes its own SQL; it fills a spec of metrics that exist in your catalog, so an unmapped question is refused. The order agent holds anything that fails validation.
How fast is a pilot?
Weeks, not quarters. Send one folder of exports or five real purchase orders, and the first working version comes back on your own data.
Pick the one that costs you the most people: the order mailbox, the status calls, or the report nobody has time to build. A pilot runs on your own data, not a slide.