Collect enough detail to follow up
A good service request includes the caller’s name, contact number, vehicle registration, the work requested and preferred dates. Ask only for information needed for the enquiry. Avoid collecting payment-card details or unnecessary sensitive information in the call.
Separate a request from a confirmed booking
The initial MotorCall AI pilot is designed around requests for staff approval. The caller should hear that the garage will confirm the appointment. This avoids allocating a ramp, technician or courtesy vehicle without checking the actual workshop plan.
An illustrative handover
Example only: a caller requests a routine service next Tuesday morning and asks whether they can wait. The assistant records the request and callback details. The adviser checks the work required, duration, price and waiting arrangements before responding. This example is not a real customer booking.
Connect calendars only when the workflow is ready
A calendar slot alone may not represent workshop capacity. Before offering automatic booking, assess job duration, technician skills, bays, parts and any courtesy-car requirements. The integration must handle failed saves and changes as well as a successful booking.
Your questions, answered.
Can you connect our existing booking software?
We can assess it as part of a Connected proposal. Compatibility and implementation are confirmed before a commitment.
Will the customer receive a confirmation automatically?
The starting flow is a request for your team to confirm. Any automatic customer messaging needs an agreed and tested setup.
Can it quote a service price?
Only from approved information that applies to the customer’s vehicle and request. Otherwise the enquiry goes to your team for a quote.