Vendor Page Coordination

When vendors page you.

Overview

Vendor pages need explicit handling because they cross trust boundaries the internal rotation does not. A page from Datadog, AWS, or Cloudflare arrives with different context, different SLA terms, and different escalation paths than an internal alert.

• Cross-boundary signal. Vendor pages bring outside context. The team cannot see the vendor’s telemetry, only the symptom.
• Per-vendor routing. Each vendor routes to a named handler. Random round-robin loses context across pages.
• SLA awareness. The vendor’s SLA dictates how the team must respond. Missing the SLA is contractual, not just operational.
• Cross-team coordination plus escalation. Vendor pages frequently span teams. Each vendor has a documented escalation chain that names humans, not Slack channels.

The approach

Three habits keep vendor pages from becoming the noisy, mishandled corner of the rotation: per-vendor routing, per-vendor SLA tracking, and a written page policy.

• Per-vendor routing. Dedicated PagerDuty integration or escalation policy per vendor. The first responder is consistent.
• Per-vendor SLA tracking. SLA terms in the runbook, not in the contract folder. Responder reads the SLA at page time.
• Cross-team coordination protocol. Vendor pages spanning multiple teams trigger a written coordination protocol, not an ad-hoc bridge call.
• Documented escalation chain. Per-vendor escalation lists names, not slugs. The on-call knows who to call when ack does not arrive.

Why this compounds

Each correctly-handled vendor page preserves the vendor relationship and the team’s contractual standing. Patterns transfer across vendors with similar shapes.

• Vendor trust. Predictable, on-SLA responses preserve the working relationship and the future renewal conversation.
• Faster incident response. Routing-by-vendor cuts the time the wrong responder spends figuring out what they are looking at.
• Workload-matched policy. The right page policy per vendor reflects the vendor’s SLA, not a uniform internal default.
• Year-one investment, year-two habit. The first vendor policy is heavy lift. Subsequent vendors reuse the template with new names.