Project desk
Use the inquiry form for model comparison, controller/receiver compatibility, commissioning preparation or an operating issue. No street address is asserted because the supplied brand assets do not provide a verified office location.
A useful initial message does not need every answer. It should identify the screen, source path, project stage and the decision that is blocked. Mark unknown items for verification instead of filling them with assumptions.
Use the inquiry form for model comparison, controller/receiver compatibility, commissioning preparation or an operating issue. No street address is asserted because the supplied brand assets do not provide a verified office location.
Provide a monitored work email and your role in the project. A reply can then distinguish commercial questions from technical evidence that should be reviewed by an integrator or application engineer.
Include the event date, maintenance window or procurement milestone. Urgency does not remove the need to verify model documentation, firmware context and safe site procedures.

Recommended items: active canvas in pixels, source formats and frame rates, controller and receiving hardware, firmware identifiers, cabinet map, photos or video of the symptom, configuration backup, and the acceptance condition you need to reach. Remove confidential credentials before uploading files.
For an operating fault, state when it began and whether it follows a source, port, cabinet, temperature condition or software change. Do not work on energized equipment or elevated structures beyond your training and site authorization. If remote review cannot reproduce the behavior, schedule an on-site test under the real source, cable, thermal and viewing conditions.
The form records the contact and project context. In the message, distinguish observed behavior from interpretation. For example, “output 2 loses image after 20 minutes” is more useful than “the processor is unstable.”