Prepare the technical context
Provide the model, device identifier, firmware version, operating country, SIM or network details and platform or app version. Describe the expected behaviour, actual behaviour, time and time zone of the incident, and the steps needed to reproduce it. Include the number of affected devices and whether the issue occurs continuously or intermittently.
Start with power and connectivity
Use the model-specific installation instructions to check power, connectors, indicator lights and the antenna position. For an offline device, check SIM activation, data availability, APN settings and local coverage. Do not change vehicle wiring, bypass protection or open the enclosure without suitable instructions and a qualified installer where needed.
Check positioning, alerts and battery behaviour
For position errors, note whether the device was indoors, under cover or near tall buildings, and check the location timestamp before comparing positions. For missing alerts, review the relevant settings and platform delivery path. For short battery life, record reporting frequency, signal conditions, charging behaviour and temperature; advertised or estimated runtime is not a substitute for a field test.
Review platform and integration settings
For missing data, confirm the device identifier, account access, server address and protocol expected by the platform. Integration enquiries should include the required data fields and a sanitized example message. API access, custom firmware, remote sessions and private deployment are discussed per project; availability and scope must be confirmed.
Share logs safely and control changes
Remove passwords, tokens and personal location information from shared logs and screenshots. Send only the records needed for diagnosis. Agree the scope and timing of any remote session, keep control of access and revoke it afterwards. Back up configuration and confirm model compatibility, power requirements and rollback options before an update or reset.
Validate the fix and escalate if needed
Test the change on a small number of devices first, repeat the original scenario and record the result. If the fault persists, send the earlier case reference, new logs and steps already tried. Confirm the next update with your contact. Hardware faults can continue through the after-sales process; support hours and response commitments depend on the agreed service arrangement.
Before you proceed
This guide describes the working process. Warranty, fees, delivery dates and support commitments are confirmed for each order or service agreement.