Auto repair updates that keep the customer and repair order in sync.

It can send intake, inspection, estimate, approval, parts-delay, repair, collection, and reminder messages; present approved photos or documents; capture customer decisions; notify advisers; and write the result back to the repair order. Each trigger and status must come from an authoritative source.

Yes, when the client defines identity, consent, terms, pricing display, expiry, partial approval, changed estimates, attachments, and the authoritative repair-order update. The workflow should record what the customer saw and selected, then route ambiguous or disputed cases to an adviser.

Use native messaging or a specialist product when it supports the required channels, consent, evidence, approvals, and integration. Custom work fits a valuable recurring path that those products cannot cover cleanly. It should extend, not duplicate, the repair-order system.

Scope and price are agreed before development starts, once the service path, event triggers, approved messages, consent rules, and integration are defined. A first release covers one service path: event triggers, approved messages, secure customer decisions, adviser review, history, one system integration, monitoring, and handover. More locations, brands, channels, languages, payment, marketing, or complex consent add scope.

Every customer conversation in a single shared inbox. The decisive test: if a customer replies to a message sent by a service writer who is now off shift, who sees the reply? Suites that route SMS replies to the initiating user have the same problem as no shared inbox. Map only approved events (intake, inspection ready, estimate changed, customer decision required, parts delay, work complete, collection) and confirm current state before each send. Prevent duplicates, stale messages, and out-of-order updates.

Present the authorised vehicle, work, photos, findings, estimate version, terms, choices, and expiry through a secure link. Share photos and video of worn parts instead of describing them, and record what the customer viewed and selected. Route partial, changed, ambiguous, or disputed decisions to an adviser: the estimate closes faster when the customer sees the evidence, not a line item.

Run the trial in parallel with the current system through real peak days, with the front desk using it for real conversations. The trial must cover the hard cases: a customer partially approving work, a part becoming unavailable mid-order, a technician change mid-order, and an accounting export clean enough for month-end. If advisers avoid it during the trial, the platform fails.

Ask the off-shift question: who sees the reply when the sender goes home? Check the estimate story: can customers approve from a secure SMS or email link, and does the system record what they viewed? Confirm the consent rules: operational communication separated from marketing, contact preference and opt-out visible, no repair or customer information exposed in an insecure notification. And compare the full cost picture, messaging, devices, migration, training, integrations, support, exit, not the starting plan alone.

The plan is set after system access, repair states, templates, consent rules, test records, and owners are ready. Vendor approval, poor contact data, several shop systems, payment, or complex multi-location routing can extend the plan.