A mobile appointment consumes more than the time spent beside a vehicle. Travel, access problems, loading, weather and the return of waste or unused parts all compete with repair time. A service that looks profitable on the estimate can become difficult to sustain when those dependencies are invisible.
Start by defining a small service territory and a precise menu. The objective is not to make every workshop job portable. It is to deliver selected work reliably, with a clear route back to the workshop when the location or vehicle needs more than the mobile team can provide.
Define the location as part of the job
Ask where the vehicle will actually be parked, who controls the site and whether the customer has permission for commercial work there. Collect access instructions, vehicle identification and photographs of the proposed working area when useful. A postcode alone does not establish a suitable workplace.
Have a competent person assess the job-specific risks, including traffic, surface conditions, lighting, weather and public access. Establish refusal and stop-work criteria before dispatch. Roadside emergencies and controlled fleet-yard appointments should not share a booking promise merely because both happen outside the workshop.
Separate assessment from a promised repair
Record the customer’s concern without accepting their proposed diagnosis as established fact. Explain what the initial visit includes, its charge and the decision point for further work. If an assessment may lead to a workshop referral, say so before the customer books.
For example, a customer asking for a replacement battery may be describing a starting problem with an unknown cause. The appointment should identify the authorized assessment rather than guarantee that a particular component will solve it. Follow the same evidence and approval principles used in repair-order handoffs.
Price the complete dispatch cycle
Build an internal job-cost review that includes travel, loading, service time, consumables, administration and return handling. Compare this with the charge the customer agreed to pay. Distinguish an illustrative planning allowance from a guaranteed arrival or completion time.
Group compatible appointments geographically only after checking skill, parts and equipment requirements. A short drive does not make two jobs interchangeable. Keep room for realistic delays, and decide who contacts later customers if an earlier appointment changes. The capacity-based scheduling guide offers a useful starting point.
Control what leaves and returns
Create a dispatch checklist tied to the actual vehicle and authorized scope. Identify reserved parts, required tools, applicable technical information and the technician assigned. Verify the van’s loading and storage arrangements through the appropriate safety and operational review rather than treating it as an extra parts shelf.
At return, reconcile used parts, unused stock, consumables and waste. Assign ownership for missing equipment and supplier returns. Where a job cannot proceed, record the reason and what happens next; do not leave a mobile appointment open with no named owner simply because the technician has returned.
Design the workshop fallback
Agree how a vehicle will be referred or transported when mobile completion is unsuitable. Confirm who authorizes the next stage and whether another business will perform it. Pass along observations and completed tests, clearly distinguishing them from unresolved hypotheses.
Review insurance, local permissions and waste-handling arrangements before launch. Use the risk-review guide to prepare questions for your adviser. Neither customer permission nor a signed estimate replaces a safe working location, suitable competence or the applicable legal requirements.
Pilot one route before expanding
Run a limited pilot with a defined service menu and review each appointment’s entire cycle. Record travel overruns, missing information, parts mismatches, referrals and customer feedback. Change the booking criteria when a problem repeats instead of asking technicians to absorb it informally.
Bring that dispatch-to-invoice process to a SaSa Shop OS discussion. Ask which records and scheduling steps are supported today, and test the actual device and connectivity conditions your team expects. Do not assume offline access, route optimization or field-service automation without verification.




