Business ContinuityITVendor Management

Vendor Risk Playbook: What Departments Must Do Before Switching Carriers After an Outage

ddepartments

2026-01-22

9 min read

Step-by-step playbook for IT and ops to assess risk, claim service credits, and migrate carriers after a major outage.

When a major telecom outage leaves phones and critical links dead, departments panic. Here’s a vendor risk playbook IT and operations teams must run — now.

Immediate priorities: protect continuity, gather evidence for service credits, and evaluate vendor risk before making any carrier switch. This playbook gives a step-by-step risk assessment and migration plan you can execute the same day, in the weeks after, and into a full migration if you choose.

Immediate 0–72 Hour Response: Stop the Bleed

When an outage like the high‑profile telecom disruptions seen in late 2025 hits, the first 72 hours decide whether your operations survive without customer harm. Follow these prioritized actions.

1) Document everything — evidence is power

Time-stamped logs: collect syslogs, monitoring alerts, call failures, and application errors with accurate UTC timestamps.
Vendor ticket IDs: open a ticket immediately and record ticket numbers, support reps, and escalation paths.
Customer impact records: gather customer complaints, lost transactions, and sales impacts (ideally dollarized).
Third-party corroboration: screenshots of outage maps, provider status pages (archive with web capture), and independent outage monitors.

2) Activate continuity measures

Failover to secondary circuits or cellular (LTE/5G) using SD-WAN or local routing rules.
Enable eSIM or pre-provisioned SIMs for critical devices and point-of-sale terminals.
Bring up cloud-based contact center fallbacks (SIP trunking, cloud IVR) if PBX is impacted.
Communicate to customers: post on your status page, social channels, and key clients about expected impacts and mitigations.

3) Start the service credit clock

Most telecom SLAs require claims to be filed within a set window — often 30–60 days. Prioritize: collect documentation now so you can submit before deadlines expire.

Locate the telecom SLA in your contract — find credit calculation method and claim deadlines. If your legal and ops docs live as structured text, consider a docs-as-code approach to make contract search and evidence extraction faster.
Prepare an evidence packet: logs, timestamps, vendor incident reports, and business impact summary.
Submit a formal claim to the vendor and set follow-up reminders (escalate if no response in defined timeframes).

Step-by-Step Risk Assessment Before You Switch Carriers

Switching carriers is expensive and risky. Use this eight-step assessment to decide whether to switch, negotiate, or add redundancy.

1) Stakeholder mapping and decision authority

Identify signatories, budget owners, compliance leads, and users affected by telecom changes.
Assign an incident owner for the evaluation (IT or operations lead) and a steering committee for go/no‑go decisions.

2) Inventory & criticality scoring

Map all services tied to the carrier: voice, SIP trunks, MPLS, dedicated internet, failover, IoT, POS systems.
Score each asset on a 1–5 criticality scale for customer-facing uptime and regulatory risk.

3) Vendor performance evaluation

Collect historical MTTR and outage frequency over the last 12–24 months.
Review incident root cause reports (if provided) and vendor remediation timelines.

4) Contract and SLA deep dive

Spot termination windows, early termination fees (ETFs), minimum commitment periods, and notice requirements.
Locate the SLA schedule: guaranteed uptime, maintenance windows, exclusions, and service credit formula.

5) Financial & business impact analysis

Calculate hourly revenue loss and reputational costs from outage scenarios (use cost playbooks and TCO models — see cost playbook approaches).
Estimate total cost of ownership (TCO) for migration vs. cost of implementing redundancy.

6) Technical migration risk assessment

Assess porting timelines for phone numbers, certificate management, DNS changes and routing propagation.
Identify single points of failure in your stack that a new carrier could expose.

7) Regulatory and compliance check

Confirm number portability regulations, privacy impacts, and obligations for regulated industries (healthcare, finance).
Assess audit trail requirements for incident investigation and evidence preservation.

8) Scoring and recommendation framework

Create a risk scorecard. A simple formula to start: weighted sum across criticality, financial impact, migration complexity, and contract exposure. Use scores to recommend: Stay and enforce SLA, Add redundancy, or Switch.

How to Evaluate a Telecom SLA — What Departments Must Look For

When the outage makes you think “never again,” the SLA is where the rubber meets the road. Focus on these elements.

Uptime guarantee (e.g., 99.95%) — confirm measurement method (calendar month) and exclusions.
Mean Time To Repair (MTTR) commitments and response/priority SLA tiers.
Service credit calculation — how downtime maps to percentage credits and monthly caps.
Escalation matrix — guaranteed response times for priority 1 issues and named contacts.
Maintenance notification rules and allowed maintenance windows.
Liability and indemnity — caps on damages versus actual business loss.

Illustrative credit calculation (example only): if a 30‑day month guarantees 99.95% uptime (≈21.6 minutes allowable downtime), and your observed downtime is 120 minutes, the percentage below SLA is (120 - 21.6)/ (30*24*60) = X. Multiply that by monthly circuit fee and apply cap per contract. Always verify the exact formula in your SLA.

Migration Plan: A Phased, Reversible Approach

Never do a “big bang” cutover without pilot validation. Follow this phased migration plan to reduce operational risk.

Phase A — Planning & procurement (Weeks 0–4)

Run an RFP or ask for proposals focused on resiliency and measurable SLAs.
Negotiate transitional supports: temporary overlapping service, porting acceleration, and outage indemnities.
Provision non-production test lines and firewall rules to validate connectivity (use automated runbooks and templates-as-code approaches to keep playbooks reproducible).

Phase B — Staging & pilot (Weeks 2–6)

