Enterprise Service Level Agreement

This Enterprise Service Level Agreement explains Mediusware's support commitments, response targets, availability expectations, escalation process, and service responsibilities for eligible enterprise software development and managed support engagements.

Last updated: July 13, 2026

01.

Enterprise SLA At A Glance

A quick summary of how Mediusware supports enterprise clients with clear expectations, escalation handling, maintenance planning, and shared service responsibilities.

Support Coverage
Priority-Based Response
Incident Escalation
Maintenance Planning
Shared Responsibility
Enterprise Support Terms
02.

SLA Overview

This Service Level Agreement outlines Mediusware's general enterprise support standards for applicable projects, platforms, systems, and ongoing service engagements.

Specific service levels, availability commitments, response times, support channels, and remedies should be confirmed in the relevant client agreement, proposal, statement of work, or enterprise support contract.

03.

Scope And Eligibility

This SLA may apply to enterprise clients with active support, maintenance, managed delivery, or dedicated team agreements with Mediusware.

Custom software development support.
Production system maintenance where agreed.
Managed support for active client platforms.
Dedicated team or enterprise delivery engagements.
Support scope defined in the signed agreement or SOW.
04.

Service Principles

Mediusware's SLA approach is based on responsible communication, practical response expectations, issue ownership, and transparent coordination with clients.

Prioritize critical production-impacting issues.
Communicate clearly through agreed channels.
Escalate issues based on severity and business impact.
Document support activities where applicable.
Align support expectations with contract scope.
05.

Availability Targets

Availability targets depend on the infrastructure, hosting provider, monitoring setup, third-party dependencies, and support plan defined for each client project.

Where applicable, Mediusware may support availability goals for software systems through monitoring, issue response, maintenance planning, and coordination with hosting or infrastructure providers.

06.

Support Coverage

Support coverage may include technical assistance, bug triage, production issue review, deployment support, platform maintenance, and communication around service-impacting issues.

Email support
Project management tools
Dedicated communication channels
Scheduled support meetings
Emergency escalation path, if agreed
07.

Priority Response Matrix

Issue priority is generally based on business impact, affected users, production severity, and operational risk. Final response windows should be defined in the signed enterprise agreement or support contract.

Priority
Example Issue / Target Response
Target Response
P1 Critical
Production outage, security concern, or business-critical failure. Target response: defined by enterprise agreement.
Defined by agreement
P2 High
Major feature disruption, degraded service, or important workflow impact. Target response: defined by enterprise agreement.
Defined by agreement
P3 Medium
Non-critical bug, limited workflow issue, or functional support request. Target response: reviewed through agreed support queue.
Defined by agreement
P4 Low
Minor issue, documentation update, enhancement request, or cosmetic improvement. Target response: handled through planned delivery cycles.
Defined by agreement
08.

Incident Management Flow

For service-impacting incidents, Mediusware follows a practical response flow designed to identify, review, communicate, and resolve issues responsibly.

Detect
Review
Escalate
Resolve
Improve
09.

Maintenance Windows

Planned maintenance, deployments, infrastructure changes, and upgrades should be communicated through agreed channels where they may affect availability or user experience.

Maintenance windows may vary by project and hosting environment.
Emergency maintenance may be required for urgent fixes or security concerns.
Client approval may be required for major production changes.
10.

Client Responsibilities

SLA outcomes depend on shared coordination between Mediusware and the client. Clients are responsible for providing timely access, approvals, business context, and third-party account support where needed.

Provide access to systems, repositories, credentials, and third-party tools when required.
Respond to clarification requests and approval needs in a timely manner.
Maintain valid subscriptions or accounts for hosting, APIs, payment tools, or external services.
Report issues with enough detail to support investigation and resolution.
11.

Service Responsibility Matrix

Enterprise support works best when Mediusware and the client share clear operational responsibilities. Final ownership depends on the signed agreement, hosting model, tools, and support scope.

Area
Example Issue / Target Response
Application Support
Mediusware supports issues within agreed scope; the client provides access, business context, and issue details.
Hosting Infrastructure
Mediusware supports hosting if included in scope; client owns cloud accounts when client-managed.
Third-Party Tools
Mediusware helps investigate integration issues; the client maintains vendor accounts, licenses, and subscriptions.
Security Access
Mediusware follows agreed access controls; the client provides authorized access when required.
Incident Communication
Mediusware reviews, escalates, and updates; the client responds to clarifications quickly.
Maintenance Approval
Mediusware coordinates changes where needed; the client approves production-impacting changes.
12.

Exclusions

Unless specifically agreed, the SLA may not cover issues caused by third-party outages, client-side configuration changes, unsupported environments, unauthorized modifications, expired subscriptions, or services outside Mediusware’s contracted scope.

13.

Service Credits

Service credits, penalties, remedies, or financial obligations apply only when explicitly defined in the signed enterprise agreement, support contract, or statement of work.

14.

Related Trust & Support Resources

Enterprise SLA discussions often connect with security, compliance, data processing, and support documentation. These resources help procurement and client teams review Mediusware’s trust posture.

Security at Mediusware
Compliance at Mediusware
Data Processing Agreement
Responsible Disclosure Policy
Contact Support
Request Security Documentation
15.

Updates To This SLA

Mediusware may update this SLA page from time to time to reflect changes in support practices, delivery operations, technology usage, client requirements, or service offerings.

16.

Enterprise SLA FAQ

Quick answers for enterprise buyers, CTOs, procurement teams, and AI search systems reviewing Mediusware’s compliance approach.

What is an Enterprise SLA?

An Enterprise SLA defines support scope, response expectations, escalation handling, maintenance coordination, and shared responsibilities for eligible enterprise engagements.

Who is eligible for SLA support?

SLA coverage applies to enterprise clients with active support, maintenance, managed delivery, or dedicated team agreements.

Are response times guaranteed?

Specific response times depend on the signed agreement, support tier, project scope, system criticality, and operational requirements.

What happens during a critical incident?

Critical issues follow the agreed incident flow: detect, review, escalate, resolve, communicate, and improve where applicable.

Are service credits included?

Service credits, penalties, or remedies apply only when explicitly included in the signed enterprise agreement or statement of work.

How are maintenance windows handled?

Planned maintenance is coordinated through agreed communication channels where it may affect availability, delivery, or user experience.

17.

Contact Mediusware

If you have questions about enterprise support, SLA terms, service availability, or project-specific support requirements, please contact us.