Přeskočit na hlavní obsah

Use Chat Effectively

Chat is the fastest place to ask, draft, compare, summarize, and work with files. It can also continue into agent work, task creation, tool calls, and realtime conversations when those capabilities are enabled.

Write Requests The Agent Can Execute​

Good chat requests include four parts:

  • Source: the file, conversation, data collection, memory page, URL, or pasted text to use.
  • Goal: what should be produced or decided.
  • Constraints: tone, length, audience, allowed sources, deadline, or system limits.
  • Next action: whether to only draft, ask for confirmation, create a task, or prepare an external action.
Use the attached customer email and the Support FAQ data collection. Draft a reply for a non-technical customer, under 120 words, and do not send it.

Use Files Deliberately​

Attach files when the agent needs current context that is not already in Data or Memory. Name what each file is for: summarize, extract action items, compare two versions, clean a CSV, draft a report, or inspect a screenshot.

If the work should be reused by many users, move the source into Data or Memory instead of reattaching the same file in every chat.

Before A Tool Action​

Ask for a preview before external writes:

Prepare the Jira ticket, but show me the summary, description, priority, and acceptance criteria before creating it.

When a tool runs, the conversation can show status and approval behavior. If something looks wrong, open Tool Executions and inspect the action, arguments, result, and approval state.

Prompt Patterns That Work​

Summarize a source​

Summarize this recording into decisions, risks, owners, and follow-up tasks. Quote only short fragments when needed.

Compare files​

Compare these two PDFs. Return only changed obligations, missing sections, and open questions in a table.

Continue later​

Turn this into a task for the Sales Operations agent. Include context, expected output, and what needs review.

Use a data collection​

Answer only from the Q2 Product Feedback data collection. If the answer is not there, say what is missing.

When Chat Is Not Enough​

Move from Chat to:

  • Agents when the work needs a prepared role, tools, and controlled data.
  • Tasks when work needs status, ownership, or review.
  • Data when files or synced sources should be reused.
  • Workflows when the same steps should run repeatedly.
Naposledy aktualizováno