Module screen from the modules page

Maintenance Request Management

Turn customer service requests into trackable cases with ownership, priorities, scheduling, updates, evidence, and closure.

Why the case matters

Module workflow from the modules page

A service request becomes a case the team can follow. It carries an owner, a priority, and a schedule, and the updates, evidence, and closure stay on that case.

Connected view

Keep the customer request, its owner, and its priority on one case.

Right context

Show the schedule and the next update, so the team knows when the work is due.

Workflow data

Read the updates and evidence on the case to see what has already been done.

Shared pipelines

Hand the case onward with the evidence and the latest update still attached.

Case closure

Close the request when the updates and evidence are on the case, so the record shows how the work ended.

Related Features

Each request names who owns it and when the work is scheduled, so a case is not left without a next step.

Module workflow from the modules page

Confirm who can own a case, how priority is set, and what evidence is required before closure.

Module screen from the modules page

Why Amarnex?

Amarnex

Limits

The case tracks owner, priority, schedule, updates, evidence, and closure. Warranty decisions stay outside it.

Handoffs

Scheduled work goes to the owner, and closure returns with the evidence and the latest update.

Confirm first

Confirm who may own a case, and what evidence is required, before requests are opened.

Limits

The case tracks owner, priority, schedule, updates, evidence, and closure. Warranty decisions stay outside it.

Handoffs

Scheduled work goes to the owner, and closure returns with the evidence and the latest update.

Confirm first

Confirm who may own a case, and what evidence is required, before requests are opened.