What this is
The “Service company” template is listed as planned: it needs a field-work module (work order, engineer, visit) that is not built yet, and an internal request does not replace it.
More detail
The shared modules cover intake, queue, deadlines, approval and the decision record, but not visit planning. Not in this build:
- Field work orders, engineer routes and workload — no module.
- Warehouse, stock levels and parts write-off — no module.
- Visit notifications to customers: the platform never writes first.
- A mobile app for engineers: the panel runs in a browser.
Modules and AI employees
AI employees with work here: support, operations, IT helpdesk, procurement and BI analyst. Modules switched on for a service company today:
- Support: customer requests with a queue, priority and time to first reply.
- Internal operations: requests, tasks, deadlines, schedules and approvals.
- Sales: requests as leads and deals.
- Finance: plan and actuals, invoices for approval.
- Knowledge base: confirmed answers on services, warranty and terms.
- Analytics: monthly figures with a source for every number.
More detail
Same in every industry
Company isolation in the database, a closed permission register, a decision journal the application cannot change or erase, and two-person sign-off where needed. AI employees only prepare drafts; payments, signatures and decisions about people stay with staff. A customer gets a staff member’s reply or, in the website chat when it is on, the verbatim text of a confirmed answer.
Basis: the registry of modules and industry templates; product documentation. This page describes what exists in this build, not what is planned.