Service & Communication

The Laws

1. 23

   Serve the need they haven't said yet

   The best move: you never have to ask. We already saw it coming.

   If you have to ask, we were already too slow.

   Why it matters

   If you have to ask us to notice a problem, we've already lost a bit of your trust, even before we fix anything. The real value of a Google Ads partner isn't fast answers. It's catching things before you ask at all. Spend jumps. A competitor moves. A product runs out of stock. You should hear it from us first, not find it on your own dashboard. Wait to be asked, and we're just a vendor. Speak first, and we're the team you hand the keys to and stop worrying about. This can't live in one person's memory. It has to be a system every account runs on, so it holds true even when someone is out sick or on holiday.

   The Ritz-Carlton experience enlivens the senses, instills well-being, and fulfills even the unexpressed wishes and needs of our guests.

   The lesson

   Anticipation is not luck or a good memory. It is a system, and it needs three things: a place to write down what we learn about your account, so it never lives in just one person's head. A daily habit of checking for warning signs before you ever have to raise them. And a rule that says if we see something, we say something, straight away. Speed doesn't come from trying harder. It comes from building the job so noticing early is just how it works.

   How we do it

   1. 01We build a living brief on your account: what normal spend looks like, your risk tolerance, your busy seasons, your top competitors, and what matters most to you.
   2. 02We check your account against that baseline every day, not once a week. Anything unusual, spend, competitors, feed issues, a seasonal shift, gets flagged the same day it happens.
   3. 03We decide in minutes, not days, whether you need a heads up right away or it can wait for the weekly update. Real problems never wait.
   4. 04We message you before you log in and notice it yourself.
   5. 05We log every early catch, so the whole team can see the pattern of what we caught before you had to ask.

   How you’ll know we hit it

   We track how many issues we catch and tell you about before you ask, against how many you had to raise yourself. The first number should keep growing. The second should shrink toward zero.

2. 24

   Fast, and one clear owner

   Speed only counts if someone is actually holding the ball.

   Every issue gets one name and a clock, the second it lands.

   Why it matters

   You don't feel cared for because our average response time looks good on some internal report. You feel cared for because the first reply is fast, and you know exactly who is handling it. The fastest way to lose trust isn't a slow answer. It's a message that sits there, or worse, one that three people answer because everyone assumed someone else had it. We run a lot of accounts with a small team, so we can't afford any doubt about who owns what. Speed without an owner is just chaos in a nice outfit. An owner without speed is just bureaucracy with a name on it. You need both, every time.

   The lesson

   Zappos' longest recorded customer service call ran over ten hours. Tony Hsieh wore it as a badge: nobody was watching the clock, someone was taking care of a customer. There are two ways this breaks, and you have to fix both. One is ownership: a problem can quietly become "someone else's job" if nobody's name is attached to it. The other is fake speed: things like reply time can look great on a dashboard while the actual problem never gets solved. Here's the fix. Give every issue one name the second it appears, then judge speed by whether it actually got fixed, never by how fast someone typed a reply.

   How we do it

   1. 01Every message you send us, on Slack, email, or the dashboard, gets answered. Our bar is a first reply within the hour during business hours. Hard questions get a real answer the same business day.
   2. 02One name gets attached to your issue the moment it's flagged. Never "the team." Never "someone will look into it."
   3. 03If that person can't fix it alone, they escalate it straight to a named senior person, fast and specific, not a vague "can someone help."
   4. 04We measure speed by whether your problem actually got solved, not by how fast we replied. A quick "we're on it" that goes nowhere is worse than a slightly slower message with the real fix.
   5. 05Every escalation ends with a message back to you confirming it's done, not just handed off and forgotten.

   How you’ll know we hit it

   We track first-reply time on every issue, and how often one name owns it start to finish, against how often something gets passed around before anyone actually closes it out.

3. 25

   Empower the front line

   The person closest to the problem should be the one who can fix it, on the spot.

   The person who sees the problem is the person who fixes it, without waiting for permission.

   Why it matters

   Every extra layer of approval between a problem and a fix is a delay you feel. If someone on our team sees something wrong and has to wait for a manager's sign off, you wait too, and you notice. Empowering the front line doesn't mean being reckless with your money or your account. It means we trust the person looking at the problem to fix it, inside clear limits we set in advance, so nobody on our side has to guess how much they're allowed to do.

   In all our interactions with our guests, customers, business associates and colleagues, we seek to deal with others as we would have them deal with us.

   The lesson

   The shape is always the same: a clear line, drawn in advance, and inside that line the person closest to the problem doesn't need permission to act. That doesn't mean no rules at all. It means the everyday stuff gets fixed the moment it's spotted, and escalation gets saved for the genuinely unusual.

   How we do it

   1. 01Any team member can pause a campaign the second they spot a clear problem, a broken feed, a spend spike, a tracking failure, with no sign off needed. We explain it to you after, not before.
   2. 02Anyone on the team can make a goodwill call on their own judgment, on the spot. Nobody waits for permission to make something right.
   3. 03The bigger the call, the more senior the owner. Big calls go straight to a named senior person, fast, never slow.
   4. 04You never wait on hold for someone else's approval to hear "yes, we'll fix this."
   5. 05Every use of this authority gets logged on your account, so the team can see the pattern of good calls being made.

   How you’ll know we hit it

   We track how often a team member solves your problem on the spot within the pre-set limits, against how often something that should've been fixed same-day got stuck waiting for approval instead.

