Receive and organize every request
Create requests internally or receive them from your customers. Prioritize them, assign them to the right technician and move them through your statuses on a visual board — nothing goes unattended.
Receive, assign and track every service request, log your technicians' work in work orders and bill the hours — with Kanban boards, a portal for your customers and full traceability per asset. All integrated with your invoicing and inventory.
The Adm Cloud Service module is the solution for companies that handle requests, maintain equipment and bill their technicians' work. It connects four pieces in a single flow: the customer's asset, the service request, the work order and the contract — all inside the same ERP where you already run your invoicing, inventory and accounting.
Create requests internally or receive them from your customers. Prioritize them, assign them to the right technician and move them through your statuses on a visual board — nothing goes unattended.
Every intervention is documented in a work order: technician hours, spare parts used and the asset serviced. Distinguish what is covered by warranty from what is billable.
Authorize and convert work orders into credit invoices, carrying over items, services, prices and taxes. Service and sales speak the same language.
Each piece has its own purpose and independent access permissions, but they share the same information: the customer, the asset and the history are always connected.
The ticket or requirement: the heart of the module. This is where you plan, prioritize, assign and track every job before and during its execution.
The record of actual execution: how much time each technician spent, which spare parts were used and on which asset. It is the bridge between technical work and invoicing.
The recurring commercial agreement: contracted maintenance, extended warranty or support plan. Track active coverage, expirations and renewals.
The catalog of equipment, machines or goods you service. It provides full traceability: every request, order and contract points to a specific asset.
This is how a request travels through the Service module, leaving a trail at every step.
The customer or your team creates the request and links it to the affected asset.
It is prioritized and assigned to the right technician from the Kanban board.
The technician logs hours and spare parts in a work order.
It goes through QA and customer approval; then it is authorized for invoicing.
The order becomes a credit invoice in a single step.
Beyond the four pieces, the module brings cross-cutting capabilities that adapt to the way each company works.
Visualize and move your requests by status, technician, owner or type. Drag, drop and reorder; reassign on drop.
When a status changes, the technician is notified in the app and, if you configure it, the customer by email. Ticket followers stay in the loop too.
Your customers create requests, follow their tickets, approve pending work and leave comments — with wording and statuses designed for them.
Define your own statuses with color, name and behavior (closes, notifies, hides from portal). Create multiple workflows depending on the type of service.
Suggests similar, already-resolved requests using semantic similarity, so your team reuses solutions and responds faster.
Schedule requests, reschedule them and view them on a calendar. Then compare what was planned against what was executed.
Link requests from different customers reporting the same issue: status and attributes are managed from the parent and propagate automatically.
Log commercial follow-up per request and contract, and detect which ones have gone the longest without customer contact.
The module includes reports, charts and pivot tables to understand workload, response times, your technicians' productivity and service profitability.
Request execution time, efficiency by status, average days in each status and requests with status and days of age.
Billable hours per technician and month, hours per employee, billable-hours chart and a work order cost report.
Identify stalled tickets or those with no recent activity, and the ones that have gone the most days without customer contact.
Pivot tables to analyze service requests and orders your way, cross-referencing customer, technician, status, date and more.
Compare what you scheduled against what actually got done, to fine-tune your planning and deliver for your customers.
All the service provided to each customer asset in one place: what was done, when and who handled it.
If your business serves customers, repairs equipment or bills work hours, this module is for you.
Help desks with tickets, priorities, QA and day-based SLAs.
Assets with brand, model and serial, service history and recurring contracts.
Assigned technicians, hours worked and orders that consume spare parts from inventory.
Tickets linked to projects, assigned consultants and billable-hours tracking.
Service doesn't live in isolation: it shares data with the rest of Adm Cloud, with no exporting or re-entering.
Work orders become credit invoices with items, services, prices, discounts and taxes.
Consumes items with lot, serial, location, kit and unit-of-measure handling. Assets are linked to the catalog.
Activities and contacts per request and contract, with the requester taken from the customer's contacts.
Requests and orders are tied to projects so you can track services within each initiative.
Log technician hours and the use of your own machinery, to bill labor and equipment.
Subsidiary and location filters throughout the module, with screen names and statuses customizable per company.
The service request is the requirement: what is being asked, for which customer, on which asset, with what priority. The work order records the actual execution of that requirement: the technician's hours and the spare parts used. A single request can generate several work orders (one per visit or intervention).
Yes. Statuses are fully configurable: you define their name, color and behavior (whether they close the ticket, notify the customer, show or hide in the portal). You can also create several different status workflows depending on the type of service you provide.
Yes, through the customer portal. From there they can create new requests, check the status of theirs, approve work that needs their sign-off, change the priority, cancel and leave comments. The statuses and wording the customer sees can differ from the internal ones.
Each work order distinguishes warranty hours (no charge) from billable ones. Once authorized, the order becomes a credit invoice, automatically carrying over items, services, prices, discounts and taxes — with no re-entry. You can group several orders into a single invoice.
Yes. You register each piece of equipment as a customer asset with its brand, model, serial number and year. Every request, order and contract is linked to the asset, so you have its complete service history and can manage maintenance contracts and their expirations.
Completely. The Service module shares data with Invoicing, Inventory, CRM, Projects, Employees and Accounting. It is part of the same ERP, so a service delivered is reflected in your invoicing, your inventory and your financial reports with no manual steps.
Requests, orders, contracts and assets — all connected to your invoicing and inventory, in a single ERP.