24/7 NOC Overlay for a Hosted PBX Reseller

A hosted PBX reseller running NetSapiens® for 45+ small-business customers had a 15-minute critical SLA in its contracts but only daytime in-house engineering. Overnight and weekend coverage was on-call paging to a senior engineer, which worked but burned out the team — and meant the team's only Tier 4 engineer was effectively unavailable for new work because he was always recovering from off-hours pages. Worse, several customer incidents had been undetected for hours because nobody was actively watching platform health overnight: a SIP trunk that flapped at 2am, a certificate that expired without renewal, a queue that filled silently. Customers were complaining, the senior engineer was threatening to quit, and the SLA credits being issued were eating into margin.

• Scope review and inventory: 45 customer tenants, three upstream SIP trunks, two carriers, defined alert categories the in-house team wanted covered.
• Monitoring integration: hooked NOC tooling into NetSapiens® APIs, tuned tenant-specific thresholds for SIP trunk registration, MOS scores per route, CDR anomalies, and certificate expirations.
• Runbook capture: for each alert category, documented the response sequence — initial triage steps, escalation thresholds, customer-communication template, when to wake the on-call senior engineer.
• Shadow period (1 week): NOC ran in parallel with the in-house team copied on every alert to validate thresholds and response quality.
• Cutover: NOC took primary off-hours monitoring ownership. In-house team retained day-shift queue ownership and Tier 4 platform engineering.
• Weekly post-incident review: every customer-impacting event reviewed jointly to refine runbooks and thresholds.
• Monthly NOC report: top alerts by category, incidents resolved before customer impact, average detection-to-resolution times.