The short answer
Use one clear intake process with a visible repair type, an assigned owner and a defined next action. Keep hail and collision sources identifiable even if one team handles both. Separate an inquiry, an inspection appointment, an estimate and authorized work so reminders match what the customer has actually agreed to.
What should the initial repair inquiry collect?
Start with information that helps your team decide the next step: contact details, vehicle description, damage type, location and photos when useful. Let customers describe what happened in their own words. A long form that asks for every possible detail can delay a simple request for an inspection.
Explain whether the form books a confirmed inspection or merely asks the shop to contact them. If a vehicle needs urgent help or cannot be driven safely, provide the appropriate phone-based contact path rather than implying that an online form resolves the situation.
- Repair type: hail, collision or unsure.
- Vehicle: year, make and model where useful.
- Contact preference and a suitable time to reach them.
- Photos and a brief description, with a clear explanation of their purpose.
- A source or brand tag that remains visible to the team.
How do you keep two repair brands organized?
Store the business or brand associated with the inquiry as a field, not only inside a free-text note. Use it in lead filters, owner routing and the sender identity of customer communications. A customer who contacted the collision brand should not receive an unexplained message from the hail brand.
Keep one lead history when the same customer needs help from both teams. A repair type can change after inspection; record the change rather than duplicating every conversation. Restrict access to customer details to the people who need them.
Which stages belong in a repair lead pipeline?
A workable sales pipeline might use New inquiry, Contacting, Inspection scheduled, Estimate or scope under review, Work booked and Closed. The labels should describe real events your team can confirm. Keep detailed repair production scheduling in the appropriate operational system.
When the customer replies, pause generic outreach and let the coordinator handle the question. If an inspection moves, replace its reminders. If the customer declines, stop the active follow-up. Do not use a marketing automation to make promises about coverage, payment responsibility or a repair result.
- New inquiry has a person responsible for contact.
- Inspection scheduled has a real date and confirmation.
- Work booked reflects the shop's actual approval process.
- Closed records the outcome without pretending every inquiry became a job.
How should the owner review inquiry performance?
Compare hail and collision inquiries separately, then look at contact rates, inspections and booked work. Combine totals only when the same definitions apply. Raw inquiry volume can hide a large backlog of people who never received a useful response.
Review a few closed and lost conversations each week. Look for unclear next steps, incorrect brand messages and reminders that continued after a change. These practical checks often reveal more than adding another dashboard chart.
Common questions
Should hail and collision leads be in separate systems?
They do not have to be. One workspace can work when brand, repair type, permissions and routing remain clear. Use separate systems when your business requires that separation.
Can an automation promise an inspection outcome?
No. Use it to acknowledge, request appropriate details and arrange the next step. Leave coverage, scope and repair decisions to the authorized people handling the job.
About this guide
Written for service-business owners by WellRun. The workflows and examples are practical recommendations; example messages are illustrative, not client results. Actual setup depends on your services, team and connected tools.
Spotted something that needs correcting? Email WellRun.