CHECK 01
List the customer’s digital requirements
Ask which display language, phone connection and cabin controls are essential. Separate offline operation from services that need a network, account or subscription. A specific requirement is easier to verify than a general promise of full connectivity.
Request demonstrations on the actual offered vehicle, identifying the device and relevant software context. A recording from another market may concern a different configuration. The market guide keeps those descriptions separate.
CHECK 02
Check assistance claims carefully
Identify the installed equipment and applicable operating information. A trim label alone does not establish every assistance function. Keep conditions and limitations with the customer description rather than presenting the system as unrestricted autonomous driving.
The trim review helps connect claims to evidence. A successful demonstration in one environment does not prove availability or identical operation after export. Important uncertainties belong in the acceptance discussion.
CHECK 03
Plan access transfer through supported processes
Ask how ownership-linked services and keys are handled at handover. Do not request another owner’s password or expose their personal information as a substitute for an appropriate transfer process. Identify the party responsible for unresolved account questions.
Retain the physical-key count and any separately agreed devices. A seller’s present access does not establish a continuing service commitment for the buyer. Applicable support terms need to come from the party offering them.
CHECK 04
Record the result by function
Use a simple list: requirement, evidence, observed context and remaining dependency. If the car or software changes, consider whether earlier demonstrations still answer the customer’s question.
Preserve key and access arrangements in the handover record. This lets the receiving dealer describe what has been established without promising every future update, regional service or manufacturer benefit.
If a software update or reset takes place before dispatch, check whether essential demonstrations need repeating. Record the change and any result rather than assuming the earlier session still describes the delivered car. Keep this review limited to supported processes and the customer’s specified functions.
CHECK 05
Example: a connected-service demonstration
A seller shows a feature working with an existing account. Record the vehicle and circumstances, then ask whether a supported route exists for the intended owner and destination. Independently demonstrated offline controls can be described separately. Leave the account-dependent outcome open until confirmed, rather than using one online session as proof of the entire ownership experience.
Model context: GS3 Yingsu in China and GS3 EMZOOM in Malaysia. Specifications and market programmes are not interchangeable; confirm the actual offered vehicle.
Make the next request specific.
Send the condition, accepted years and version, destination and quantity. Include the items that must be confirmed before you accept a candidate. A sourcing enquiry begins the discussion; availability and purchase terms require an actual offer.
Discuss a suitable GS3 →