A shared inbox should mean faster replies. Without clear rules it usually means nobody replies. Here is the response SLA per channel, the claim-the-thread protocol, and a weekly 10-minute audit that keeps everyone honest.
System 2 from the Leveraged Owner Starter Pack
Thursday, 2:14pm. A homeowner texts your business number asking about a water heater quote. Your office manager sees the preview pop up on the shared screen and figures your dispatcher is on it. Your dispatcher sees it too, and figures the office manager will grab it. At 4:45pm, nobody has replied. The homeowner texts your competitor, who answers in six minutes. By Friday morning the job is sold, the truck is scheduled, and your inbox still shows the thread sitting there, read, untouched, owned by no one.
That is the paradox of the shared inbox. One inbox, three people watching it, and somehow the thread dies in broad daylight. The tool is not the problem. The missing piece is a service level agreement, or SLA: a written promise about who replies to what, how fast, and what happens when nobody does.
This is a Pillar A "Capture Every Lead" system for a reason. A Pillar A "Capture Every Lead" system only works if someone is actually standing behind it. If you have not yet set up the foundation, start with the complete guide to missed-call text-back and read Speed to Lead: Why the First Contractor to Respond Wins the Job next. Speed is the weapon. The SLA is how you aim it.
Every shared inbox runs on an unspoken rule: if everyone can reply, someone will. That rule is a fantasy. In practice, responsibility spreads out until it belongs to no one. Office staff assume the dispatcher saw it. The dispatcher assumes the CSR grabbed it. The owner assumes everyone is busy doing their jobs and the inbox is fine. Nobody is lying. Everybody is wrong.
The damage is real and measurable. Responding within 5 minutes makes you 21x more likely to qualify a lead and roughly 100x more likely to actually reach the contact, compared to waiting 30 minutes (MIT/Oldroyd, published in Harvard Business Review 2011). Meanwhile, the typical business takes 42 to 47 hours to respond to an inbound lead (2026 benchmark studies of 250K+ inbound leads; HBR's 2011 audit of 2,241 companies found the same 42-hour average). A shared inbox with no SLA puts you right in the middle of that 42-hour pack. The whole point of Pillar A is to get you out of it.
Concrete takeaway: a shared inbox is a tool, not a system. The system is the written agreement about who replies and by when. Without it, you have three people watching the same thread drown.
An SLA is a service level agreement: a written commitment that every new message gets a human reply within a defined number of minutes, depending on the channel it came through and the hour it arrived. It is not a vibe. It is not "we try to answer fast." It is numbers, names, and consequences.
A working SLA has exactly three parts:
Notice what is not on the list: any particular software. An SLA is a human agreement first. The tools just make it harder to cheat.
Concrete takeaway: if your response policy cannot be printed on one page and taped above the desk, you do not have one.
Not all channels are equal. A text is a conversation happening now. An email is a conversation happening sometime this week. Your SLA should reflect that, or people will treat everything like email. Here is a starting table. Adjust the numbers to your staffing, but never leave a cell blank:
| Channel | Business hours | After hours | Default owner |
|---|---|---|---|
| Inbound text | 5 minutes | 15 minutes | On-duty dispatcher |
| Missed-call callback | 5 minutes (automated text-back fires instantly) | Next business morning | CSR on call |
| 2 hours | Next business morning | Office manager | |
| Facebook message | 15 minutes | Next business morning | CSR on call |
Two notes on these numbers. First, the 5-minute text promise is not arbitrary: responding within an hour makes you 7x more likely to qualify a lead (Harvard Business Review, 2011). Second, after-hours numbers only work if your text-back automation covers the gap, which is what after-hours lead capture is built for. The SLA sets the promise. Automation keeps it while you sleep.
Concrete takeaway: print this table, fill in the owner names, and pin it where the team works. An SLA in your head is a wish.
Speed without ownership is chaos. The fix is a claim protocol with one hard rule: a thread is not being handled until someone visibly claims it. Reading is not owning. Owning means you put your name on it in a way everyone else can see.
The protocol works like this:
This kills the two failure modes: the double-reply (two people answering the same thread, which looks sloppy) and the no-reply (everyone assuming someone else has it). One owner per thread, visible to all, until resolution.
Copy-paste claim note (internal)
"Claimed by [Your Name] at [Time]. Customer [First Name] asked about [topic]. I replied at [Time]. Next step: [booking/estimate/callback] by [date]."
Copy-paste handoff note (to the team)
"Handing off to [Teammate Name]: customer [First Name] needs [reason]. I told them you will reach out by [time]. Confirmed receipt?"
Concrete takeaway: "claimed" must be visible in the tool or the message history. If it only exists in someone's head, the thread is unowned.
A rule without a consequence is a suggestion. Write the escalation ladder before you need it, so the first broken SLA does not turn into a debate about what "breaks" means.
The shared miss log matters most. After a month, patterns appear: texts arriving at 12:15pm during lunch coverage get missed, or one CSR handles 70% of the thread volume. Those are staffing problems wearing the costume of individual failures.
Concrete takeaway: every miss gets logged with a cause. Within a month the log will tell you whether you have a people problem, a coverage problem, or a volume problem.
The SLA only survives if someone checks the score. Once a week, ten minutes, same time, owner of the shop or the office lead. Pull the week's threads and score five things:
Score it on a simple sheet. Five checks, pass or fail each, note the action. Ten minutes. The moment the audit stops, the SLA becomes decoration.
Example: A two-truck HVAC shop in Jackson runs the audit every Monday at 8:10am. In week one, first-response compliance is 61% and 14 threads were never claimed. By week six, compliance is 94% and unclaimed threads are down to one, because the office lead started reassigning orphans on the spot. Nothing changed about the team. The only thing that changed was that somebody was watching.
Concrete takeaway: the audit is the product. The SLA is just the spec. Put the ten minutes on the calendar before you publish the table.
You do not need new software for any of this. If you run a field service management software (FSM, the scheduling and dispatch tool most contractors use) or a CRM (customer relationship management software) with a shared inbox, you already have the pieces:
One compliance note before you touch any of this: business texting runs on A2P 10DLC rules. A2P (application-to-person) registration through 10DLC (the ten-digit long code system for business texting) is required before you send business texts, approval typically takes 1-7 days and costs roughly $15-$20 one-time. Put opt-out language in your first text, and respect TCPA quiet hours: no marketing texts before 8am or after 9pm in the recipient's local time. This is general information, not legal advice, but it is the kind of detail that keeps your number out of trouble.
Write the SLA, the claim rules, and the escalation ladder into one SOP (standard operating procedure) document. One page for the table, one page for the rules, one page for the audit checklist. New hire onboarding takes twenty minutes: read it, shadow it, claim your first thread.
Concrete takeaway: use the tools you already pay for, and put the whole system on three printed pages. Complexity is where SLAs go to die.
Run your own math once and the SLA will never feel optional again. A missed hot thread is a missed job. The illustrative lost-revenue-per-missed-call range of $275-$1,200 (not a promise, plug in your own average job value) means one dropped thread per week costs you somewhere between fourteen thousand and sixty thousand dollars a year. You do not need to hit those numbers exactly. You need to multiply your average ticket by your weekly miss count and look at the result.
That is what the SLA buys: not manners, not appearances. Revenue that was already calling you.
This post is part of Pillar A, Capture Every Lead, and System 2 of the Leveraged Owner Starter Pack. Read How to Set Up Missed-Call Text-Back for Your Contracting Business to build the automation layer that backs up every promise on the SLA table, and Speed to Lead: Why the First Contractor to Respond Wins the Job for the research behind the five-minute rule. For keeping those fast replies coming after hours, see After-Hours Lead Capture: Never Lose Another Night or Weekend Lead.
The full setup SOP, all four copy-paste scripts (including the owner notification), the "Your Numbers" missed-call worksheet, and the step-by-step setup guide — free, no catch. Fix your missed calls this week.
Free. The full 8-system Starter Pack is $27 if you want everything else.
This post is System 2 from the Leveraged Owner Starter Pack — the done-for-you version with the full step-by-step SOP, every script, the worksheets, and screen-by-screen setup instructions for all 8 systems.
Stats sourced as labeled: 27% of inbound calls unanswered (Invoca call-analytics research); 21x qualification lift and ~100x contact reach within 5 minutes (MIT/Oldroyd, Harvard Business Review 2011); typical business takes 42-47 hours to respond (2026 benchmark studies of 250K+ inbound leads; HBR's 2011 audit of 2,241 companies); responding within an hour is 7x more likely to qualify a lead (Harvard Business Review, 2011); $275-$1,200 lost-revenue-per-missed-call figure is illustrative, not a promise — plug in your own average job value.
Related guides from the Leveraged Owner blog:
10DLC registration in plain English for contractors: brand and campaign registration steps, the 1–7 day timeline, $15–$20 cost, and rejection mistakes to avoid.
Business texts going to spam? The contractor’s troubleshooting guide: 10DLC status, carrier filtering, opt-out wording, number reputation — diagnosed in order.
What is review gating? Why filtering unhappy customers before the review ask violates Google policy — and the compliant system that gets more 5-stars instead.