Orders from phone calls and messaging apps
A staff member dictates or pastes the customer's message, and the assistant recognises the parts, checks stock and the customer in Streamsoft and drafts the order. A person only approves it.
ERP integration
Streamsoft, a Polish ERP used by many distributors and manufacturers, holds your stock, customers and invoices. But orders arrive by phone and on WhatsApp, end up in Excel, and then someone retypes them into the system. We build an AI layer that connects the two.
We don't build a second ERP next to Streamsoft, and we don't duplicate stock or invoices. Streamsoft remains the source of truth for the warehouse, customers and accounting. We add what it lacks: taking orders from messaging apps, keeping track of deadlines, deposits, returns, and an assistant that answers the team's questions about the data. Everything is read live from Streamsoft.
Choose where the order comes from and see how the assistant recognises the items, checks the customer and stock in Streamsoft and drafts a pro forma you approve with one click. Sample data.
Hi, 2x brake caliper, same as last time. Ship with DPD please.
The assistant is drafting…
Items recognised
Customer in Streamsoft
Live warehouse stock
Pro forma draft
The assistant never issues anything on its own. It recognises the items, checks the data in Streamsoft and drafts the document, which is only created after a person clicks.
A staff member dictates or pastes the customer's message, and the assistant recognises the parts, checks stock and the customer in Streamsoft and drafts the order. A person only approves it.
Is the part in the warehouse, what did it cost last time, has the customer paid. The answer comes from Streamsoft's data, not from an employee's memory or an outdated spreadsheet.
Unpaid pro formas, stalled orders, cores to be returned, returns without a decision. The system reminds the right person before anything goes overdue.
Every order and return has its stage, visible to everyone. No more asking in the corridor what's happening with a customer's parcel.
A trading company in the automotive sector selling truck parts, a team of a few people, Streamsoft Pro as the ERP. The client's name stays with us.
Most orders came in by phone and on WhatsApp. They went into Excel, shipments were tracked on a Trello board, and data was retyped into Streamsoft by hand. Knowing what was happening with an order lived in the heads of two people.
An AI operating system for the whole company. An assistant in the messaging app takes orders and returns, reads Streamsoft live (stock, customers and documents for both companies in the group), moves each order through 11 stages from pro forma through shipment to deposit refund, and automations watch deadlines and send reminders. The team works from one board instead of Excel and Trello.
We started with a map of the whole company's processes: 38 processes in 8 areas, half of which existed only in people's heads. Every rule, for example when a pro forma lapses or who pays for shipping on a return, was agreed with the team in writing before it went into the system.
We integrate with Streamsoft Pro and Prestiż, including companies where the system runs on a single office computer. The connection is secure, doesn't expose your data to the internet and doesn't change how your accounting team works. At the start the assistant only reads data. Writing to Streamsoft, for example customer orders, is introduced in stages, agreed with your Streamsoft service partner.
When a company has an ERP and still lives in Excel, it's a sign the ERP doesn't cover part of the process: taking orders from messaging apps, deposits, returns, or simply keeping track of who has to do what. We build that part as a separate layer that reads Streamsoft rather than copying it. That way there are never two versions of the truth.
Invoices and submission to KSeF, Poland's national e-invoicing system, stay in Streamsoft, because that's where the accounting is and where they belong. Our layer looks after the process around the invoice: has the pro forma been paid, has the invoice gone out, has the customer received the documents.
The cost depends on the number of companies and databases, whether reading is enough or writing to Streamsoft is needed, and how many processes you start with. We usually begin with one process, typically order intake, and extend the system in stages. You receive a written quote after the audit.
Yes. We integrate with Streamsoft Pro and Prestiż: live data reading, and document writing agreed with your service partner. We check your version and configuration during the audit.
For reading alone, usually not. When writing to Streamsoft, for example customer orders, we agree the configuration with your partner or service provider so documents enter the system the way the vendor intends.
At the start the assistant has read-only access, so it simply can't. Anything that should go into Streamsoft is first created as a draft for a person to approve. Prices and amounts are calculated by code from the system's data, not by the language model.
During the rollout we set up automatic backups of our layer's data and check that the Streamsoft database has its own. Surprisingly often it turns out it doesn't, and that's the first thing to fix before we build anything else.
As little as possible. Orders are taken in the messaging app they already use, and the order board looks like a spreadsheet or a Kanban board. Team training is part of the rollout.
Yes. In the rollout described above, the assistant reads the databases of both companies, and a person decides which company an order goes to.
A 65-minute call. We walk through how orders flow today, where data is retyped by hand and what can be safely read from Streamsoft. You leave with a plan and a written quote.
Book a consultation