Mastering the OUPI Chat: From First Message to Team Collaboration · Lesson 5 of 7

5. Handing Off Complex Tasks to @oupi

Understand when and how to delegate multi-step missions to @oupi so they run in the background while you continue working, with progress and notifications in the conversation.

In the OUPI Chat, most questions get an instant reply. But some tasks are bigger: they need several steps, several tools, or simply more time. That's when you hand the work to @oupi. Think of it as delegating a mission to a capable assistant.

Examples of good hand-off tasks: • "Prepare a briefing from these five reports." • "Clean this spreadsheet, then chart the results." • "Find and compare competing offers on this topic."

You ask for it right inside the conversation — just describe what you need and mention @oupi. The mission then runs in the background: you can close the chat, switch to another conversation, or keep working elsewhere. Progress updates appear directly in the same conversation thread, so you always know where things stand.

Once a mission is running, two things can happen:

It finishes on its own. You receive a notification that the mission is complete, and the results (documents, charts, summaries) appear in the conversation — often as artifacts you can preview and edit in the Atelier side panel.
It needs your input. Sometimes @oupi reaches a decision point and asks you a question before continuing. You'll be notified so you can jump back in, answer, and let the mission resume.

This means you're never blocked waiting. You stay productive while @oupi handles the heavy lifting, and you only intervene when your judgment is actually needed.

Missions become even more powerful when combined with other Chat capabilities:

• Attached files & knowledge bases — Give @oupi the documents it needs by attaching them or selecting a knowledge base, so answers are grounded and cited. • Connected tools (MCP) — If your external tools (Microsoft 365, Google Workspace, CRMs, etc.) are connected, @oupi can read and act in them during the mission. • OupiBox sandbox — When a mission involves code execution or heavy file processing, it runs safely in an isolated environment. • Workspaces — In a team workspace, you can launch a mission for the whole group; every member sees progress and results, each in their own language.

Tip

Keep your mission request specific. Instead of "analyze this data," say "clean the duplicates in this spreadsheet, calculate monthly totals, and create a bar chart." The clearer your steps, the better @oupi can execute without needing to ask you follow-up questions.

Tip

Missions use credits proportional to the work involved — the tokens, the model, and any sandbox processing. For everyday multi-step tasks, the balanced model keeps costs low. Save frontier models for the steps that truly need them.

Try it now

Go to the Chat, attach a document (or pick one from your files), and type a multi-step request — for example: "@oupi, summarize this document, extract the key figures into a table, and create a chart." Watch the mission progress appear in the conversation and explore the results in the Atelier when it finishes.

Take this course in OUPI → This exercise is done inside the OUPI platform.

Recap

When a task needs several steps, tools, or time, hand it to @oupi right in the conversation. The mission runs in the background — you'll see progress updates and get notified when it's done or needs your input. Combine hand-offs with attached files, knowledge bases, connected tools, and team workspaces for maximum impact. Be specific in your request, and remember that mission costs follow the same credit logic as regular messages.