Chat course 01 — Find the right conversation and prepare a complete request

Chat is useful for clarifying a question, discussing material and agreeing the next action. A message works best when the right person can understand the request without reconstructing missing context. This chapter takes you through direct-conversation navigation and the composer, then shows how to prepare a complete request before sending.

Use an approved practice conversation and a partner who has agreed to receive a labelled training message. If no partner is available, draft locally and inspect navigation without sending to an unrelated person. The screenshots contain a separate synthetic example, not a recipient to contact.

In this chapter

• Confirm the workroom and conversation audience
• Identify the conversation controls
• Give the recipient enough material to answer
• Propose timing without inventing agreement
• Prepare the request and inspect it once more
• Practise the audience decision

Confirm the workroom and conversation audience

Read the workroom name before selecting Chat from the left navigation. A workroom can have its own conversation list. An empty list in one context does not prove a conversation is absent everywhere.

The sidebar separates TEAMS and DIRECT MESSAGES and includes Search conversations and + New. Wait for loading to settle. A connection warning is not an empty directory; use the displayed Retry when appropriate and preserve a persistent service problem for the responsible owner.

For a direct conversation, choose + New. New Chat opens Search by name or email. Search for the intended approved person and compare the full displayed identity with the person you mean. Two similar names are not interchangeable. If the intended match is absent or ambiguous, resolve it before disclosure rather than choosing the closest result.

Select the verified row, then compare the conversation header. The conversation should also appear under Direct Messages. Opening it establishes the selected audience context; it has not sent a request or obtained agreement.

A team section is not itself proof of a particular group's privacy. When using a team conversation, inspect the actual displayed audience and supported membership controls before posting. Do not infer access from a title such as Private or Leadership. Creating, inviting or changing membership is a separate audience-changing action, not a required step for this direct-message exercise.

Identify the conversation controls

The open conversation provides Messages, Media and Pins. Use Messages to read the message area and locate the bottom Message... composer. Media and Pins identify separate views; do not assume they automatically contain a file mentioned in a message or establish its permissions.

The composer holds the outgoing text. The blue up-arrow is the send control. Treat the nearby plus or other action icons according to their actual labels and current menu, not by guessing what a familiar icon means. Huddle-related controls concern a live conversation and are not substitutes for a written request or an unanswered review.

Three searches have different jobs. Search by name or email finds recipients for New Chat. Search conversations narrows the sidebar. Search messages... belongs to the open conversation. A sentence from a message entered into recipient search is not a valid test of whether that message exists.

Give the recipient enough material to answer

A complete request answers five questions: what is being reviewed, which version, why it matters, what response is needed and where the material is. Include the short material directly when appropriate, or verify the exact file and audience before relying on a link.

For practice, use this fictional plan: the objective is to rehearse a welcome checklist; the agenda has a five-minute introduction, fifteen minutes of guided practice and a five-minute recap. Ask whether any preparation step is missing, and request “Ready for practice” or “Changes needed” with one reason.

That is more useful than “Can you review this?” A title or file link alone does not supply the body. Starring a file helps organisation but does not grant access. If the reader cannot open a required file, resolve the permitted access or supply the necessary approved text rather than widening the audience indiscriminately.

Keep the request proportional. Reviewing the plan is not agreeing to run the workshop, correct every issue or accept a customer commitment. State the requested output, not a vague instruction to “handle it.” If the material has revisions, identify the version explicitly so a response about an older copy cannot be mistaken for approval of a newer one.

Propose timing without inventing agreement

If timing matters, give a calendar date, time and timezone. “Tomorrow afternoon” becomes ambiguous when read later or in another region. Ask whether the person can meet the proposed timing; entering it in your message does not make it accepted.

A reviewer and a revision owner may be different people. For example, a reviewer can identify a missing recap while the author remains responsible for adding it. Do not assign operational work merely because the recipient is willing to comment on the plan.

Prepare the request and inspect it once more

Draft the full message before committing it. A suitable local example is: “TRAINING ONLY. Please review the fictional welcome-checklist plan below: five-minute introduction, fifteen minutes of guided practice and five-minute recap. Are any preparation steps missing? Please reply Ready for practice or Changes needed, with one reason.” Include a version reference and proposed review time only when those facts are part of your actual plan.

Before sending, compare the workroom, recipient header, text, material version and any proposed timing. Remove unnecessary personal information. Check that the request does not promise an automatic task, meeting or result. The next chapter explains the single send and independent readback.

Practise the audience decision

You search by first name and find two people. Your file is starred, and you have copied its link. Your draft says “Please approve.” The correct next action is to verify the person, confirm access to the exact version and replace the vague request with a specific review question. Do not send until those points are resolved.

Your expected result is the correct conversation and a complete, reviewable draft. There is not yet a sent message, response, accepted task or finished review.