Keep work in context with team chats

Use team and group chats to coordinate work around Cloudgate projects. Keep the conversation tied to the relevant action, request, release, or support ticket so another teammate can follow it.

Start a useful conversation#

Choose the intended teammate or group and confirm its participants. Lead with the affected system and the decision or help you need.

For an investigation, include the environment, approximate request time with timezone, action name, expected behavior, and observed result. Link to the relevant log or ticket instead of pasting a large, sensitive payload.

Separate collaboration from execution#

A team conversation, an agent conversation, and a workflow run serve different purposes. Discussing a proposed fix does not apply it. An agent's completed job does not by itself prove a release was published or an incident resolved.

Record the final decision where the operational history belongs: a release description, support-ticket finding, or maintained documentation page.

Share evidence clearly#

• Link the specific request or node that failed.
• Explain whether a screenshot shows sandbox, preview, or production.
• Distinguish reproduced facts from a suspected cause.
• Include the outcome of the latest verification.

Avoid sharing credentials, raw authentication headers, or another user's private data. Redacted logs can still include ordinary personal information, so choose the minimum evidence needed by the recipients.

Close the loop#

After the change is reviewed, share the release or ticket reference and the verification result. If more work remains, state who owns it and what evidence will establish completion.

For structured investigation and review, use support tickets. For tool-assisted work, use AI agents.