Vendor Management¶
16 cards — 🟢 3 easy | 🟡 4 medium | 🔴 3 hard
🟢 Easy (3)¶
1. What are the four vendor support tiers (L1-L4) and what can each do?
Show answer
L1 (Frontline): script-driven troubleshooting, known workarounds. L2 (Technical Support): log analysis, reproduce in lab, config recommendations. L3 (Escalation Engineering): create hotfixes, analyze crash dumps, root-cause complex bugs. L4 (Product Engineering/R&D): design-level changes, architectural fixes, rarely customer-facing.Remember: "Vendor lock-in = switching cost." The deeper you integrate, the harder it is to leave. Use abstraction layers where cost-effective.
2. What are the two axes of vendor escalation and when do you use each?
Show answer
Functional escalation (technical): move the case to a higher tier because the current tier lacks expertise — triggers include inability to reproduce, known workarounds don't apply, or evidence of a software bug. Hierarchical escalation (management): engage the vendor's management chain because the process is failing — triggers include SLA violations, case stalled for 2+ business days, or escalation requests denied.3. What is an RMA and what determines replacement speed?
Show answer
RMA (Return Merchandise Authorization) is the process to get failed hardware replaced. Speed depends on your support contract: Next Business Day (NBD), 4-Hour Response (dispatch within 4 hours), 2-Hour On-site, or Cold Spare (you stock the part yourself for immediate replacement). Always have critical spares on-site for hardware that can't wait for shipping.🟡 Medium (4)¶
1. What makes a well-written support ticket the highest-leverage activity in vendor management?
Show answer
A good ticket front-loads all information L2 needs, bypassing L1 triage entirely. It includes: environment details (product version, serial number, deployment), clear problem statement with impact, timeline of events, troubleshooting already done, attachments (core dumps, logs, graphs), your hypothesis, and requested action. This lets an L2 engineer start working immediately.2. What four SLA metrics should you track for every critical vendor case?
Show answer
(1) Response Time: how long until the vendor acknowledges the case. (2) Update Cadence: how often the vendor provides status updates. (3) Resolution Time: how long until a fix or workaround is delivered. (4) Uptime: availability guarantee for SaaS/hosted services. Document violations with timestamps and reference specific contract clauses.3. What is the recommended escalation timeline for a Severity 1 (production down) vendor case?
Show answer
0h: Open case, state Sev1, request immediate callback. 1h: No response, call back and request manager. 2h: No progress, functional escalate to L2/L3. 4h: No progress, hierarchical escalate to support manager. 8h: No resolution, escalate to regional director plus your account team. 24h: No resolution, executive escalation via your sales contact.4. What six contract leverage points improve your vendor support experience?
Show answer
(1) Named TAM (Technical Account Manager) — single point of contact who knows your environment. (2) Designated Support Engineer — same engineer for all cases. (3) Premium SLA — faster response, 24/7 coverage. (4) Early access/Beta — preview releases, influence roadmap. (5) Quarterly Business Reviews. (6) Training credits included in contract. Negotiate during renewal, not during incidents.🔴 Hard (3)¶
1. What are the key sections of a Severity 1 support ticket that will bypass L1 and go directly to L2?
Show answer
Subject line with severity and concise problem description. Environment section (product version, hardware model, serial number, deployment topology). Problem statement with specific details. Impact section (capacity loss, user count affected). Timeline with UTC timestamps. Troubleshooting already performed. Attachments (core dumps, show-tech output, filtered logs, traffic graphs). Hypothesis. Requested action (confirm known issue, escalate to L3, recommend workaround).2. How should you use case history data as leverage during contract renewal?
Show answer
Document total cases opened, how many required L3 escalation, SLA violations with timestamps, and time-to-resolution metrics. Use this evidence to justify specific asks: "We opened 47 cases last year, 12 required L3 escalation — a named TAM would reduce MTTR significantly." Accumulated SLA violations strengthen your negotiating position for premium support tiers or price concessions.3. What is the four-step process when a vendor violates their SLA?