Service Module · Adm Cloud i-ERP

Your service operation, under control

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.

Ideal for
Technical support Maintenance Field service Consulting and projects
4integrated modules
5Kanban board views
15reports and analytics
360°traceability per asset
What is the Service module?

From ticket to invoice, without losing the thread

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.

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.

Log hours and the actual work

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.

Invoice without re-entering anything

Authorize and convert work orders into credit invoices, carrying over items, services, prices and taxes. Service and sales speak the same language.

The four pillars

One module, four pieces working together

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.

Service Requests

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.

  • Kanban boards by status, technician, owner or type, with drag and drop.
  • Two-level priority, warranty, tags, attachments and asset link.
  • QA stage and customer approval built into the workflow.
  • Calendar scheduling and a queue of unassigned tickets.

Work Orders

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.

  • Hours tracking: warranty (no charge) vs. billable.
  • Authorization workflow before invoicing, with a pending queue.
  • Consumes items with lots, serials, locations and kits from inventory.
  • Direct conversion to a credit invoice with prices, discounts and taxes.

Service Contracts

The recurring commercial agreement: contracted maintenance, extended warranty or support plan. Track active coverage, expirations and renewals.

  • Early alerts for contracts about to expire (30 days).
  • Renewal workflow: accepted or declined, with a signed status.
  • Linked to the customer's asset, the catalog item and the business line.
  • Days remaining and days overdue calculated automatically.

Customer Assets

The catalog of equipment, machines or goods you service. It provides full traceability: every request, order and contract points to a specific asset.

  • Brand, model, serial number, year and link to the catalog item.
  • Complete service history per asset in a single report.
  • Search by customer, SKU, brand, model or serial.
  • Delete protection when linked transactions exist.
How it works

A clear flow, from start to finish

This is how a request travels through the Service module, leaving a trail at every step.

1

It's created

The customer or your team creates the request and links it to the affected asset.

2

It's assigned

It is prioritized and assigned to the right technician from the Kanban board.

3

It's executed

The technician logs hours and spare parts in a work order.

4

It's validated

It goes through QA and customer approval; then it is authorized for invoicing.

5

It's invoiced

The order becomes a credit invoice in a single step.

Features that make the difference

Built for real service operations

Beyond the four pieces, the module brings cross-cutting capabilities that adapt to the way each company works.

Kanban boards

Visualize and move your requests by status, technician, owner or type. Drag, drop and reorder; reassign on drop.

Real-time notifications

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.

Customer portal

Your customers create requests, follow their tickets, approve pending work and leave comments — with wording and statuses designed for them.

Configurable statuses and workflows

Define your own statuses with color, name and behavior (closes, notifies, hides from portal). Create multiple workflows depending on the type of service.

Similar tickets with AI

Suggests similar, already-resolved requests using semantic similarity, so your team reuses solutions and responds faster.

Scheduling and calendar

Schedule requests, reschedule them and view them on a calendar. Then compare what was planned against what was executed.

Parent-child links

Link requests from different customers reporting the same issue: status and attributes are managed from the parent and propagate automatically.

Activities and contacts

Log commercial follow-up per request and contract, and detect which ones have gone the longest without customer contact.

Reports and analytics

Measure what matters in your service

The module includes reports, charts and pivot tables to understand workload, response times, your technicians' productivity and service profitability.

Times and efficiency

Request execution time, efficiency by status, average days in each status and requests with status and days of age.

Hours and productivity

Billable hours per technician and month, hours per employee, billable-hours chart and a work order cost report.

Idle requests

Identify stalled tickets or those with no recent activity, and the ones that have gone the most days without customer contact.

Dynamic analysis

Pivot tables to analyze service requests and orders your way, cross-referencing customer, technician, status, date and more.

Planned vs. executed

Compare what you scheduled against what actually got done, to fine-tune your planning and deliver for your customers.

Asset history

All the service provided to each customer asset in one place: what was done, when and who handled it.

Who is it for?

Made for companies that live off service

If your business serves customers, repairs equipment or bills work hours, this module is for you.

Technical support

Help desks with tickets, priorities, QA and day-based SLAs.

Maintenance and repair

Assets with brand, model and serial, service history and recurring contracts.

Field service

Assigned technicians, hours worked and orders that consume spare parts from inventory.

Consulting and projects

Tickets linked to projects, assigned consultants and billable-hours tracking.

Everything in one place

Integrated with the rest of your ERP

Service doesn't live in isolation: it shares data with the rest of Adm Cloud, with no exporting or re-entering.

Invoicing (Accounts Receivable)

Work orders become credit invoices with items, services, prices, discounts and taxes.

Inventory

Consumes items with lot, serial, location, kit and unit-of-measure handling. Assets are linked to the catalog.

CRM and customers

Activities and contacts per request and contract, with the requester taken from the customer's contacts.

Projects

Requests and orders are tied to projects so you can track services within each initiative.

Employees and fixed assets

Log technician hours and the use of your own machinery, to bill labor and equipment.

Multi-company and multi-branch

Subsidiary and location filters throughout the module, with screen names and statuses customizable per company.

Frequently asked questions

We answer your questions

What is the difference between a service request and a work order?

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).

Can I define my own statuses and workflows?

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.

Can my customers view and create their own requests?

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.

How is the completed work billed?

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.

Does it work for maintaining my customers' equipment?

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.

Does it integrate with the rest of Adm Cloud?

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.

Get your service operation in order today

Requests, orders, contracts and assets — all connected to your invoicing and inventory, in a single ERP.