The loop
A staff member types a question or an instruction in the chat, or a customer asks by phone or in the customer chat. The model sees the conversation so far, the facts your team has taught it, and the tools this person's role allows. It calls tools until it can answer, or until it has a draft to show. Reads run freely. Anything that would change SAP comes back as a preview with every value filled in, and a Confirm button.
Pressing Confirm runs our posting code directly. The model is not involved in that step and cannot post on its own.
What it can do today
| Ask | Any question about customers, items, stock, orders, deliveries, invoices and payments. Totals and reports run as one read-only SQL query; single documents come from the Service Layer. |
|---|---|
| Create | Sales quotations, quotes copied from earlier quotes (for another customer, or with prices adjusted), and sales orders from an open quote. |
| Change | Close or cancel quotes and orders with a reason, move stock between bins or warehouses, email a quote or order, and edit a record's fields where an admin has allowed that object. |
| Beyond SAP | Other MCP servers and APIs an admin connects: a carrier's tracking, a CRM, a web shop, another BE product. The assistant reads them in the same conversation and puts the answer beside the SAP data. |
| Remember | Teach it a fact about the business and every later chat knows it. Log anything it could not do for the team to look at. |
Where it answers
- Staff chat, with a login and a role that sets which tools are available.
- Customer chat, after the customer verifies with their account number and PIN.
- Phone, through BE Voice: callers verify the same way and the answers are scoped to their account.
What never happens
- Nothing is posted to SAP without a person pressing Confirm.
- Generated code can only read. Writes go through fixed, tested actions whose parameters the model fills in and code validates.
- A customer or caller only ever sees their own account. The PIN is checked against SAP and never stored.
- Payments, credit memos, deletions and anything outside the allowed objects are out of reach by design.
Note. Development and testing run against a copy of your company database. Going live against the production company is a switch your administrator and we agree on, not a default.