Front of Shop

Hiring the first office person: a day-one SOP

A practical test for when to hire the first CSR or office person, plus a day-one SOP covering phones, the lead log, scheduling, and a clean handover from the owner.

There is a point, in a lot of 1–3 person shops, when the work is there and the phone is the problem. You are on a job, the cell is buzzing, a form came in at lunch, and tonight you will return calls from the driveway. Some of those calls will wait until tomorrow. Some of those people will not.

Hiring the first office person is how you buy back that attention. It is also how you can create a new mess if you hire someone, hand them a dead inbox, and disappear onto a roof with no rules. This is about when to hire, and what they should own on day one.

When it is time

You do not need a perfect formula. You need a few weeks of honest signs. Look at your own log, not a national benchmark.

  • You are regularly missing calls during posted hours, or returning them the next day, and you can see it in the missed-call numbers.
  • The same-day follow-up floor is slipping on ordinary Tuesdays, not only on storm days. That floor is a human response the same business day.
  • Scheduling is living in your head, and techs are getting stacked windows you cannot defend.
  • You are doing office work after dinner most nights, and it is still behind.
  • A spouse or helper is already unofficially answering the phone, and it is costing the relationship or the quality of the answers.

If two or three of those are true for a month, it is reasonable to hire help, even part time, even for the busiest hours only (late morning through mid-afternoon is a common first slice). You do not have to staff a full front desk from day one. You do have to know what the hours are, and who owns the phone when that person is not there. The owner still owns leftovers. There is no rotating coverage chart that magically appears with the hire.

What the first office person owns on day one

Keep the first week small. They should leave day one able to do these things, even if they are slower than you:

  1. Answer the shop line during their posted hours, or pick up the ones they can and log the misses.
  2. Work the shared intake log: new rows, first attempts, next steps.
  3. Schedule jobs inside the rules you wrote (windows, buffers, what they may book without asking you).
  4. Take a message they cannot resolve, and get it to you in a way you will actually see at the next break.
  5. Know what is an emergency, what waits until open, and what they must never promise.

They should not, on day one, invent prices, change the scope of a job, or argue a review. Those come later, or stay with you.

Write a one-page handover. If it is not written, it is not handed over. A verbal tour of "you'll figure it out" is how they learn by disappointing a customer.

A one-page day-one SOP

Hours they cover: ________

Number they answer, and where it rings when they are out: ________

The lead log lives here: ________

Time standard for new inquiries during their hours: a first human attempt the same business day, ideally in the current callback block, leftovers at the end of their shift or at open.

Pricing they may quote without you: ________ (example: "published service call only; no repairs, no installs")

Jobs they may book without asking: ________ (example: "maintenance in open windows on the board")

Jobs they must park for you: ________ (example: "anything over $X, any warranty dispute, any emergency dispatch")

After-hours message and morning list: who works it, and at what time. See after-hours coverage if that path is still fuzzy.

Texts: only to people who opted in, with a clear STOP opt-out. Practical caution, not legal advice.

How they reach you on a job, and when not to: a short text for true blocks, not a play-by-play of every call.

How the owner has to change

This is the part shops skip. If you hire someone and keep every call forwarded to your cell, you did not hire an office person. You hired an expensive witness.

During their hours, the shop line should ring where they are. You can get a summary at the next break, or a text when something needs you. You should not be the secret receptionist.

You also have to be available for the park-for-you list at known times. A 15-minute window at lunch and a short window at the end of their shift is more realistic than "call me anytime, I'll pick up." If you never pick up, they will start guessing, and guessing is how prices and promises drift.

Plan a five-day shadow if you can: they listen, then they take the call while you listen, then they take it alone and you review the log together at the end of the day. A longer training checklist can wait for a first-week CSR piece. Day one is ownership and boundaries.

What to look for in the person, briefly

You want someone calm on the phone, willing to write things down, and comfortable saying "I will find out" instead of inventing an answer. Trade experience is a bonus, not a requirement, if the SOP is clear. Hiring a relative is fine if you will still write the rules and still review the log. It is not fine if the rules will feel too awkward to enforce.

Pay and hours have to be real for your market and your cash. Do not staff forty hours because a blog said a "real company" has a full-time CSR. Staff the hours that are leaking.

What we would do in a 1–20 person shop

We would spend two weeks tightening the log and the same-day floor before we posted the job. If the leaks were still there, we would hire part-time hours first, write the one-page SOP, and move the shop line during those hours. The owner would keep a twice-a-day check-in and the park-for-you list, and would not vanish for a week.

After a month we would look at missed-call counts, leftover leads, and whether the owner was still doing office work after dinner. If nothing moved, the problem is the handover, not the idea of hiring. We would fix the SOP before we added hours.

This article was drafted with AI assistance and reviewed by AuraGrid Labs editorial. Front of Shop is published by AuraGrid Labs LLC.

Front of Shop is published by AuraGrid Labs LLC, which sells software for small businesses. Drafts may be prepared with AI assistance; a person reviews every article before it is published. How we work · Disclosure policy