At 11:47 PM on a Thursday in April, one of our client's Stripe checkout integration started returning 502 errors. The on-call person got the alert. Then they froze. Who do you call? What's the first thing to check? Is it Stripe's problem or ours? They spent 40 minutes just figuring out where to start.

That's what happens without a runbook for funnel failures.

Why Most Teams Don't Have a Runbook (and Why That's Dangerous)

I get it. Writing a runbook isn't exciting. Nobody wakes up on Monday morning and says "I can't wait to document our incident response procedures." But the teams that skip this step pay for it during every single outage.

Here's a number that should bother you: the average e-commerce site loses $1,500 per minute of downtime during peak traffic hours, according to Gartner research. If your team spends 40 extra minutes fumbling because nobody wrote down the steps, that's $60,000 in lost revenue. For a single incident.

A runbook for funnel failures cuts that fumbling time down to almost nothing.

What Goes in a Funnel Failure Runbook

Your runbook needs to cover the most common failure scenarios your funnel can experience. Not every edge case. Just the ones that actually happen.

Start with these:

  • Landing page returns a non-200 status code
  • Form submission fails or data doesn't reach CRM
  • Checkout flow throws an error (payment processor, SSL, timeout)
  • Conversion tracking pixel stops firing
  • Page loads but critical elements are missing (CTA button, form, pricing table)

For each scenario, document three things. First: how to confirm the problem is real and not a false alarm. Second: the immediate fix or workaround. Third: who to escalate to if the immediate fix doesn't work.

A Real Example From Our Team

We keep a runbook at FunnelLeaks that I'll partially share. When we get an alert that a client's checkout page is returning errors, here's the first 5 minutes:

Step one: open the page in an incognito browser on desktop and mobile. Is the error visible? Step two: check Stripe's status page. If Stripe is down, it's not our client's problem, but we still notify them so they can pause ads. Step three: if Stripe is fine, check the client's server logs for the checkout endpoint. Look for 500-series errors, database connection failures, or SSL cert issues.

That's it. Three steps. Takes about 4 minutes. Without the runbook, the same person would spend 20 minutes context-switching between tabs trying to remember what to check first.

Keep It Short and Keep It Updated

The worst runbooks I've seen are 40-page documents that nobody reads. Don't do that. Your runbook for funnel failures should be a single page per scenario. Bullet points. Links to the relevant dashboards and admin panels. Phone numbers or Slack handles for the people who can actually fix things.

And update it every time you hit a new failure mode. We had a client whose Cloudflare WAF started blocking legitimate checkout requests after a rule update. That wasn't in our runbook. It is now. Took 5 minutes to add the entry. Next time it happens, the on-call person will know exactly what to check.

Your Future Self Will Thank You

Write the runbook this week. I'm serious. Block 90 minutes on your calendar, sit down with whoever manages your site, and document the five most common funnel failures you've experienced in the past year. Include the fix for each one. Share it with your team.

The next time something breaks at midnight, you'll be glad you did. And if you want automated alerts that actually tell you when these failures happen, FunnelLeaks can help with that part.