Will’s Take is editorial perspective — opinion, future-casting, and industry observation from Will Tygart. Not analysis. Not client work. Just how I see it.
Every service business I’ve ever worked with runs on the same infrastructure at its core.
The phone call.
Not a CRM. Not a ticketing system. Not a scheduling platform. Those things exist and they’re used. But the actual transaction — the one that matters, the one where something gets committed — starts with a phone call. Or ends with one. Or gets unstuck by one.
The phone call is how trust gets established, scope gets negotiated, authorization gets captured, and relationships get maintained. It’s load-bearing infrastructure for industries that have never had to think about it that way because nothing has ever threatened to replace it.
UCP threatens to replace it. And the industries that understand that first are going to move very differently than the ones that don’t.
Think about what a phone call actually does in a service transaction.
It’s not just information transfer. That’s the naive read. If it were just information transfer, email would have replaced it years ago.
A phone call does something email and forms and portals can’t do cleanly: it establishes mutual presence. Both parties are there, in real time, committed to the interaction. That presence creates a soft accountability — you said what you said, I heard it, we both know the exchange happened. It’s a handshake with audio.
It also carries signal that text can’t. Hesitation. Confidence. The slight change in tone when someone isn’t sure about something. The speed of a yes that tells you they’re comfortable versus the speed of a yes that tells you they’re not. Twenty years of sales and service experience lives in that signal and none of it transfers to a contact form.
And it’s flexible in a way that structured data entry isn’t. The homeowner who calls about water damage doesn’t know the right categories. They know their basement is wet and they’re scared. The intake conversation shapes the scope. The contractor’s questions organize the chaos into something actionable. That’s not form completion — that’s collaborative sense-making.
Agents can do more of that than people think. But not all of it. Not yet.
The information transfer part — hours, availability, pricing tiers, service area, intake requirements — that’s fully replaceable today. That’s a capability profile. That’s UCP doing exactly what it’s designed to do.
The flexible sense-making part — helping a panicked homeowner understand what they’re dealing with — that’s getting there. Conversational AI is genuinely good at this now and getting better fast. The gap between a skilled intake agent and a well-designed AI intake flow is closing faster than most operators realize.
The presence and accountability part — that’s the hard one. The mutual commitment that a real-time voice exchange creates isn’t easily replicated by an asynchronous agent interaction. When an agent books an appointment on your behalf, something is lost in terms of the felt sense of agreement. Nobody said yes out loud. Nobody heard the other party confirm. The commitment happened in a log file somewhere.
That gap matters more in some industries than others. A pizza order doesn’t need presence. A contractor coming into your home to assess damage to your most valuable asset — that’s a different situation.
The phone call will die in layers, not all at once.
The first layer to go is outbound scheduling and status. Confirmation calls, reminder calls, update calls, “we’re on our way” calls. Agents eat all of that immediately and nobody misses it. The contractor doesn’t miss making those calls. The customer doesn’t miss receiving them.
The second layer is inbound intake for straightforward transactions. Standard service requests with known parameters. Agents handle that too and handle it well. Faster than a human, available at 2am, never puts you on hold.
The third layer — the complex intake, the scope negotiation, the relationship maintenance call — that’s where it gets slow. That’s where the phone holds on longest. Not because voice is inherently superior but because the accountability and presence infrastructure hasn’t been built into the agent layer yet.
UCP can carry the transaction data. What it can’t yet carry is the felt weight of a commitment made between two people in real time.
Here’s what I tell operators in these industries.
Stop defending the phone call as a relationship tool and start asking which parts of it are actually doing relationship work versus which parts are just inefficient information transfer wearing relationship clothing.
The status update call isn’t relationship work. It’s a notification with social overhead. Kill it.
The intake call for a routine job isn’t relationship work. It’s structured data collection with a human interface. Systematize it.
The call where you walk a client through a complicated scope, manage their anxiety, negotiate authorization, and set realistic expectations — that’s relationship work. Protect it. Get better at it. Because when the routine calls are gone, that’s all that’s left and it better be worth the rate you’re charging.
The phone call is the last legacy protocol. But it’s not going to zero.
It’s going to the top of the value stack, where it always should have been.
Leave a Reply