I answered my own phone for a week

Before I built a system to answer business phones, I spent a week answering one.

A contractor I know was losing calls and agreed to forward his line to me during the day. I took notes on every call. Forty-one calls in five working days.

Here is what they were.

Nineteen were people asking whether he covered their area and roughly what something cost. Every one of those conversations was under ninety seconds and followed the same shape.

Eight were suppliers, scheduling, or somebody he already knew.

Seven were sales calls. Insurance, SEO, a man extremely confident about Google listings.

Five were people who wanted to book, and knew what they wanted, and just needed a time.

Two were genuinely complicated. A structural question and an insurance job. Those needed him, in detail, for a while.

So: two calls out of forty-one actually required the expert. Thirty-nine required somebody who could answer politely, capture a name and number, and know which trades he covers.

That is the entire case for putting an agent on a phone line, and it is much narrower than the way it is usually sold. The pitch is normally that AI will handle your customers. It will not. It will handle the nineteen calls that are the same nineteen questions, capture the five bookings, screen the seven sales calls, and hand you the two that need you, with a transcript, so you are walking into them informed.

The other thing the week taught me: the caller almost never minded a wait, and always minded a voicemail. A recording that says leave a message is a closed door. Somebody picking up, even to say he is on a job and will call you at four, keeps the job.

That is what I built toward. Not a replacement. A thing that picks up.