WISPGate
Home
Business Outcomes Core Modules Technical Details
High-Level System Deep Customization Deployment Models Integration Ecosystem
Tiers Offers AI Module
Media Hub Knowledge Base Case Study Blogs Whitepapers Integration Guide API Reference Release Notes
Core Commercial Public Legal Compliance & Data
About WISPGate Partner Program Contact Us
Book Demo Explore Platform
WISPGate Legal

Service Level Agreement (SLA)

Last Updated: April 23, 2026  •  Version: v2.0  •  Document ID: wg-sla

1. Scope

This Service Level Agreement applies to hosted production environments under an active paid subscription and only to the extent expressly referenced in a signed order form. It does not apply to sandbox, trial, development, staging, proof-of-concept, implementation, or legacy environments unless expressly stated in writing.

2. Definitions

Available means the production application login and core service functions are materially reachable and operational from Provider-controlled infrastructure. Downtime means verified inability of the covered service to perform core platform functions due solely to Provider-controlled production failure. Intermittent slowness, partial degradation, customer-side issues, or third-party failure do not automatically qualify as downtime.

3. Uptime Commitment

Provider targets 99.5% monthly uptime for covered production services unless a different figure is stated in a signed order form.

4. Support Priority Targets

PriorityDescriptionInitial Response Target
P1Critical platform outage affecting core production operations for the customer15 minutes
P2Major functional impairment with no reasonable workaround1 hour
P3Non-critical issue, defect, or degraded behavior with workaround available24 hours
P4General request, advisory matter, or cosmetic issueBest effort

5. Resolution

Response targets are not fix guarantees. Provider will use commercially reasonable efforts to investigate and mitigate incidents based on severity, reproducibility, scope, and dependency profile.

6. Exclusions

The following are excluded from uptime calculations and SLA remedies:

  • Scheduled maintenance and emergency security maintenance.
  • Customer-side network issues, DNS issues, firewalls, credentials, or device failures.
  • Failures of third-party systems, APIs, payment gateways, telecom equipment, or internet providers.
  • Misconfiguration, unsupported customizations, or unsupported environments.
  • Beta features, custom development work, and migration periods.
  • Force majeure events, legal restrictions, or actions required for security containment.

7. Credit Schedule

Verified Monthly UptimeService Credit
Below 99.5% but at or above 98.5%5% of affected monthly recurring fee
Below 98.5% but at or above 97.0%10% of affected monthly recurring fee
Below 97.0%Maximum 10% of affected monthly recurring fee unless a signed order form states otherwise

8. Credit Conditions

  • Customer must submit a written credit request within seven (7) days after the month in which the incident occurred.
  • Credit is applied only to future subscription fees and is never payable in cash.
  • Credits are the exclusive remedy for covered downtime.
  • No credit applies if Customer is in payment default.

9. Measurement Control

Provider’s incident records, infrastructure logs, uptime records, and ticket history control the determination of whether an event qualifies for SLA credit, subject to correction of manifest error.

10. No SLA Expansion by Conduct

Support effort beyond stated targets, goodwill actions, WhatsApp responsiveness, or ad hoc interventions do not amend this SLA or create binding precedent.

WISPGate
© 2026 WISPGate. All rights reserved.
Home Legal Copyright
We use cookies to improve your experience. By continuing, you agree to our Cookie Policy.