Initial enquiry
Ask for the vehicle, mileage, symptoms, and desired outcome in short, understandable steps.
For auto repair shops
An AI administrator for auto repair shops
AI can ask about the vehicle, issue, and preferred time, but it must not invent a repair price before inspection or promise parts availability without verification.
Registration, Web Chat, server-side AI, Inbox, CRM, and the built-in calendar are part of the current MVP. External calendars, multiple staff schedules, and industry-specific integrations remain future stages.
HexSales / SolutionMVP · working version
One conversation, one business
AI receives approved knowledge from the current organization only.
01
Understand customer intent
02
Ask only for necessary details
03
Answer or bring in a person
A working-flow illustration, not proof of an industry integration
Challenge
Turn “something is rattling” into a useful service enquiry
A first message rarely contains everything a technician needs. AI asks for the make, model, year, symptoms, and contact details in sequence, keeps the history, and hands the conversation to a technician without making mechanical guesses.
Workflows
What works today and what comes next
Answers from business data, contact capture, Inbox, CRM, the built-in calendar, and human handoff are in the working MVP. External integrations and industry data sources remain clearly marked as future stages.
Services and policies
Answer from the approved job list, opening hours, location, and vehicle intake policies.
Diagnostic booking
Offer a real time from the built-in calendar or hand the enquiry to a technician for manual coordination.
Now
Working foundation
Before launch, each business validates the product with its own data, policies, and real customer scenarios.
- Registration and setup store the organization, profile, services, and business rules.
- Web Chat creates one tenant-scoped conversation and sends messages to server-side AI.
- Inbox and CRM show real messages, contacts, and leads without demo records.
- The built-in calendar shows real availability and prevents overlapping appointments.
- Manual control keeps AI silent until the owner explicitly returns control.
Process
The working flow and future connections
- 1
The shop adds its jobs, standard conditions, opening hours, location, and FAQ.
- 2
AI identifies the request type and asks only necessary follow-up questions.
- 3
Vehicle details and the problem description are stored in the lead profile.
- 4
The customer selects a verified time, and AI books only after explicit confirmation.
- 5
A technician sees the original conversation and can continue it manually.
Guardrails
What AI must not do
Server-side AI receives these limits with the business rules. The owner must validate industry-specific policies before serving customers.
- Never state a final repair price or duration without shop confirmation.
- Never diagnose a mechanical issue from a text description.
- Never promise parts, equipment, or specialist availability without current data.
FAQ
An honest view of what works today
No decorative promises and no claims about features that are not available.
Can AI estimate a repair from a customer message?
It can collect details and share only pre-approved estimates when the shop has supplied them. Final diagnosis, cost, and timing remain with a qualified technician.
What booking capabilities are available?
The HexSales calendar already shows open slots and supports creating, rescheduling, and cancelling appointments in one primary schedule. External calendars, equipment, and multiple technician schedules remain future stages.
Which details does an enquiry collect?
The expected minimum is contact information, vehicle make and model, year, problem description, and preferred time. The business owner controls the concrete information requested.
Can a technician take over the conversation?
Yes. In manual mode, AI stops replying. An authorized employee can see the history and continue the conversation, and control can be returned to AI separately.
Early access
Start with a real workflow, not a polished demo metric
Add your services, policies, and common questions, then verify answers in Web Chat. External channels become active only after separate server-side verification.