You Can't Outsource Accountability

We use a third-party call center because we're not ready to hire full-time staff. That's a legitimate business decision.

What's not legitimate is assuming the accountability transfers with the contract.

Our canary flagged a gap between calls to our Quo number and leads logged in the FMS. We called the number ourselves.

Dead line.

Our vendor had inbound routing to a disconnected number. We caught it the same day. Based on normal call volume we still likely lost 5-10 leads before we did.

They didn't call us. We found it.

Last week was about building canaries. This week is what happens when you actually need one.

A canary proves the line rings. It does not prove the vendor on the other end is doing their job. And it does nothing for you if it lives inside the system you're trying to verify.

Think about how you'd treat any data pipeline you didn't build. You wouldn't deploy it and walk away. You'd instrument it. You'd watch the outputs, alert on anomalies, and verify it's producing what it promised.

A vendor is no different.

Your call center, your third-party manager, your AI answering service — these are all pipelines you don't own or control.

Most operators run them with zero observability. The vendor is performing because they said they would, and you have no reason to think otherwise until a number doesn't add up.

That assumption is where the dead number hides.

The outsourced accountability problem is simple: the person responsible for the failure is no longer the person who feels the pain. When calls die at a number your vendor controls, the complaint loop is cut. Prospects don't call back to tell you they couldn't reach anyone. They just rent somewhere else. The failure shows up later, if at all, as an occupancy number that doesn't explain itself.

This is not a trust problem. Third-party management is a legitimate business decision. For operators running multiple facilities without a dedicated team, it's often the only move that preserves your sanity. The trade-off is verification. When you own a function in-house, you feel the friction directly. A manager who goes to voicemail gets feedback immediately because you're the one watching the reservation count.

When you outsource it, that friction disappears from your daily experience. Problems run quiet until a canary catches them, or until a buyer's due diligence finds a revenue gap you can't fully explain.

Missed calls don't file complaints. They show up as absence. 5-10 leads gone quiet looks exactly like a slow week until you pull the data and see the gap. That number doesn't announce itself. It just stops showing up in your move-in count and you file it under "soft month."

The AI and automation layer makes this more complicated, not simpler. An AI answering service handles after-hours inquiries, logs conversations, and passes off reservations. That raises your floor. Your worst case is better than a facility where nobody picks up at 9pm. That is true. But notice what it assumes: you are watching the output. You are checking that overnight conversations are getting followed up.

The AI assistant does not monitor itself. Neither does the call-center vendor. Neither does the third-party manager. That monitoring falls on you, and it has to run independently of the system you're monitoring.

Every vendor you use is a pipeline you didn't build. Treat it like one. That means call volume logs you pull yourself, not just the manager's report. Answered-rate trends you track independently. A canary comparing the numbers that should match — calls in versus leads logged — routing the alert to your phone, not theirs.

The rule isn't "trust your vendors." The rule is: instrument them. The ones running quietly without observability are the ones that will surprise you. Not because the vendor is bad. Because no system monitors itself.

The facilities that stay off a buyer's problem list treat third-party management as a contracted function with documented accountability, not a delegation that earns its own trust by default. They pull the data. They run the checks. They catch the gap before it becomes a gap they have to explain to someone writing a check.
Some operators build this instrumentation layer themselves. Some don't, and that's exactly where revenue goes quiet before anyone notices.

You can outsource the labor. You can't outsource the audit.

Here's how to instrument your vendor layer properly, using what you already have.

Option 1: Pull your Quo report and build the ratio. Quo exports a full call log CSV: every call, direction, status, facility, timestamp. Download it weekly. Filter for incoming calls. Count answered versus total. That answered-rate ratio, trended week over week in a Google Sheet, is your real signal. A vendor problem shows up as call volume holding steady while answered rate drops. You don't need a dashboard. You need one number that moves.

Option 2: Go real-time with a webhook. The CSV approach works. The webhook approach means you stop checking and start getting notified. Quo supports webhooks, meaning it can push call data to an external URL the moment an event happens. In Make.com, create a new scenario with a Webhook trigger. Make gives you a URL. Paste that into Quo's webhook settings. Now build a filter: incoming call, status missed or unanswered, send a Slack message or SMS. "Facility [NAME] missed a call at [TIME]." The dead number that ran quietly for days becomes a Slack message within seconds of the first missed call.

Option 3: Add the mystery shop. Automation tells you the line rang. It does not tell you the person who answered could actually rent a unit. Once a week, call the facility yourself or have a VA do it. Log the result in the same Google Sheet: date, facility, answered or not, reached someone who could close a tenant. Two minutes. The ratio tells you the trend. The mystery shop tells you what's behind it.

I write a lot about operations and monitoring. I'm curious what actually lands.

If you built one thing from a recent issue what was it?

The Quo ratio, the webhook alert, the mystery shop call, something else entirely?

Hit reply and tell me. I read every one.

— Epictetus