Maintenance Contractors

Maintenance contractors can manage requests, dispatch, field work, parts, approvals, evidence, and service outcomes while developers or property operators follow the cases assigned to them.

Generic Pipeline Management in Amarnex

How This Tenant
Works In Amarnex

The contractor keeps its technicians, schedules, internal costs, supplier details, credentials, and other clients private. Each developer or property operator receives a controlled service pipeline for the properties, units, contracts, and service levels it authorizes.

Customer And
Partner Interactions

Shared Pipelines Between Tenants

Shared Pipeline
Management

The originating tenant shares the minimum property, unit, contact, issue, access, priority, and service-level information. The contractor returns the appointment, status, estimate, approval request, evidence, completion, and service result.

Shared pipeline management product interface

Tenant Data & Access
Controls

Each tenant keeps its users, credentials, communication channels, internal notes, and private records isolated. Staffing, margin, suppliers, and unrelated customer data stay private. Only approved records, stages, documents, tasks, and indicators are shared, with permissions, ownership, expiry, and audit history.

Recommended Amarnex Modules

  • Service Request Management
  • Scheduling and Field Operations

    Assign teams, visits, routes, access, and real-time status.

    Maintenance workflow product interface
  • Work Orders and Approvals
  • Customer Communications
  • Documents and Evidence
  • Service Pipelines and SLAs

Recommended Features

Service history product interface

Property and unit service history

SLA tracking product interface

Priority, SLA, and escalation timers

Business Benefits

Connected Maintenance Workflows

Why This Configuration Matters

Customers judge the property experience through service delivery. A connected pipeline keeps them informed and gives the property organization visibility, while the contractor retains operational control.

Example connected journey

A tenant reports an issue, the property operator assigns it through a shared pipeline, the contractor schedules a technician, requests approval if needed, sends progress updates, records completion evidence, collects feedback, and returns the result to the property record.

Governance and rollout

Start with the pipeline stages, information ownership, sharing rules, service levels, and success measures agreed by the participating tenants. Configure the required modules, train each team for its role, and review performance without exposing unrelated tenant data.

CTA

Design Your Tenant Workflow

Closing ring

Your Next Development Deserves a
More Connected Way To Work

Ready to make your next development a connected journey?

Book a Demo