Create a service request for an existing device
Start a service request directly from a saved vehicle or device and take over its data
→ Open vehicles · Open service requests
If the customer's device is already recorded in SimpliServ, start the service request directly from the device or vehicle record. In SimpliServ this record is the central place for brand, model, serial number, licence plate and owner.
This guide means a customer device or vehicle in vehicle management. A paired kiosk or signature tablet under Administration → Devices is something else and is not taken over into a service request as a repair device.
Prerequisites
You need Service registrations → Create and Files → Create for the ticket action. To open the existing record you also need the matching vehicle/device access. If the device has an owner, their customer ID is passed to the creation process as well.
Start a service request from a device or vehicle
Open the device
Open Vehicles and select the saved device. Check serial number, brand and model so you don't work on the wrong record.
Choose new ticket
Click New ticket in the header. The action is only visible if you're allowed to create service requests.
Select service request
In the dialog Where do you want to start? choose Service Request. SimpliServ opens the intake page with the record's vehicleId and – if present – customerId.
Check the context
At the top, New ticket for shows the selected device and the owner. If both are correct, you're working in the right context.
Capture fault and work
Only add the details that are new for this case: fault symptoms, requested work, photos, signature or other form fields. Existing device data isn't asked for again, as long as it's recognised as device data in the form mapping.
Choose request or order
Leave Convert to order immediately off if it should be reviewed first. Turn the checkbox on if an order including the workshop tag should be created right from the intake.
Create the request
Click Create request. SimpliServ saves the service request, links the new customer flow to the device and – if present – takes over the customer.
Which device data is taken over
When started with vehicleId, the intake page loads the existing vehicle record. Depending on the field mappings, recognised device data is hidden and inserted on submit:
- brand (
brand), - model (
model), - serial number or VIN (
serial_number,vinor matching field names), - licence plate (
license_plateor matching field names), - a combined form field of type Vehicle for brand and model.
The form still shows case-specific fields such as the fault description. The app inserts the hidden values back into the payload so that required fields and PDF/email data stay correct.
If the vehicle has a customer, the known customer fields are also hidden and filled with customer data. If it has no owner, customerId stays empty; the ticket is then still linked to the device, but not to a customer account.
Check serial number and owner before submitting. Starting from the wrong device links the new ticket phase to the wrong record. Don't just change brand or model in the form if you want to correct the underlying record.
What's linked after submitting
The creation process creates a service request and the associated customer flow. After successful creation SimpliServ writes the vehicle_id into the flow. That way the ticket stays visible on the vehicle and can later be tracked together with order, proposal, invoice and further phases.
Without direct conversion
The service request is saved. When started via the flow, the app returns to the customer flow. There you can review, accept or decline the request and later convert it into an order or cost estimate.
With direct conversion
SimpliServ converts the service request into an order, loads the workshop tag and then opens the order. Use this option when the workshop can start right away and no approval phase is needed.
Difference from starting in the customer profile
| Starting point | Passes | Best choice when |
|---|---|---|
| Customer profile → Create ticket | Customer ID | Customer known, device still unclear or only described in the form |
| Device/vehicle → New ticket | Device ID plus owner ID, if present | a specific existing device should be taken over reliably |
| Service requests → New request | no preselected record | neither customer nor device is known beforehand |
Troubleshooting
"New ticket" button is missing
Check Service registrations → Create and Files → Create. The vehicle must also be loadable.
Device is shown, but customer is missing
Check in the vehicle record whether an owner is set. The action only passes customerId if vehicle.customer_id is present.
Serial number appears again as an empty field
The field is only hidden if the mapping or field name is recognised as device data. Check the mappings and field names in the service registration form. For a deliberately additional field you have to enter the value separately.
Ticket on the wrong device
Only delete the wrong request if you're sure no history is needed. Better: check the vehicle record before the next start and correct the request via the existing field corrections or the responsible record.
Related topics
Take over an existing customer
Start a service request directly from the customer profile.
Handle service requests
Review and process incoming requests.
Pair tablets and devices
Manage kiosk and signature tablets; not to be confused with customer vehicles.
Full-screen signature
Capture a signature with mouse or stylus in full screen.
How is this guide?