The maintainability of an LED project is often decided on the handover day. Customers do not expect a display to need zero service; they expect a clear technical contact, a ticket number, a configuration backup, an escalation path and a rollback method when something changes. A good after-sales system gives every issue evidence, an owner, a status and a next action.
The handover pack should include the final equipment list, cabinet layout, screen-zone resolutions, power drawing, signal topology, port mapping, receiving-card files, processor scenes, software versions, firmware records, spare list and site photos. Name configuration files by project, zone, date and device. Keep the original, site-tested and rollback versions separately. Do not place RCFGX files, processor scenes or firmware from different projects in one folder called “final.”
One ticket number should follow the customer’s email, photos, video, remote session, spare part and final conclusion. At first report, collect the symptom, affected scope, time of occurrence, recent changes, power state, input source, controller, software version and fault images. The response should distinguish confirmed, likely and requires customer/site or manufacturer confirmation. If a site session is required, request availability, time zone, site personnel, computer access and safety conditions in advance.
The escalation path must be visible. Level one collects evidence and performs basic layered checks. Level two handles configuration, signal and device diagnosis. The manufacturer or R&D team handles serial-number/brightness verification, firmware, protocol and suspected batch issues. The project manager handles scope, change control and commercial communication. If the assigned engineer is unavailable, the customer should know the replacement contact, shared case channel and escalation route. Technical support should not depend permanently on one person’s WhatsApp account or a shared sales mailbox.
Remote support also needs boundaries. The customer can provide screen recordings, software screenshots, port indicators, configuration files and test results. Power distribution, grounding, cabinet opening, cable disconnection, lifting and receiving-card replacement must be performed by qualified site personnel. Remote work follows the same rules: backup first, isolate before internal work, change one variable at a time and test a small known-good zone first. If the issue remains, list what has already been excluded and what tools/spares the site visit needs.
Maintenance should include distribution and earth checks, cooling-path cleaning, seals and connectors, configuration backup, brightness/colour/gray-scale sampling, emergency-content checks and firmware-change records. The interval should match environment, runtime, rental frequency and product structure. Every maintenance action should record date, person, change, result and next recommendation.
A mature after-sales system answers five questions: What configuration is installed? Which area is affected? Who owns the next action? How can we roll back a failed change? When will the customer receive the next update? That is more valuable than sending a manual without a support process.
Use the same case number for the first customer email, reseller forwarding, engineering notes, remote-session recording, configuration file and spare-part shipment. If a reseller is involved, identify the end-customer site separately from the reseller contact. This prevents a technical question from being lost when the reseller is on holiday or when a shared mailbox receives several unrelated projects. A direct corporate technical address and an escalation backup are valuable for larger installations.
The first response should be short but complete: acknowledge the impact, state what is currently confirmed, request the minimum evidence and explain the next action. Do not bury a safety restriction inside a long paragraph. For example, “Please send a photo of the receiver status and the current configuration. Do not open the cabinet or disconnect internal cables until power has been isolated by qualified site personnel.” This is easier to follow than a long list of possible causes.
Close the case only when the agreed closure condition is met. Registration of a ticket is not the same as customer-confirmed resolution. A case may be technically mitigated, waiting for a replacement, waiting for factory confirmation or resolved but not yet accepted by the end customer. Keep these statuses separate so management reports do not show an unresolved customer issue as a completed repair.
Frequently Asked Questions
Q1: Which files must never be missing at handover?
At minimum: equipment list, cabinet layout, power/signal topology, port map, receiving-card configuration, processor scenes and version record.
Q2: Should the customer report technical faults to sales or engineering?
Sales and engineering may cooperate, but there should be a named technical contact, corporate email or ticket channel.
Q3: Can remote support ask the customer to remove a receiving card?
Only qualified site personnel who have isolated and verified power may do so. Remote support cannot replace site safety responsibility.
Q4: When should a case be escalated to the manufacturer or R&D?
Escalate when serial/brightness verification, firmware compatibility, protocol/API behaviour, a suspected batch issue or repeated unresolved faults require manufacturer evidence.
