You'll work directly with me.
No account managers or ticket queues. When you contact Linchpin, you're talking to the person who built and configured your receptionist.
I'm Daniel Lowe.
I'm based in Midland, Michigan, and I personally handle every part of each Linchpin setup. I learn how your business handles calls, build the call flow around your actual policies, connect the systems it needs, test realistic scenarios, launch it, review how it performs, and make adjustments afterward.
Every receptionist is built around the business it answers for. It isn't handed a generic script with your company name added to it.
Why I built Linchpin
My father once called a plumber to have a backflow preventer installed. After sitting on hold for about ten minutes, he hung up and called the next business on Google.
The first plumber didn't lose that job because of their pricing or the quality of their work. They lost it because nobody was available to answer.
Built from real calls
Chain Reaction Bike Repair
For Chain Reaction Bike Repair, I built a receptionist that answers maintenance calls while the owner works another job. It knows what the shop services, refuses requests the shop can't take, gathers the details Carston needs, and helps customers without requiring him to stop what he's doing.
Michigan Rental
For Michigan Rental, I'm building a different system around an entirely different business. It answers general questions, searches current property listings based on what a caller wants, and sends the relevant information to office staff.
One business at a time
That's how Linchpin works: each system is built around the business rather than forcing the business into a template.
In just one month, I estimate it helped me keep more than 10 customers I otherwise would have lost to missed calls.
What you're actually buying
Linchpin runs on proven voice infrastructure: Retell AI handles the calls, and Stripe handles billing. I'm not asking you to bet on experimental technology.
What I do is the part that actually matters for your business: understanding your policies, designing the call flow, setting transfer and escalation rules, connecting other systems, testing realistic calls, and continuing to improve it after launch. Routine adjustments are included for as long as you subscribe. If your hours, services, transfer numbers, or call-handling rules change, I'll update the system.
What happens when something goes wrong
Forwarding your business line to anyone is handing over a single point of failure. Here is how I handle that.
You reach me, not a queue
Support comes to my inbox, and I'm the person who built the system. There is no diagnosis relay between you and the fix.
Every call is on the record
Calls are captured in recordings and transcripts, so mistakes are visible instead of argued about. When one shows up, I adjust the call flow and you see exactly what changed.
Your exit is easy
Cancel with 15 days' written notice. Turning off forwarding is one carrier command, and I'll walk you through it. Your number stays yours the entire time.
You remain in control.
You keep control of your existing business number. In most cases, Linchpin works through call forwarding, so you don't have to give up the number your customers already know.
During setup, you decide which calls the receptionist should handle, refuse, record for follow-up, or immediately transfer to a person. Sensitive or judgment-heavy situations can always be routed according to your rules.
What Linchpin is not
Linchpin is not an unlimited AI employee. It should not improvise safety advice, make judgment-heavy decisions, or pretend it can handle situations that belong with a person.
Its job is narrower and more useful: answer consistently, follow the rules established with you, collect the right information, help with routine requests, and connect callers to a person when necessary.