About
Built for locksmiths. Nothing else.
LeadLatch is not a general answering service with a locksmith setting bolted on. The whole thing is shaped around one trade, because the decision a locksmith has to make on a call is not the same decision a plumber makes.
Why it exists
The job is decided before you pick up.
A locksmith’s phone rings when someone is standing outside their own house at one in the morning. They call the first three numbers they find and they go with whoever answers. If you are under a dashboard or up a ladder, you never even know the call happened.
The software that exists for this mostly answers the phone and takes a message. That is the easy half. The hard half is deciding whether the job is worth the drive at all, and that decision depends on something almost nobody computes: how long it actually takes to get there, on real roads, at the hour the phone is ringing.
That is the piece LeadLatch is built around. Everything else on the call exists to serve it.
Where we are
Early, and saying so.
LeadLatch is taking on its first shops now. There are no testimonials on this site because there are no customers to quote yet, and inventing some would tell you everything you need to know about how the rest of it would be run.
What that means for you, practically: you would be early. You get a person on the phone rather than a support queue, and your feedback changes the product rather than joining a backlog. You also get something less finished than it will be in a year.
Both of those are true at once, and you should weigh them.
How it is built
The rules it is built on.
The model never decides a number
Prices, service area and open slots come from your settings, fetched by code. The model is handed the answer and told to say it. It is not trusted with arithmetic that costs you money.
Drive time is never estimated
Not a radius, not a straight line, not a guess. A routing engine returns the real driving time door to door, and that is what decides the job.
Nothing is claimed that is not built
This site describes what the product does today, not what is on the roadmap. Where something is coming rather than finished, it says so.
Come and test it.
The fastest way to judge any of this is to try to break it. Book a demo and do your worst.