Field reference: an outdoor event application. It supports environment discussion and is not evidence for a particular customer order.
Field reference: an indoor display installation. It illustrates venue context and does not define a Stellux product grade.
Field reference: a conference-room display. Use it to explain project context, not to infer stock, price, or delivery terms.
An international LED inquiry becomes useful when the team can understand the project behind the question. “Please send price” may be a reasonable opening message, but it leaves important decisions unanswered. A short, complete brief gives the customer a better chance of receiving a relevant batch match and gives the Stellux team a clear route for follow-up. That is the purpose of Service S02: bring contact details and project requirements together in one usable record.
The first part is identity and communication. A business name, contact name, business email, and at least one phone or WhatsApp number give the team a reliable way to continue the conversation. The contact channel matters because international projects often cross time zones, languages, and several departments. A buyer may be working with an end client, a local installer, a production manager, and a freight partner. When the first inquiry includes the preferred communication channel, the next exchange can stay focused on the equipment rather than searching for the right person.
The second part is timing. The customer does not need to promise a fixed date before the project is ready, but a target event date or preparation window is extremely useful. A screen needed for a fixed venue has a different planning rhythm from a screen needed for an event next month or a touring season later in the year. Timing helps the team understand what should be checked first: current batch relevance, technical review, packing coordination, or a missing requirement. Stellux should record the date or range the customer provides and should leave it as pending when the customer has not confirmed it. It should not invent an availability promise in response.
Destination is the third essential input. A country name is a start, but a city, venue type, or delivery context can make the brief more actionable. The destination can affect the way the project is discussed, the type of packaging that needs to be reviewed, the handover contact, and the information needed for later coordination. The destination does not automatically determine a delivery date, freight price, tax result, or local compliance position. Those items require separate confirmation. The safe practice is to collect the destination early without pretending that all logistics are already solved.
The fourth part is the operating environment. Tell the team whether the intended use is indoor, outdoor, temporary rental, touring, or fixed installation. If the environment is not yet decided, say so. The project may include daylight, weather exposure, a protected venue, a large audience, a close viewing area, or a camera-facing production. These details influence the next engineering questions. They also prevent a common misunderstanding: a photograph of a bright stage display can look impressive, but it cannot by itself confirm that the same equipment is suitable for a different environment.
The fifth part is the physical requirement. Give the target screen width and height when possible, the approximate screen area, the desired quantity, and any known cabinet size or pixel-pitch preference. If the customer is replacing part of an existing system, include the existing cabinet format, brand or series information, and the problem that the replacement must solve. A replacement request should not be treated as a new product request because compatibility may depend on the physical cabinet, module arrangement, controller configuration, power path, and available accessories.
The sixth part is the result the customer needs. Some buyers need a product direction. Others need a batch inspection reference, a technical compatibility conversation, a replacement plan, a packing discussion, or after-sales coordination. Saying what a useful response looks like helps the team organise the next step. For example, “We need to know whether this cabinet format can match our existing rental stock” is more actionable than “Need LED screen.” A precise request also makes it easier to separate confirmed facts from questions that still need checking.
One clear brief reduces repetition. Without it, the customer may send a product name in one message, the destination in another, and the target date several days later. The sales team then has to reconstruct the project from fragmented messages, and engineering may review a configuration that is no longer the right one. A shared brief creates a small source of truth for the conversation. It can be updated when the project changes, but the change should be visible.
The brief also protects the customer’s time. Overseas buyers often work with different technical vocabulary. One person may say “panel,” another may say “cabinet,” and a third may describe only the screen area. Asking clear follow-up questions is part of professional service, but asking the same basic questions because the original message was incomplete creates friction. A short form or WhatsApp service panel should make it easy to provide the important information in one pass.
A strong brief does not need to be long. A name, business email, phone or WhatsApp number, destination, application, target date, screen requirement, and one sentence about the project may be enough to start. Attachments can help, but they should be labelled: site photo, existing cabinet photo, screen drawing, content reference, or control-system note. The customer can also mark unknown items as “to confirm.” That wording gives the team permission to investigate instead of forcing a guess.
For international customers, clarity is also a trust signal. The team is not asking for information to create unnecessary paperwork. It is trying to match a real requirement to a real batch and avoid a recommendation that looks good on paper but fails at the site. When the customer shares the context early, the sales and engineering review can be more direct, the quotation can be tied to a known configuration, and the later quality path can use the same project reference.
S02 is therefore more than a contact form. It is the moment where a general product question becomes a project conversation. Give the team one usable brief, keep unknowns visible, and state the result you need. The next step becomes faster, more technical, and more honest because everyone is looking at the same starting information.
