How to Delegate the Inbox

Why this matters

The inbox is the last thing owners hand over and the single largest recurring drain on their attention. It is not one big task, which is why it never makes the list of things to delegate. It is a hundred small ones spread across the whole day, each individually too fast to bother handing off, and collectively the reason you cannot get through a quote without stopping four times.

It is also the handoff most likely to fail on the first attempt, because it looks like it can be done in one move. It cannot. Done as one move it comes back within a month with damage attached, and after that you will not try again for a year.

The first attempt, and why it failed

A shop owner with five techs and one part-time office person did the obvious thing: gave her the login on a Monday, told her to use her judgment, and went back to work. Three weeks later he took it back. Two customers had been quoted a rate that was not current. A message from a claims adjuster about a water-damage allegation sat for nine days. And she had spent most of the three weeks asking him what to do anyway, so his interruption count went up rather than down.

None of that was her fault. She was handed a mailbox with no categories, no scripts for the questions that repeat, no list of what must never leave his hands, and no defined response standard. She was placed at the last rung of the ladder on day one. Everything below is the procedure that would have worked, in the order it has to happen.

Step 1: Consolidate before you delegate

You cannot hand over five inboxes. Most shops have the shop email, the shop voicemail, texts to the dispatch line, a web form, and the owner's personal cell, which by now is the number half the customer base actually uses.

Get them into one place a second person can see. That usually means a shared mailbox rather than a personal one, a shop line that forwards, and the web form landing in the same shared mailbox. Then change what is published: the number on the truck, on the invoice, in the signature block, and in the listings. Publishing your cell and then complaining that customers use it is not a delegation problem.

The personal cell is the hard part, because you cannot recall it from the two hundred customers who already have it. Do not try. Let it decay: answer from the shop line, sign from the shop address, and when a regular texts your cell, reply once from the cell and add "quickest way to reach us is the shop line, somebody is on it all day." Attrition over months, not a policy announcement.

Skipping consolidation is the most common cause of a bounced handoff. The office person handles the shared mailbox competently while the owner keeps fielding the cell, so the volume never drops and both of them conclude the handoff did not work.

Step 2: Sort one real week into buckets

Take one week of everything that arrived and code each message into one of five buckets. Do it on a real week, not from memory, and do not clean up the week first.

The sort itself is the finding. Almost every owner is surprised by how much of the week is bucket A, and bucket A is the part that needs no judgment at all - it needs a written answer that currently exists only in your head.

Step 3: Write the scripts for the facts

For every recurring bucket A question, write the answer once, in the words you would use. Not a policy document. Four or five sentences each, in a shared file the office person can copy from and edit lightly.

Write them in your voice, including the parts that sound like you. If your answer on the diagnostic charge is "we charge for the trip and the diagnosis, and it comes off the repair if you go ahead the same visit," write that, not a formal restatement of it. The scripts are how your voice survives the handoff, and a customer who notices the tone changed is a customer who thinks they got demoted.

Keep them dated and review them whenever the underlying fact changes. A stale script is the mechanism that produced the wrong-rate quotes in the failed first attempt.

Step 4: Write the never-list and the same-hour list

Two short lists, and they are not the same list.

Never leaves your hands, regardless of how experienced the office person becomes:

• Anything alleging injury, property damage, or a safety condition at a customer site
• Anything from an attorney, an insurer, a regulator, or a licensing body
• Employee pay, discipline, hours disputes, or a complaint about another employee
• Pricing exceptions beyond whatever discount authority you have written down
• A customer who has already complained once and is asking for you by name

Reaches you the same hour, whoever is on the inbox: anything on the never-list above, plus any message describing a live hazard. For hazards the answer is never a reply in the thread. If someone reports a gas odor, the office person calls them immediately and tells them to leave the building right away, not to touch any light switch or appliance, not to use a phone inside, and to call the gas utility emergency line from outside. Water reaching live electrical gets the same treatment: nobody touches anything, leave the area, and the panel gets shut off only if the disconnect is dry and reachable without standing in water. No heat in freezing conditions with an elderly or medically vulnerable occupant is dispatched, not replied to.

Write these on one page and put it where the inbox is worked. A never-list that lives in the owner's head is not a control.

