Office Document Bot

Audience: front-end end users

Scenario

Companies regularly create and edit office files (Word, PPT, spreadsheets, and similar). Scattered materials and many versions take time to organize, lay out, and revise.

The system already provides a standard Document Designer employee. You do not need to create an employee from scratch: click Use in the AI Employee Market to copy it into the current project. In the left AI Employee, say in natural language what document you need, who it is for, and what it should include, and attach existing materials.

Hand the materials to the AI, say what you need, then keep revising in the conversation.

Work type

Create, edit, and organize enterprise office documents:

Create Word files: company intro, proposals, reports, product notes, and similar
Build PPT: intro, pitch, review, training, and similar
Organize tables: lists, quotes, plans, summaries, and similar

It can also build a new document from existing materials, or change structure, length, audience, and language as asked.

Configured tools

This work is done by chatting in the left AI Employee. It does not use external chat hosting. You cannot chat from My employees.

Setup	Purpose
AI Employee → Enter market → Use	Copy the standard Document Designer into the current project
⋯ → Enterprise Docs	First create the office文档 folder; open that folder, then add the memory Markdown; after create, click ⋯ → View info on the file and copy the url
AI Employee, Agent session	Who does the work, and which kind of document work is in progress; paste the memory url into Session prompt, and say it owns and updates that memory
Chat box paperclip	Add attachment: Audio, Image, Camera, File
Mapped document tools	Actually create and edit files (follow what is mapped to this employee)

Map extra tools, Skill, SOP, MCP, and enterprise resources when you need a closer fit to company templates or libraries.

Skill and SOP

The market copy of Document Designer already has basic document-making ability. The company can map more Skill, SOP, and materials to match its own document rules and process.

Logic in brief

Write memory inside the office文档 folder, copy the url → paste the url into Session prompt so it owns and updates that memory → provide materials and the goal → Document Designer makes a first version → keep revising in the same session.

Keep the same kind of document work in the same session. Create a new session when the customer, purpose, or rules change.

Matching human system

This matches an in-house document-making role: people spend time confirming content, communicating, and deciding; repeated organizing, drafting, and versioning go to the AI.

Steps

Open AI Employee → Enter market, find Document Designer, and click Use.
After you enter that employee, click ⋯ → Enterprise Docs in the top right. Click the folder icon, New folder, name it office文档, then click Create.
Open the office文档 folder (the top should show office文档, not the tenant root). Only then click cloud upload and choose New Markdown document. The memory file must sit in this folder. On the first line write #文档设计师记忆 (the memory name follows the employee: “[name] memory”). Click Save in the top right, rename document.md to office文档.md, then Save again.
In File info, fill in Title, Description, and Tags as needed (example: Title office, Description 记忆, Tags 记忆O1), then click Confirm.
Click ⋯ on the office文档.md you just created, choose View info, and copy the url.
Click ⋯ → New session in the top right. Session name defaults to the name you just used; rename it to your own. Paste the copied url into Session prompt, and write: this is your memory, you fully own it, and you update your own important memory. Click Confirm.

Sample:

This is your memory: (paste the url)
You fully own this memory. Update your important memory yourself.
In the chat box, say the company materials or website, and what document to make, who it is for, the focus, and the length. To add materials, click the paperclip, open Add attachment, and choose Audio, Image, Camera, or File. Send and wait for the first version. If you need changes, add requirements in the same session.
Use different sessions for different kinds of document work.