Enterprise CMS Content Manager

Audience: front-end end users

Scenario

After the site is live, the company still needs to keep updating news, industry articles, service pages, cases, help, and company updates. Doing all of that by hand—drafting, formatting, tagging, then publishing—is very repetitive.

The system already provides a standard Enterprise CMS Content Manager employee (application name Article Management Bot). You do not need to create an employee from scratch: click Use in the AI Employee Market to copy it into the current project. It writes and manages site content as required, except sales products. In the left AI Employee, say what to write, who it is for, and which category to publish to.

Hand the materials to the AI, say what to write, then publish to the site after you confirm.

Work type

It is responsible for what the site says and how it is updated, not how pages are built:

• Write and publish articles: company news, industry content, service intros, cases, help, company updates, and similar
• Edit existing articles, organize categories and tags, and improve titles and summaries
• Keep writing from existing materials or images, then change tone, length, or language in the same session before publishing
• Keep the site content current, instead of leaving it unchanged after launch

It does not handle sales products, orders, or prices. Page structure, blocks, navigation, and style belong to Website Building and Maintenance Manager.

Configured tools

This work is done by chatting in the left AI Employee. It does not use the website visual editor, and it does not use external chat hosting. You cannot chat from My employees. Published items can be checked in Enterprise CMS → Content List.

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

Skill and SOP

The market copy of Enterprise CMS Content Manager already has basic drafting and publishing ability. Read the matching Skill before use, as this employee requires: read the specified Skill before publishing or editing, and read the specified Skill before writing a strong article. Run tasks in order. Store questions that need a user reply, and confirmed answers, in the task steps. The company can map more Skill, SOP, and materials to match its own sections and publishing process.

Logic in brief

Use Enterprise CMS Content Manager from the market and create a session → Read Skill as required → Provide materials and say what to write, who it is for, and which category → Get a first draft → Keep changing in the same session → After you confirm, publish to site content.

Keep daily content updates for the same site in the same session. Create a new session when the section, language, or publishing rules change.

Matching human system

This matches an in-house site content operations role: people confirm the topic, brand voice, and whether to publish; repeated drafting, rewriting, tagging, and publishing go to the AI.

Steps

1. Open AI Employee → Enter market, find Enterprise CMS Content Manager (Article Management Bot), and click Use.
2. After you enter that employee, read the matching Skill first, as this employee requires.
3. Click ⋯ → New session in the top right. Rename Session name to your own content-operations name, fill in Session prompt if needed, then click Confirm.
4. In the chat box, say what to write, who it is for, and whether it goes to news, cases, help, or similar. To add materials, click the paperclip, open Add attachment, and choose Audio, Image, Camera, or File. Send and wait for the first draft.
5. If the first version is not right, keep saying how to change it in the same session. After you confirm, ask it to publish. Check published items in Enterprise CMS → Content List.
6. Use different sessions for different kinds of content or different languages.