Chat, attachments, and department handoffs

Department chat is the quickest way to give work to Winglo. Conversations are saved, so choose whether to continue an existing topic or start a clean one.

Write a clear message#

Include the goal, source facts, limits, output, and approval boundary.

Example:

Review this landing-page image for brand and readability. List the changes first. Do not create or publish a replacement yet.

Do not rely on a department to guess a customer, market, date, or destination.

Use conversation history#

Continue the same conversation when the new request depends on earlier messages. Start a new conversation when the topic, customer, or goal changes.

Before relying on old context, restate facts that may have changed.

Attach images#

Chat accepts PNG, JPG, WebP, and GIF images. Each image can be up to 10 MB. Winglo also limits how many images can be attached to one message and shows the current limit in the composer.

Winglo checks the actual file type, not only its filename. SVG and PDF files are not chat images.

Remove an unwanted attachment before sending. After upload, confirm that the thumbnail and filename belong to the intended task.

Add knowledge documents#

When the knowledge-document control is shown, it accepts supported text, Markdown, or PDF documents. This is different from attaching an image for visual review.

Winglo can extract suggestions from a knowledge document. Review those suggestions before saving them to department memory.

Do not upload passwords, API keys, private keys, or data the department does not need.

Involve another department#

Type @ when the composer offers teammate mentions. Choose an available department lead and explain the requested contribution.

Example:

@Sarah, review the visual brief and return brand risks to Max. Do not publish or contact anyone.

The department that owns the conversation remains the main point of contact. A handoff asks another department for help; it does not approve an external action.

Confirm proposed actions#

Some chat requests create a confirmation panel. Read the exact tool, target, and payload.

• Approve only when it matches your request.
• Reject to prevent that proposed call from running.
• If you do nothing, a guarded call does not run.

After approval, read the result. A confirmed action can still fail at a connected provider.

If chat fails#

Shorten an overly large message, remove an unsupported file, check the department and connector state, then retry once. Start a new conversation only when the old thread itself is no longer useful.