Emberforge builds a warranty claim system that sits beside your DMS. Customers start a claim and pick a time online, each shop sees its own jobs and updates from a phone, and everyone can see where a claim stands without calling the front desk.
No cost, no obligation. Erick replies within a day to set a time.
DFW has the largest used-car dealer base of any metro we compared, and over a hundred dealerships run with ten or more staff. Those are the stores selling enough warranties that claim coordination has become a job nobody was hired for.
The problem is not the warranty. It is what happens after the customer calls: confirming coverage, finding a shop with availability, handing off the car, and calling back until it's done. In a market this spread out, with shops across Dallas, Fort Worth, and the suburbs between them, that chain is longer than it looks.
The system doesn't replace Frazer, DealerCenter, Dealertrack, or whatever DMS you run, and it doesn't replace your warranty administrator. It handles the coordination in between, and records the coverage call your team already makes.
Counts: U.S. Census Bureau, County Business Patterns 2023, employer establishments in the Dallas–Fort Worth–Arlington metro area, NAICS 441120 (used car dealers). Concentration compares the industry's share of local businesses with its share nationally.
Your DMS handles the sale. Everything that happens after a warranty customer calls lives on the phone and a notepad.
The customer calls the dealership for updates because the shop won't call them. Your staff call the shop, then call the customer back.
A status link for every claim. The customer opens it to see which shop has the car, what stage it's in, and when it's expected back.
Staff confirm coverage, then call each shop to find availability, hand the job off, and call back repeatedly to check status.
One master calendar with each shop's live availability. Customers self-schedule against it, and the shop gets the job without a phone call.
Which shop has which car, and where each claim stands, lives with one person. When they're out, nobody knows.
A claims board: every open claim, its shop, its stage, and how many days it has been sitting there.
Getting a status update out of a shop means calling until someone picks up.
Each shop gets a link that shows only its assigned jobs. They update status, add photos and notes from a phone, and the customer is notified automatically.
The repair was fine, but the experience was slow and opaque, so the customer doesn't renew and nobody can see why.
A history per customer and per vehicle, a report on each shop's turnaround, and a list of customers coming up for renewal.
How warranty coverage gets determined doesn't change. Your team makes that call the way it does today; the system records it.
Sales, inventory, and deal paperwork stay where they are. This connects where it makes sense and never duplicates them.
Claim intake, shop scheduling, status updates, customer communication, and the record of what happened.
DoulaFlow is practice management software we built with Megan, a practicing doula. Every client's stage, due date, and next appointment sit on one board, so nobody has to ask where things stand.
It took two months to build and two in beta, and it's been live since June 2026. See more of DoulaFlow
A claims board works the same way: one row per claim, with its shop, stage, and next step at a glance.
Step 1
Walk through how a warranty claim moves through your store today. We'll tell you whether a build makes sense.
Step 2
Usually 1–2 weeks. We map your claim process and hand you a fixed scope and a firm price. Credited in full toward your build.
Step 3
A claims board with customer and shop links is a Workflow build, typically 6–10 weeks. Customers and shops work through secure links; the dealership is the only party that logs in.
Erick Quintanilla maps your process and builds the system himself. He spent 12+ years as a developer and process consultant in banking, healthcare, and aviation, mapping workflows by hand and automating the manual steps in between.
No. Your DMS keeps handling sales, inventory, and deal paperwork. This handles the warranty claim coordination that currently lives on the phone and a notepad.
No. Your team makes the coverage call the way it does today. The system records the decision and removes the busywork that follows it.
Over video, on your schedule. Chattanooga is on Eastern time, one hour ahead of Dallas, so the working days overlap almost completely. The Blueprint is a series of screen-shares where we walk through how a claim moves through your store; nobody needs to fly.
No. Customers and shops work through secure links. The dealership is the only party that logs in.
It depends on which systems you run and what they allow. Finding that out is one of the first things the Blueprint answers, before a price is set.
You do. Once the build is paid in full, the system, its source code, and your data belong to you, running on your own domain.
Emberforge brings a set of reusable tools and components to every project, and your system includes a permanent license to use them. If you need exclusivity in your market, that's scoped and priced in the Blueprint.
The Blueprint usually takes 1–2 weeks. A claims board with customer and shop links typically takes 6–10 weeks to build.
A file board and status links beside RamQuest, SoftPro, Qualia, or ResWare.
See the page → Property managementWork orders, vendor updates, and owner status beside your accounting software.
See the page → Any marketThe same warranty claim system, wherever your store is.
See the page →Thirty minutes, no cost. If a claims board and shop links would take phone tag off your staff's plate, the next step is a Blueprint. If not, you'll hear that too.