Service Management and SLAs

Clearer expectations at the point work is logged.

Configure the service-desk, catalogue, customer-contract and service-level structure that guides how teams record, assign and prioritise work.

Reliable service starts with a defined model

Service desk around equipment

An iTop ticket can record a request or incident, relate it to equipment and customer, and allocate ownership.

Medeq adds the field job on top of that ticket context. Confirm exact ticket types, lifecycle steps, approvals, assignment rules and hand-offs in the deployed environment.

Define the requested service

A configured service catalogue can organise maintenance and support offerings for a customer, and give the ticket a service and subcategory context.

Catalogue content, eligibility, pricing treatment and customer access are customer-specific. Availability depends on the configured service model.

Relate work to contracts

Customer-contract structures can distinguish covered services and define the relationship between customer, service offering and agreed service model.

A contract record alone does not determine commercial coverage. Content, exclusions, dates, approvals and billing treatment require business rules and commercial review.

Configure service-level expectations

An SLA can set response and resolution targets by service, priority and customer context — a high-priority incident may carry a different target.

Target calculations, priorities, escalation rules, coverage windows and business-hours behaviour depend on the deployed configuration. A target sets an expectation; it does not ensure the result.

Connect coordination to the job

The ticket can carry customer, device, service, contract, priority and target context. Medeq then guides the technician through the job card.

This keeps service coordination and the completed device record related. Field-interface visibility still depends on the deployed configuration.

Notifications after rules agreed

Medeq can assess workflow rules and notifications for status changes or target events, and reporting views once measures and permissions are clear.

Medeq can assess, configure and test each required reminder, customer message, escalation or report. Availability depends on agreed rules, data, permissions and the deployed environment.

Define the service rules before configuring the workflow

Bring your service catalogue, customer agreement, priority model and field process. We assess what the deployed environment can support.