Enterprise Service Level Agreement

We hold ourselves to clear service levels because accountability should be measurable — not something you have to take on faith. We think of these as service level objectives: a standard we hold ourselves to, knowing one size doesn't fit all. They give you a clear baseline for what to expect, and a foundation we tailor to what matters most for your business. This document covers our support priorities, response and resolution targets, availability, and how we escalate during emergencies.

Effective date: January 1, 2024 · Version: 1.0

Support coverage

  • Standard support: Monday–Friday, 9:00 AM – 5:00 PM Eastern Time (ET), excluding statutory holidays.
  • Critical (P1) support: 24/7/365 via our after-hours on-call team for company-wide outages and emergencies.
  • How to reach us: Submit a ticket by emailing support@portalnetworks.ca, or call 519-804-1234 or 844-777-8888.
  • After-hours Critical emergencies: call 519-804-1234 or 844-777-8888 and press 9 to reach our on-call service.

Response and resolution targets are measured from ticket creation during the applicable coverage window. Most issues are handled faster than the targets below.

Priority levels & targets

PriorityWhat qualifiesFirst responseResolution targetCoverage clock
P1 — CriticalEntire business down; company-wide outage; active security incident; hosted voice or internet fully down at a siteWithin 1 hourContinuous work until restored; restoration or workaround targeted within 4 hours (best effort)24/7 (on-call)
P2 — HighA team or department can't work; major service degradation; partial outageWithin 2 business hoursWithin 8 business hoursBusiness hours
P3 — MediumA single user affected; degraded but workable; non-blocking issueWithin 4 business hours1–2 business daysBusiness hours
P4 — LowService or change request, “how-to” questions, scheduled workWithin 1 business day3–5 business daysBusiness hours

Resolution targets are goals, not guarantees, and reflect best-effort restoration; some issues require third-party or vendor action outside our control (see Exclusions).

Availability objectives

Our availability objectives for the services Portal hosts and monitors. Uptime is measured monthly, per service, and excludes scheduled maintenance and the conditions listed under Exclusions.

ServiceAvailability objective
Hosted voice (Portal-managed PBX)99.9% monthly availability for Portal's hosted PBX platform, running on redundant Canadian infrastructure.
Business internetDelivered and managed by Portal over wholesale access to Canada's major carrier networks, with proactive monitoring and 24/7 support. Enhanced availability is available where Portal provides redundant or failover connectivity. Last-mile access circuits are governed by the carrier's SLA (see Exclusions).
Managed infrastructure99.9% monthly availability for infrastructure Portal hosts. For on-premises environments, Portal provides comprehensive monitoring, proactive maintenance, and the response and resolution targets above.

How we respond to a Critical (P1) incident — escalation

When a Critical incident is confirmed, Portal commits to:

  1. Acknowledge within 1 hour, 24/7, and begin work immediately.
  2. Status updates every 60 minutes to your designated contact until the issue is resolved or a workaround is in place.
  3. Escalation path: if a P1 is not resolved or progressing, it escalates to the service manager at +1 hour and to Portal ownership at +2 hours.
  4. Post-incident report: for any P1 — and for any month a service misses its availability commitment — Portal provides a written summary of what happened, root cause, and the corrective action taken.

This remediation-and-communication commitment is how we stand behind our targets.

Scheduled maintenance

Routine maintenance is performed during off-peak windows, typically Sundays 2:00–4:00 AM ET, with at least 48 hours' notice for any maintenance expected to cause a service interruption. Scheduled maintenance is excluded from availability calculations.

Exclusions & when the SLA clock pauses

These targets do not apply to, and the SLA clock pauses during:

  • Force majeure events (natural disasters, widespread internet/power failures, etc.).
  • Outages or faults caused by third parties or upstream carriers (e.g., last-mile internet, SIP/SMS carriers, cloud providers) outside Portal's control.
  • Issues caused by customer actions, equipment, or environment, or changes made without Portal's involvement.
  • Time spent awaiting a response, access, or approval from the customer.
  • Services or equipment not covered under the customer's active agreement.

Reporting

SLA and availability performance is available to customers on request, and is reviewed during regular account check-ins (QBRs for MSP clients).