It's 11:15am and your van is parked in a customer's office lot, a fresh windshield you just set still curing — the van has to stay put and nothing can bump that glass until the adhesive reaches a safe strength. Your phone buzzes twice while you wait it out. The first voicemail is from someone whose "small" crack from yesterday now runs corner to corner across their line of sight, asking if their insurance covers it and how fast you can get there. The second is a text from someone else asking if a chip the size of a pencil eraser is even worth fixing before it spreads. Neither call needed you to leave the curing windshield — but neither one waits for a callback either. Here's what's safe to hand off about that first call, and what still needs you on the phone.
Most calls to an auto glass shop aren't a booked job yet — they're someone trying to figure out whether their chip needs a $60 repair or a $400 replacement, whether their insurance actually covers it, and how soon a mobile technician can reach them. A system can answer the informational part of that honestly, using your real pricing, your real mobile schedule, and the insurers you actually work with, then text back a rough answer and your next opening the moment it has enough information. What it can't do: tell someone their specific crack is safe to keep driving on, or promise their deductible is $0 without their insurer confirming it.
Before anything else: when this guide says AI agent, it means a software system that looks at what's happening — an inbound call about a spreading crack, a text with a photo of a chip, a website form asking "does insurance cover this?" — figures out what the caller actually needs, and answers or routes it the way a well-trained front desk would, without pulling you off a curing windshield to do it. It doesn't decide whether a crack is safe to drive on, and it doesn't confirm someone's specific insurance coverage. It handles the answerable, logistics part of the call so you can step in for the part that actually needs your judgment.
Auto glass work has a scheduling constraint most businesses never think about: after a windshield goes in, the vehicle can't just drive off. The adhesive needs time to reach what the industry calls Safe Drive-Away Time (SDAT) — the minimum time a urethane adhesive needs to cure before it's safe to drive the vehicle at all, because a fully-bonded windshield is part of what holds the roof up in a rollover and keeps the passenger airbag from launching straight through the glass in a front-end crash. The Auto Glass Safety Council's AGRSS Standard, the auto glass industry's own ANSI-recognized safety standard, sets out how that time is determined — and it isn't one fixed number. Depending on the specific adhesive, it can run as short as 30-60 minutes for fast-cure products or stretch to 2-8 hours or longer for conventional moisture-cured ones, with the shortest published times based on a 75°F, 50%-humidity baseline that a cold driveway in January won't match.1 Full mechanical bond strength takes even longer to develop — 24 to 72 hours — which is why a responsible shop won't rush a customer out the door just because they're in a hurry.
That cure window is exactly when calls tend to stack up. A technician who's mid-install or waiting out a cure time genuinely cannot leave the vehicle to answer the phone, and that's precisely when the next customer — someone standing in a parking lot looking at a spreading crack — is deciding whether to wait for a callback or just search for the next auto glass shop.
| What happens | Left alone | Automated first |
|---|---|---|
| Call comes in while a windshield is curing | Rings out; caller tries the next shop down the list | Answered instantly, chip vs. crack and location confirmed |
| "Does my insurance cover this?" | Caller doesn't know, waits days to find out | Told what your shop knows about that insurer, callback scheduled to confirm specifics |
| "My crack runs across my sightline, is that dangerous?" | (same either way — needs a technician's judgment, always) | Never automated — flagged urgent, routed to a live callback |
| Customer asks when a mobile tech can reach them | Waits on a callback that might come tomorrow | Next real mobile opening, accounting for cure time, texted back same minute |
Take the free 2-minute readiness assessment
Illustrative example, not a real client: say a two-van mobile auto glass company fields around 35 calls a week. If 8 of those land during an install or a cure window and go unanswered, and roughly half of those callers book with whoever answers next instead of waiting, that's close to 16 jobs a month — chip repairs, full replacements, the occasional ADAS recalibration that comes with a replacement — going to a competitor. None of that shows up as a lost estimate or an angry review. It just quietly becomes someone else's job, because nobody was free to pick up.
This is a fair worry, and it deserves an honest answer, not a sales one: a system like this should never guess at whether a specific crack is safe to drive on, and it should never promise a customer their insurance will cover a claim it hasn't actually confirmed. What it should do is get someone a real answer fast, using information your shop actually has, and loop in a person the moment things sound urgent or uncertain. Picture what a caller might actually hear — illustrative only, not a real transcript: "Hi, this is the automated line for Coastline Auto Glass, and I want to be upfront about that. I can tell you our typical price range for a chip repair versus a full replacement, and check today's mobile availability near you — but if your crack is in your direct line of sight or you're not sure it's safe to drive on, I'm going to get a technician to call you back within the hour instead of guessing." That's not replacing the judgment call a technician needs to make. It's making sure the caller isn't left standing in a parking lot wondering if anyone's coming.
This isn't a generic call-answering script — it's what Unmanually actually builds for a shop like yours: a system set up around your real pricing for chip repair versus replacement, the insurers you actually work with, your real mobile schedule including cure-time buffers, and clear rules for what counts as urgent, with an immediate handoff to a live technician the moment a call involves a safety judgment, a specific coverage confirmation, or anything the system genuinely can't answer. The parts that need judgment always stay human; the system only ever handles the answerable, logistics part of the call.
We also back this with a real guarantee, not a vague promise: try Unmanually for 60 days, and if it isn't saving your business real time, whatever's left of your prepaid balance converts to account credit. That's not a cash refund on usage you've already consumed, since that reflects real infrastructure cost already spent, but it does mean you're never stuck paying for a system that isn't earning its place.
For an auto glass company, the revenue angle is direct: a $60 chip repair caught early is a job you can do in thirty minutes between other stops, and it's also the customer who comes back for a full replacement later, plus the ADAS recalibration appointment that often rides along with it. Every call that rings out during a cure window is one of those jobs answered by whoever picked up first. Catching more of them without adding a full-time phone hire is revenue you were already positioned to capture.
Not ready to commit to anything yet? That's completely fine — leave your email on our presale waitlist and we'll let you know as soon as mobile-scheduling and insurance-intake automation for auto glass and mobile repair companies is live, including founding-member presale pricing before it opens to everyone else this October.
1. Auto Glass Safety Council, AGRSS Standard (ANSI/AGSC/AGRSS 005-2022): Automotive Glass Replacement Safety Standard.
The full pillar guide this article belongs to.
Why a driver who just had an accident won't wait for a callback, and what's safe to automate about that first estimate call.
Status-check calls keep pulling technicians off the lift — what's safe to automate and what isn't.
More on the handoff pattern — where automation should stop, referenced above.
No, and it shouldn't try. Whether a crack is safe to keep driving on depends on things a technician needs to actually see — how deep it runs, whether it's spreading, whether it crosses the driver's direct line of sight, and whether the vehicle has a windshield-mounted safety camera that a fresh crack could interfere with. A system can ask the right triage questions and flag anything that sounds urgent for a callback, but the drivability judgment call always goes to a person.
It's safe for the parts that are just information lookup: whether your shop generally works with a customer's insurer, what documentation a claim usually needs, and getting a callback scheduled with someone who can check specific policy details. It's not safe for a system to tell a customer their deductible is $0 or that a claim is guaranteed to be approved, because that depends on their specific policy and only their insurer can confirm it — a real person should always close that loop before any promise gets made.
Take our free 2-minute readiness assessment — it walks through this same test against your actual call-answering process and tells you honestly what to automate first.
Take the 2-min readiness assessment