Turn the customer request into observable tasks
Ask whether the customer needs English controls, ordinary calls, music, maps displayed from a phone or a particular remote service. List the essential tasks separately. The word connectivity can hide several different dependencies. A customer who only needs calls may face a simpler buying decision than one requiring a specified projection service. Keep the intended phone and relevant operating context with the request. The fitted-equipment review provides the original vehicle identity, but it does not by itself establish software functions. A feature advertised on another market’s version must not become the candidate’s acceptance result without evidence.
Identify the actual screen and software arrangement
Request relevant installed-system information and disclose known replacement or preparation history. Determine whether the unit is factory original, a supported replacement or an added item. Retain the provider and date where applicable. The modification buying review helps separate useful additions from unpriced integration concerns. A menu photograph can show the displayed language at that moment; it cannot establish every setting, application or future update. Do not assign a universal latest software number to the E-QM5 family or present a third-party addition as an original supported manufacturer feature.
| Finding | Buying response |
|---|---|
| Specific task works | Describe the demonstrated arrangement |
| Supported preparation proposed | Require completion and repeat checks |
| Essential service region unresolved | Leave acceptance conditional |
Demonstrate language across the needed controls
While safely parked, show the normal controls and screens that the customer must use. Check the relevant status and settings rather than one attractive home screen. Ask what remains untranslated or depends on an added application. A partially familiar display can leave important functions unexplained to the receiving user. Preserve the exact demonstrated result. Where an English-language change is proposed, have the responsible provider establish eligibility, scope and completion evidence. A seller’s willingness to change the unit is not proof the requested result is supported or already completed on this particular vehicle.
Separate calls and audio from phone projection
Use the intended device to demonstrate the required ordinary tasks. A working Bluetooth connection can establish calls or audio under its tested arrangement without proving projected navigation or a named projection platform. If a cable or added interface is necessary, identify it and whether it is included. Record phone and vehicle context so the receiving dealer can reproduce the task. Avoid describing a mirrored application as another service merely because the display looks similar. The accepted promise should name the operation that worked, with limitations, rather than say that every phone feature is compatible.
Keep regional and account services conditional
Ask which functions need an account, network, registration or subscription and which provider supports them. A source-market demonstration does not establish destination operation. The ownership support review keeps relevant access and receiving-user questions alongside the service arrangement. Keep credentials private and do not rely on the previous owner’s login as a support arrangement. If the customer’s essential function has an unresolved overseas dependency, leave that issue visible before comparing a technology premium. Ordinary cabin calls working cannot settle every remote-service, map-data or future-software question associated with the vehicle.
Repeat the agreed tasks after supported work
Where the provider completes a legitimate preparation change, retain the result and repeat the tasks affected by it. Show relevant controls, normal camera operation where applicable and the requested phone function under suitable parked conditions. A completion receipt is not a demonstration of the customer’s outcome. Keep before-and-after findings and any newly observed concern with the car. Use the vehicle review for wider condition; this task does not certify every system after a software change. If the seller proposes another unit, review its actual installed arrangement instead of carrying over the earlier screen video.
Write a precise delivered-function description
List the supplied items, demonstrated language and phone tasks, responsible preparation provider and remaining service dependencies. The equipment acceptance schedule keeps these promises attached to the selected car. State future support terms only where the appropriate party has confirmed them. New stock still requires its requested functions checked; a used car needs its additional history and account release. The customer should receive a truthful description of what can be used in the established arrangement, without universal phone compatibility, guaranteed future releases or a destination-service claim inferred from a source-market sign-in screen.
Keep the decision clear.
- Separate requested tasks
- Installed system and preparation history
- English controls demonstrated
- Actual phone and supplied interface
- Remaining account and regional limits
Before you decide.
Does Bluetooth prove CarPlay or Android Auto?
No. Demonstrate each specifically requested operation rather than infer it from a working call or audio connection.
Does an English home screen establish every control is translated?
No. Review the controls and status screens essential to the customer’s use.

