Business Technology · Power & Control · Hong Kong
breadIT · Innovative Thinking

Technical support starts with clear information.

Choose the right support path and provide the details that help breadIT understand the system, symptom, impact and safe next step.

Capture the evidence before changing the system.

Where it is safe, record the exact condition before restarting, resetting, rewiring, updating or replacing components.

Identify

Record the service, device, model, revision, serial number and site or user.

Describe

Copy exact error or alarm text and explain what happened before and after.

Assess impact

State who or what is affected, whether there is a workaround and whether operation is safe.

Preserve

Keep logs, screenshots, photos, configuration records and recent-change details where appropriate.

Tell us what changed, what you see and what is affected.

Use the form to prepare a structured support email with the identifiers, symptoms and impact needed for an initial review.

Do not submit secrets. Do not include passwords, MFA codes, private keys, payment details or unnecessary personal information.
Add relevant attachments in your email after the draft opens, and remove any passwords or unnecessary sensitive information.

Some issues need a controlled site response.

Remote guidance is not a substitute for qualified on-site assessment where electrical, mechanical, fuel, fire, life-safety or operational hazards may exist.

Clear next steps

A precise support request is easier to act on.

Send the model, exact message, impact, recent changes and safe evidence. For critical coverage, agree the response arrangement in advance.

Contact support