Step 5: Run the graduation ladder

Five rungs. You start at rung 1 and you move one rung at a time.

1. She reads and categorizes. You still handle everything. This rung exists to validate the buckets, and it usually lasts a week.
2. She answers bucket A and C, drafts everything else for you. You send.
3. She answers A, B and C outright. D is still drafted for you.
4. She sends bucket D after you review the draft. The review is a glance, not a rewrite.
5. She sends everything except bucket E, with a periodic sample review rather than a per-message one.

The advance rule, per bucket: move up a rung when, across a rolling sample of 20 consecutive messages in that bucket, you changed the substance of fewer than 2 of them. Substance means the answer, the number, the date, or the commitment. It does not mean wording. Rewriting somebody's phrasing and calling it a correction is how an owner keeps himself at rung 2 for a year.

On the step size: one rung at a time, and if a rung fails the sample, you stay, you do not drop back. Dropping back is what makes it feel like a demotion, and the person stops trying to advance. Failing at rung 3 means rung 3 needs a better rule, not that rung 2 was the ceiling.

Step 6: Set the response standard, and watch three numbers

Commit to a standard and publish it internally: first response within 4 business hours for routine messages, and within 1 hour for anything on the same-hour list. Those are starting points to tune to your market, but pick numbers. "Promptly" is not a standard anyone can be held to or defended by.

Three measures, weekly:

• Messages you personally touched. The whole point. If it is not falling, nothing else matters.
• Median first-response time, across all messages. If it degrades while your touch count falls, you have offloaded a bottleneck onto someone who cannot carry it, and the customer pays for your reclaimed hours.
• Reopen rate: the share of threads that come back because the first answer was wrong or incomplete. Rising reopens means a script is wrong or a rung was advanced too early.

What the numbers looked like

He restarted with the procedure above. The Step 2 sort on one real week came back at 140 inbound messages across all channels:

From his own log, the average message cost him about 4 minutes including getting back to what he had been doing, so 140 messages was about 9.3 owner hours a week. That number is what finally made him restart, because he had been describing the inbox as "twenty minutes in the morning."

At rung 3, he touches two buckets: the 22 quote requests, as drafts he reviews at about 6 minutes each, and the 10 owner-only messages at about 12 minutes each. That is 32 of 140 messages, roughly 23% of the week's volume, and about 4.2 hours a week. He stopped touching 108 of the 140 messages, which is 77% of them, and recovered about 5.1 owner hours a week.

Run that against the advance rule before assuming rung 4 is next. Over the following 20 quote drafts he changed the substance of 4 of them - two where she had used a superseded rate and two where she quoted a scope he would have split. That is 4 in 20, which is at or above the threshold of 2, so rung 4 is not earned. The correct response was not to hover harder. It was to fix the rate sheet the two superseded quotes came from, and to write down the rule about when a job gets split, then re-sample. The next 20 drafts had 1 substantive change, so rung 4 opened.

Note what the measures did in the meantime. Median first response fell, because she was working the inbox continuously and he had been working it in bursts between calls. Reopens went up slightly in the first fortnight, all of them on billing questions, which traced to a script that did not cover partial payments. One script edit closed it.

The ways it quietly comes back

You keep a second inbox. Any channel you did not consolidate becomes the channel everything important arrives on, and within two months you are back to reading everything.

You get copied on everything. Being copied is not delegation, it is delegation with a receipt you still have to read. Ask to be copied on bucket E only, and mean it.

The scripts go stale and nobody owns them. Rates change, the service area changes, a warranty term changes, and the scripts do not. Put a named owner and a review date on the script file. Stale scripts do not fail loudly, they fail as customers quoted something you no longer offer.

A single bad week reverses everything. One mishandled message and the reflex is to take the whole inbox back. Take back the bucket, not the inbox, and only after you have checked whether the rule covering that bucket was actually written down. Most of the time it was not, which makes it your defect, not theirs.

References

• See related: What an Owner Should Stop Doing First
• See related: How to Protect Planning Time When the Phone Keeps Ringing
• See related: The First Office Hire That Buys Back Your Time
• See related: Delegating Without Letting Quality Slip
• Trade-standard practice for customer communication handling in field-service shops