Working with Operator

Talking to Operator

Ask for outcomes instead of writing prompts. Operator already holds your business context.

4 min read

Operator already holds your business context, so you ask for outcomes rather than writing prompts. This guide explains how to phrase requests and what to expect back.

1. Treat it as an operator, not a blank chat

Operator is not a blank chat session. It already holds context about your workspace, the systems you connected and the work in progress. You can speak to it the way you would brief a capable colleague.

2. What a request looks like in practice

Here Operator is asked a plain question about the day. It checks the connected calendar, works through the steps in view and comes back with the answer. You can see each action it took while it works.

WATCH: ASK OPERATOR A QUESTION

Ask in plain language, watch the live work steps as Operator checks the connected systems, and get the answer back in the same thread.

3. Good requests

  • Which leads still need a response?
  • What changed with this account?
  • Prepare follow-up for yesterday's meeting.
  • What needs my approval today?

4. Ask for outcomes

Clear outcomes work better than technical prompt engineering. Name the result you want and, where it matters, the constraint: the account, the timeframe or the tone.

If a request would make sense to a new team member with access to your tools, it will make sense to Operator.

Continue learning

Using voice with Operator

Speak a request and let Operator transcribe it, evaluate it against business context and prepare the work.

3 min read

Your Morning Brief

Understand how Operator turns overnight activity across your connected systems into one short operating summary.

4 min read

Reviewing suggested actions

What to check before approving work Operator prepared for you.

4 min read