Ask CoBrain for the right kind of help

Workroomly Editorial
Begin the lesson ↓

Share this resource

Copy the link to share this page with your team.

Distinguish writing, finding information and taking action so your request produces the result you need.

Ask CoBrain for the right kind of help

CoBrain can help with different kinds of work. A useful request makes the desired result clear instead of saying only “Handle this.”

Choose the job

Drafting turns information into text. For example: “Turn these meeting notes into a short internal summary. Use only the facts below.” The result is wording you can review—not a message that has already been sent.

Finding information asks for a fact from a source. For example: “What is the due date on this task?” Identify the exact task and check the source. A general answer based on supplied notes is not automatically the current saved record.

Taking action changes something or communicates it. Creating a task, sending a message or arranging a recurring action needs a clear destination and the right details. A proposed action is different from a completed one.

Prepare a clear request

1. Open CoBrain in the intended workroom and choose Ask to reach the conversation area.

2. In Message CoBrain, state what you want, provide the relevant facts and set any useful limit. For a draft, you could write:

Draft three bullets for an internal update from these facts: the agenda is ready; the checklist needs review; the review is due Friday. Do not invent an owner or say the review is complete.

Use your own accurate facts before submitting a real request.

3. Select Send message, then review the response against those facts. Check names, dates, missing information and any claim that work has been completed.

4. To revisit earlier work, use Search titles and saved messages and open the matching conversation.

Know what you have finished

A reviewed draft is ready to use as text. It does not prove that the underlying work is finished or that another person received it. If you need a separate action, make that request explicit and check the resulting record or communication.

Do not include passwords, tokens or information the conversation should not contain.

Turn what you learned into the way the team works.

Mark this lesson complete once the workflow exists in your workspace—not simply when you reach the bottom.