A request is opened, assigned to a technician, the work is logged on site and attached to the right piece of equipment. The request doesn't live in one place, the assignment in another and the site note on someone's phone.
The package brings together CRM service requests with Assets cards. Field teams work in the EQLEM Mobile app. Teams that look after their own machines add the Maintenance Management work order, preventive maintenance and mobile technician flow on the same license. Fleet is optional, and its mobile side is a prototype.
Mikro or Logo can keep the invoice and account records. EQLEM manages the service operation.
Who for
Built for technical service companies, businesses working under maintenance contracts, and field teams.
The service desk opens requests and manages SLA tracking and assignment. The field technician handles the work and the assignment from the mobile app. The asset lead follows tags, assignments, locations and counts. The sales team can keep lead and opportunity tracking in the same CRM. Teams using fleet open vehicle cards on web.
Typical scenario
A customer or an internal team opens a service request. The SLA rule and the assignment kick in.
The technician picks up the request in the mobile app, attaches it to the card of the relevant equipment and logs the work done.
When the request is closed, customer satisfaction is measured.
For teams maintaining a plant or machines, the flow runs through work orders. The operator reports a fault by scanning the machine's QR code. The technician moves the work order forward on mobile and records labor and the parts used. Parts come off the warehouse on their own. Preventive maintenance plans open work orders on their own when they fall due. For teams maintaining their own facility, the detailed scenario is on the Facility & Plant Maintenance page.
Asset counts and assignments run on both web and mobile. With the optional fleet module you keep the service vehicle's maintenance and inspection records on web.
Notifications pass on assignments and SLA breaches.
Permissions decide who assigns a request and who closes one. Reporting and the CRM analytics show the service figures. If you already run another system, system sync plans the transfer.
For the pilot, pick one service team, the mobile app and a limited set of equipment. Write fleet down as an optional second phase. Open customer outreach and campaign flows once the service line has settled. Keep the self-service portal and broader analytical AI suggestions out of the first pilot; Outreach Reply AI can wait until inbox volume justifies it.
Primary modules
- CRM — service requests, SLA, satisfaction scores, assignment and customer history
- Assets — asset cards, tags, assignment, location, counts and service operations
Optional: Maintenance Management (with the Assets license; work orders, preventive maintenance, spare parts), Fleet, Sales, Finance, Integration.
Shared features
Notifications, list experience, permissions, reporting, multi-company, modular licensing, system sync.
Benefits
Requests, assignments and equipment are linked in one record. The field team uses EQLEM Mobile and sees the same data as the office. SLA tracking and satisfaction scores put a number on service quality. Customer history shows the service request too. You can run asset counts from the field or the office. Fleet is optional (its mobile side is a prototype), and your current system stays put.
FAQ
Is there mobile for field technicians? Yes. Service requests and maintenance work orders run in the EQLEM Mobile app; there is no separate app to install. The fleet mobile side is a prototype.
Is EQLEM a field service ERP? No. It is a Solution Platform and works alongside the system you already run.
Next step
Start with one team, using service requests, assignment, asset cards and the mobile app; fleet and customer outreach can follow. Begin with Try Free, or open the package from Modules.