One assistant per job, not one for everything
Instructions, connected folders and tools switched on one by one: the assistant knows what it may do, and on what.
Made for your team.
A generic assistant answers everything and is accountable for nothing. On the Box an assistant is a precise configuration: the instructions you give it, the folders it is connected to, the tools you switch on and the people it is shared with.
That is where the practical difference comes from: the engineering assistant reads manuals and drawings, the finance one sees invoices and the ERP, the sales one knows the price list and the tone of voice. None of the three sees the others' material, because none of the three has those folders.
Tools are switched on one at a time and stay visible: if an assistant can write an email or read a database, you know because you decided it. Actions that matter still stop in front of a person who approves them.
How an assistant is built
Four levers, always the same, deciding what it knows and what it may do.
Instructions and tone
What job it does, in what tone, what it must not do and when it should stop and ask.
Connected folders
The sources it is allowed to answer from: the same document folders, with the same permissions.
Tools enabled one by one
Mail, calendar, databases, integrations: each capability is a switch, not an all-inclusive bundle.
Scheduled automations
Things that happen on their own at a set time: the morning briefing, reply drafts, the periodic check.
Sharing and versions
An assistant stays personal or becomes an organization asset; when you improve it, the team gets the updated version.
Approval boundary
Actions that leave the company — sending, publishing, writing to a system — go through a human confirmation.
The model runs where you decide
The assistant can run on an AI model installed on the Box: neither your questions nor your documents leave the company network.
See how the Box is built- Models run locally on the device: nothing is sent to external services, no usage-based billing.
- If you prefer an external provider you connect it yourself — and it stays a reversible choice.
- With local models, documents and conversations are processed on the Box. External providers apply their own data terms.
How the Box fits into everyday work
Every card is a real job: what goes in, what the Box does, what stays with your people.
Training and onboarding tutor
Create a tutor grounded in manuals, policies and approved material that explains and always points back to the official source.People & collaborationPeopleOperationsMaintenanceExternal communication
Prepare newsletter, social and reply drafts from approved sources and guidelines, with human review before publishing.Sales & communicationMarketingSalesLegalIndustrial maintenance and PLC diagnosis
Query Rockwell projects and Ignition tags to reconstruct alarm logic and prepare a technical review with program references.Operations & industryMaintenanceOperationsITEmail and personal productivity
Summarize threads, search archives and prepare replies for approval; cloud connectors remain optional and require dedicated network access.People & collaborationSalesLeadershipProject management
63 connectors ready, credentials stay on the Box
The tools an assistant can be granted, one at a time.
Let's run it on your documents.
Pick your own slot: half an hour on a call, on a case close to yours, no strings attached.
- WorkspaceChat, projects, calendar, mail and messages in one place, under the same permissions.
- DocumentsFolders, templates and search that answers by citing the page it took the answer from.
- IntegrationsMail, calendars, files, ERPs, CRMs and plants: connectors run from the Box and credentials stay there.