Service
Assets and equipment with history, independent of the customer.
Create assets, equipment, or sites as service objects. Every job, report, and maintenance contract hangs off the object, including a customer-visible portal description, separate from internal notes.
These are the points this feature covers day to day.
The workflow in Jupiter ERP, on this page.
Background, typical workflows, and concrete panel capabilities, more detail than the summary above.
Recurring service often hangs off an asset or site, not only the company name. Service objects model exactly that: jobs, reports, and maintenance contracts stay traceable on the object, even when the contact person changes.
An optional portal description is separate from internal notes. In the portal, customers only see what you intended for them.
From the object you open related orders and reports. Maintenance contracts reference the same object, so due service is visible before the customer calls.
The asset is the installation, the device, or the site. Visits stay attached to it even when the contact person at the customer changes.
Without an asset, history spreads across customer files and email. With an asset, dispatcher and technician open the record and see the recent visits.
Service assets belong to the Service module.
The main building blocks at a glance, complemented by the longer description above.
Name, location, contact, and internal notes, plus an optional description customers see in the portal.
Trace service orders and reports on the object: ideal for recurring maintenance on the same asset.
Reference maintenance contracts and follow-up documents on the object. No parallel Excel lists per device.
Start for free: write invoices on the Free plan. Choose plan, term, and add-ons in the app afterwards. Custom adaptations or API integration? Get in touch.