Deploy a pilot at a low-risk site or subset of users (e.g., one call center team).
Validate call quality (MOS), latency, packet loss, and failover behavior under load. Monitor with strong observability — see strategies for observability and incident detection.
Run security scans and compliance verifications on session path and management interfaces.

Phase C — Controlled cutover (Weeks 4–12)

Port numbers in batches (not all at once) and keep the old carrier active until stable.
Update DNS TTLs to short windows prior to cutover for quick rollback.
Run live failback tests and ensure rollback runbook is practiced and validated.

Phase D — Optimization & contract closure (Weeks 8–16)

Monitor KPIs for 30–90 days: call completion, latency, MOS score, and MTTR on incidents.
Finalize contractual termination with previous carrier only after service stability and port confirmation.

Technical Tasks Often Missed — Don’t Overlook These

SIP header transformations and carrier codec mismatches.
Emergency services (E911) provisioning and address validation.
Number portability timelines (local vs toll-free) and cross‑carrier dependencies.
Certificate and key rotation if session routing changes require new TLS endpoints.

Negotiation Tactics & How to Claim What You’re Owed

Use the outage not just as a grievance but as leverage. Departments often leave money on the table during negotiation — here’s how to avoid that.

Assemble the evidence packet

Outage timeline with internal and vendor timestamps.
Financial impact worksheet (lost revenue, restoration labor costs).
Customer impact and churn indicators.

Submit a formal claim — sample approach

Subject: SLA Credit Claim — [Account Number] — Outage [Start Date] to [End Date] Dear [Carrier Support Manager], We are submitting an SLA credit claim per Section [X] of our agreement. Attached are time-stamped logs, ticket numbers, and a business impact summary. Please confirm receipt and your planned resolution timeline. Regards, [Name], [Title]

Escalate and negotiate

If the initial claim is denied or delayed, escalate to named account executive and legal counsel for contract enforcement.
Request remediation beyond credit if business impact was high: free months of service, enhanced SLA terms, or waived ETFs if you transition.
Benchmark competing offers — a valid RFP demonstrating alternatives strengthens your negotiating position.

Security, Compliance, and Vendor Assurance

Switching carriers changes your trust boundary. Add these controls before and after migration.

Ensure new carrier provides SOC 2 / ISO 27001 evidence and a third‑party risk assessment. Consider augmented oversight for supervised systems at the edge.
Harden management interfaces and enable MFA for carrier portals.
Include post-migration vulnerability scans and a short attestation window from the carrier on remediation.
Retain audit logs and signed incident reports from the old carrier for regulatory proof — preserve your chain of custody records (see chain-of-custody best practices).

Case Study — Mid‑Size Retailer (Hypothetical but Practical)

Context: A 250‑store retailer relied on a single national carrier for payment processing and store connectivity. After a 6‑hour outage during peak sales in late 2025, the CIO led a cross-functional response.

Immediate actions: enabled 5G eSIM failover on POS terminals, opened vendor claims, and published status updates to customers.
Risk assessment: critical services (payment, inventory sync) scored 5; porting complexity scored 3; contractual ETFs were manageable.
Migration plan: deployed SD‑WAN with two carriers, staged porting by region, and retained old carrier for 90 days overlapping.
Outcome: during a subsequent localized outage, failover kept payments processing with negligible revenue loss. Retailer secured two months of bill credits plus an improved SLA for enterprise customers.

Lessons learned: keep pre-provisioned cellular options for POS, document evidence promptly for claims, and architect for multi-carrier redundancy rather than overreacting to a single incident.

2026 Trends and What Departments Must Prepare For

Late 2025 and early 2026 accelerated several vendor and technology shifts departments must factor into vendor risk strategy:

Multi-carrier mesh architectures and SD‑WAN orchestration are standard for mid‑market and enterprise continuity.
eSIM and remote SIM provisioning allow near-instant cellular failover — pre-provisioning matters.
SASE adoption continues to blur the line between networking and security, enabling centralized policy during carrier failover.
AI-driven incident detection improves early warning but also introduces new dependencies on vendor telemetry; invest in strong observability to validate vendor signals.
Regulatory focus on telecom resilience increased in late 2025 — expect deeper evidence requests and faster enforcement actions.

Actionable Checklists & Templates You Can Use Today

72‑hour Evidence Checklist

Timestamped monitoring logs (UTC)
Vendor ticket numbers & incident IDs
Customer impact log (transactions lost, calls dropped)
Screenshots of vendor status pages and outage maps
Internal incident report with timeline & owner

Pre‑Migration Readiness Checklist

Number portability plan (batches and timeline)
Overlapping service windows and rollback playbook
Security and compliance attestations from new carrier
Pilot success criteria and test scripts (MOS, latency, packet loss)
Stakeholder signoffs and contingency budget

Final Takeaways — What Departments Must Do Next

Act fast to preserve credits: collect evidence and submit SLA claims within contract windows.
Don’t decide under duress: run the risk assessment before committing to a full switch.
Prefer phased migration: pilot, overlap, then cutover — keep rollback options ready.
Invest in redundancy: SD‑WAN, multi-carrier mesh, and pre-provisioned cellular reduce future outage risk.
Negotiate from strength: use documented impact and competing offers to secure credits or better terms.

Quote to remember:

"Outages aren’t just tech events — they’re boardroom events. You must prepare operationally, legally, and commercially to turn disruption into leverage."

Call to Action

If your department was impacted by a recent outage, start with our 72‑hour Evidence Checklist and SLA claim template. Need a tailored risk assessment or a migration runbook built for your environment? Contact our vendor‑risk specialists at Departments.Site to run a rapid assessment and a migration readiness pilot — we’ll help you claim credits, protect continuity, and negotiate stronger SLAs so your operations never stall again.

departments

Contributor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.