FAQ
Straight answers.
What shop owners ask before a demo. If yours isn't here, email [email protected].
What is actually built today?
The backend that runs the whole job: customers and vehicles, the calendar with double-booking protection, online booking requests, inspections with photos and urgency, estimates with line-by-line approval by link, repair orders, invoices as PDF, partial and full payments, recommendations from declined work, event-driven messages, profit per repair order, lead-source tracking and an audit trail. It is delivered and tested.
What is not built yet?
The three front ends: the Staff app for the mechanic's phone, the Customer Portal, and the WordPress plugin with its booking widget, Elementor widgets, Gutenberg blocks and shortcodes. They are in development. So are the named integrations (QuickBooks, Square, Stripe, Google Calendar, SMS providers), parts and inventory, suppliers, multi-location, dispatch, fleet work, review automation and time tracking. Everywhere on this site those carry a Planned or In development label.
Can I really run a job without a service advisor?
That is what it is built for. One record per job, one next action, and the customer-facing steps (estimate approval, invoice, payment) work by link so nobody has to phone anyone. The mechanic claims the job, and no one else can claim it by accident. The owner decides what a mechanic may and may not do: change prices, give discounts, see cost and margin, delete financial documents.
How much does it cost?
Pricing is quoted per shop and is not published. It is based on locations and the features you actually need, priced per location and feature tier rather than aggressively per seat; limited-access mechanic users do not carry full seat pricing; variable costs such as SMS, telephony, AI and storage are shown transparently; data export is never locked behind a tier; cancellation is simple. Tell us about your shop and we quote it in writing.
Can I get my data out?
Yes, all of it, at any time, at no extra charge. Full data export is included at every level and is never used as leverage. Customers and vehicles come in the same way, by CSV import with duplicate merge.
Does it work with my WordPress site?
That is the plan: a plugin that puts online booking, estimate requests and a customer portal link on the WordPress site you already have, as Elementor widgets, Gutenberg blocks or shortcodes. The plugin is in development. The shop's data stays in the backend, not in WordPress, so a site rebuild never touches your records.
Do you integrate with QuickBooks, Square, Stripe or Google Calendar?
Not yet. Every named integration is Planned. We list them because shops ask, and we label them honestly because none of them ships today.
What happens to a repair the customer declines?
It stays on the vehicle as a recommendation with an urgency and a due date or mileage. When it is due, a follow-up goes out within the consent the customer gave, and the next booking lands on the same record. Nothing is retyped.
How do customer messages work, and what about consent?
Messages are driven by events on the job: booking confirmation, reminder, vehicle ready, unpaid invoice, estimate reminder, declined-repair follow-up, maintenance reminder. Transactional consent and marketing consent are recorded separately and opt-out is honoured. Email works today; SMS providers are Planned.
Do I need a consultant to set it up?
No. Working hours, service durations, tax rates and the service list are set once. Customers and vehicles come in by CSV. The WordPress plugin, when it ships, starts with an isolated demo shop so you can try a booking before you register.
Is my data safe, and who can see cost and margin?
Every shop is isolated from every other shop, and critical actions are audited. Cost, margin, discounts, refunds, deletions and exports are permissions the owner grants, not defaults every mechanic gets. The Customer Portal, when it ships, shows customers only what they are entitled to see, never internal notes, cost or supplier details.
How do I see it?
Request a demo. Tell us a little about the shop and we walk through the workflow with your kind of jobs, say plainly what is built and what is planned, and quote it.
Still have a question?