4. 26

   Own the failure, then go one step further

   When we mess up, we say so first, fix it fast, and then do more than just fixing it.

   When we mess up, you hear it from us first, the same day, with the real number, and we do something extra on top of the fix.

   Why it matters

   We manage real money for your business. Mistakes will happen: a budget cap set wrong, a campaign paused by accident, a tracking pixel that breaks, a negative keyword that blocks real buyers. That's just math. Run enough accounts, make enough changes, and something will go wrong somewhere this year. You won't judge us on whether we're perfect. You'll judge us on whether we tell you the truth fast, or whether you find out from your own dashboard before we say a word. A mistake we own and fix fast can build more trust than three quiet months of good results. A mistake we hide, even a small one, can end things the day it surfaces. Not because of the money, but because it proves we can't be trusted to tell the truth.

   The lesson

   Ritz-Carlton's five recovery steps, as Michelli documents them: react with genuine compassion, apologize properly, take care of it, make it right, then follow up (after Joseph A. Michelli, The New Gold Standard). Whoever spots the mistake owns it. They don't pass it up the chain and hope someone else has the hard conversation. The follow-up has to close fast too, checking back to confirm the fix actually held, not weeks later. The real rule underneath it all: speed of telling the truth beats the size of the mistake. A mistake we tell you about the same day builds more trust than a smaller one you find out about three weeks later on your own.

   How we do it

   1. 01Whoever finds the mistake owns it. No forwarding it to someone else and hoping they'll handle telling you.
   2. 02We react like it's real, because it is. No hedging, no "might have been an issue." We say what happened in plain words.
   3. 03We tell you before you ask, with the real impact. If we don't have every number yet, we say what we know now and when we'll have the rest.
   4. 04We fix it and show you the fix, not just promise it. A screenshot of the corrected setting, the restored campaign, the fixed tracking tag.
   5. 05We go one step further. Once the fix is confirmed, we do something extra that wasn't required. We check anything nearby that could carry the same risk. We run an extra pass of optimization. We follow up the next week to confirm it held.

   How you’ll know we hit it

   We track how often we catch our own mistake first, versus how often you catch it first. The target: every single one, caught and told by us, the same day it's found. Zero client-caught misses.

5. 27

   Remember them like they are the only one

   Every client should feel like our only account, even though we run a full book of them.

   If you have to repeat yourself, we already failed.

   Why it matters

   We're a small team, so there's no way we hold the full history of every client in our heads. But you don't care about our headcount. If you have to re-explain what you told us last month, or repeat a preference we should already know, you start to feel like a ticket number, not a partner. That feeling is what makes someone start looking at other agencies, long before results ever slip. What we can offer instead is real depth: knowing your history, what we already tried, what already failed, better than any competitor pitching you this week ever could. That only works if it's a system, not something we hope a busy account manager remembers.

   The lesson

   None of this can depend on one person's memory. We write it down in one shared place, every time, so it survives beyond one shift or one person. Memory has to be infrastructure the business owns, not something living in one person's head that might forget, quit, or go on holiday.

   How we do it

   1. 01One record for your account. Not scattered across five Slack threads and someone's memory, one place, always current.
   2. 02We log it the moment it happens. A preference, a past mistake and its fix, something you told us you hate, written down the same day, not reconstructed later from memory.
   3. 03We open every conversation with context, not a blank slate. We reference what we already know instead of asking you to repeat it.
   4. 04Hand-offs carry the full record. If your account manager is out, whoever covers reads the record first and never says "let me get up to speed" to you.
   5. 05We update it after every meaningful touch, not just after problems. Wins, preferences, offhand comments about what you care about, all of it goes in.

   How you’ll know we hit it

   We track how many conversations start cold, with you re-explaining something we should already know, against how many open with context we already had. The target is zero cold starts. Anyone covering for a teammate should be able to answer you well within minutes of opening the record.