Foreword

The business phone call is a request for work that reaches a small business in real time, usually while the owner is out doing the job the last caller booked. For an owner-operator who answers their own phone, that call has no front desk behind it. It rings on a lawn in the middle of a tent install and on the kitchen counter at nine at night.

The business phone call has a few fixed properties, and each one can be counted. One person can hold one call at a time, so the second caller in a busy hour gets voicemail. A caller who reaches nobody tends to try the next company instead of waiting. The callback is a separate job from the first ring, with its own clock. Calls keep coming after hours and all through the busy season, when the owner is either off or on site. And a call can be answered and still fail, because the change the customer asked for never makes it onto the order.

Automation is the second subject, and it gets the same plain accounting. Software can pick up a call, take down a name and a date, send a text and pass the details to the owner. It gives time back only when the steps of a job are written down first and the owner approves anything before it goes out to a customer. On a phone line it also has rules to follow. It has to disclose itself and get consent where the law requires it, and it has to say it does not know an answer instead of guessing one.

Connor Gallic comes to the subject as a marketer who became a builder. He grew up in a family of entrepreneurs who never had enough time and rarely had the margin to hire help. His working life ran through social media marketing, marketing for eighteen car dealerships in New Jersey, a telemedicine company his father had started, and a player-to-player marketplace inside a video game. The phone came later. His father's tent company had a missed-call problem, and his father called to ask how to use the AI answering companies he kept seeing. Connor found them weak at the time and started building his own as the technology improved. He now runs his own business mostly through automated systems he set up himself, so the automation chapters read like someone describing tools he uses every week.

The book is drawn from Connor's own recorded conversations about the calls and systems he works with: interviews about his career and the family business that started the work, and shorter recordings made while he explained missed calls and what an automated line should and should not do. Every quotation in these pages is his.

The chapters come in two parts. Part One stays on the phone itself. It opens on the owner's own money in What a Missed Call Costs You, then works through the free fixes, the callback, after-hours calls and the gap between an answered call and a changed order, and it closes on a weekly count an owner can keep on a whiteboard. Part Two turns to AI and automation in the same order: the hours spent doing everything by hand, why automation stalls in a small business, which calls should stay with a human voice, and how to prove an automated step paid for itself. A last chapter puts both parts into one week of work, in order.

Some chapters carry more weight than others. What a Missed Call Costs You comes first because every later page assumes the owner has put a number on the calls already going unanswered. Calling Back Before They Call Someone Else takes up how fast a missed caller needs to hear back and which calls to return first. Ground Rules for AI on Your Phone Line sets out what an automated line has to tell callers and what it should never send without the owner's sign-off.

Nothing in the book tells a rental owner how to stake a tent or a contractor how to price a job. It stays on the phone and the systems around it, the part of a small business Connor works on every day. The owner stays the expert on everything else.

Read it with last week's call log open. The phone will ring again before the first chapter is over.