What we need from your side
| Service Layer | Its URL and a user for the companies it should read; the writer user for the company it may post to. |
|---|---|
| Read-only SQL login | For reports: a login with db_datareader on the company database, on SQL Server. Never an administrative login. Without it, the report path simply does not exist and nothing mentions it. |
| A test company | Writes are developed and tested against a copy. The production company is a setting we switch together when you are ready. |
| PIN field | For customers by phone or chat: a user-defined field on business partners, alphanumeric, 4 to 8 characters, set by your admin in SAP. |
| An allow-list of addresses the assistant may send to, for emailing quotes and orders and for the support mailbox. |
How it runs
- One container on a machine inside your network, with one data volume for records, taught facts and saved patterns.
- Outbound only: to the Service Layer, to the database, and to the AI API.
- Staff reach the chat and admin pages over HTTPS with their own login. Customers reach the customer chat page, or call a BE Voice number.
Company-specific knowledge
Each deployment carries a company module: the words your business uses, the warehouses and bin conventions, the documents that matter, pictures of items if you have them. It is written with you during setup and grows through teaching.
Going live
- Connect read-only. Staff ask questions against live data for a week; nothing can change.
- Switch writes on against the test company. Quotes and orders get raised and confirmed there.
- When you are satisfied, point the writer at the production company. Rights per role stay as agreed.