07 — OpenClaw Multi‑Agent Guide (Run a Receptionist, Marketing Assistant, and Ops Helper Without Chaos)

One OpenClaw agent can do a lot.

But “one assistant for everything” eventually becomes the same problem as “one inbox for everything.”

You’ll notice symptoms:
- customer messages get an internal tone (or vice versa)
- marketing ideas leak into ops checklists
- the agent remembers something from a private internal thread and references it in a customer reply (bad)
- the agent uses the wrong tool for the moment (e.g., web browsing when it should ask you a question)

Multi-agent solves this by giving you role separation.

You don’t want one “super agent.”

You want a small org chart.

---

1) What “multi-agent” means (plain English)

Multi-agent OpenClaw means:
- one agent per role (department)
- one workspace per role (separate rules + tone + memory)
- routing that sends tasks/messages to the right agent

Think:
- Receptionist agent answers inbound leads.
- Marketing agent produces content drafts.
- Ops agent summarizes the day and tracks follow-ups.

This is how real small businesses work: specialization beats generalization.

---

2) Why multi-agent helps (the real benefits)

Benefit A: Less “tone mixing”

Customer-facing communication should be warm, short, and clear. Internal ops communication should be direct, checklist-heavy, and sometimes blunt.

Separate agents keep those voices distinct.

Benefit B: Cleaner memory

Each agent stores memories relevant to its job. - Receptionist remembers lead intake rules and FAQs. - Ops remembers SOPs, open loops, and decisions.

This reduces confusion and improves consistency.

Benefit C: Safer tool boundaries

You can restrict risky actions by role. For example: - Receptionist: draft-only, never sends externally without approval. - Ops: may update internal files, but never messages customers. - Marketing: generates drafts but never posts.

Benefit D: Easier scaling

Once you can trust a department, you can delegate more work to it.

---

3) When to stay single-agent (don’t overbuild)

Stay single-agent if:
- you have fewer than 3 repeatable workflows
- you are still finding your tone and rules
- you want minimal setup and maximal simplicity

A single, well-trained agent beats three half-trained agents.

A good signal you’re ready for multi-agent:
- You keep writing “ignore previous context” or “switch tone” in prompts.

---

4) The simplest org chart that works (the “Starter 3”)

If you want a clean, proven structure, start here.

Agent 1 — Receptionist (customer-facing intake)

Jobs - respond to new inquiries (draft) - ask 1–2 clarifying questions - propose 2 scheduling windows - tag urgency

Tone
- warm, fast, plain English

Hard rules
- draft-only for external messages
- no pricing promises unless pricing rules are explicitly provided
- no arguing with angry customers; calm escalation

Good for
- service businesses (home services, studios, clinics)

---

Agent 2 — Marketing (creative production)

Jobs - weekly content plan - write 5 post ideas + 3 hooks each - repurpose long form → short form - draft promotions and newsletters

Tone
- brand-forward, creative

Hard rules
- never post without approval
- avoid hallucinated claims (no “#1 in town” unless verified)
- produce options, not one “perfect” answer

---

Agent 3 — Ops (execution + logging)

Jobs - daily summary - follow-up tracking - SOP/checklist generation - log decisions + open loops into memory

Tone
- calm, direct, bullet-first

Hard rules
- prefer checklists
- always separate “facts” vs “assumptions”
- never message customers directly

---

5) Workspaces: what each agent should contain

Every agent can share the same file structure, but the content differs.

Recommended shared structure

- AGENTS.md — operating rules and safety boundaries - SOUL.md — tone and personality (role-specific) - USER.md — who the agent is helping and goals - TOOLS.md — how to use tools safely (role-specific) - IDENTITY.md — explicit role label (“Receptionist Agent”) + purpose - HEARTBEAT.md — periodic checklist tasks (role-specific) - memory/ — daily notes and state

Example SOUL.md (Receptionist)

Tone: warm, fast, friendly.
Boundaries:
- Draft only. Never send externally without approval.
- Ask 1–2 questions max.
- No pricing promises.
Escalate:
- angry customer, refunds, legal threats → draft + alert owner

Example SOUL.md (Ops)

Tone: calm, direct, bullet-first.
Boundaries:
- Prefer checklists.
- Log decisions and open loops daily.
Formatting:
- One-line headline, then bullets.

---

6) Routing: how messages get to the right agent

Routing answers one question:

> “When something comes in, which agent handles it?”

In plain English, it’s:
- if this looks like X, send to Y
- else send to default

Example routing rules (human-readable)

- If message contains “price, quote, estimate, availability” → Receptionist - If message contains “post, caption, newsletter, campaign” → Marketing - If message contains “summary, status, today, priorities, follow-up list” → Ops - Otherwise → General / Owner assistant

Common routing mistake

Mistake: routing based on who sent the message only.

Fix: combine sender + intent.
For example:
- customer phone line always goes to Receptionist
- internal Slack message might go to Ops or Marketing depending on keywords

---

7) Safety governance (non-negotiables)

Multi-agent feels powerful. That’s why governance matters.

Three controls prevent most disasters:

Control 1 — Approval before external sending

Put this rule everywhere:

- Never send externally without explicit approval.
- Draft first and ask.

Even if you later relax it, start strict.

Control 2 — Separate customer-facing from internal ops

If you do only one thing, do this.

It reduces the chance that:
- internal notes leak to customers
- the agent references private info

Control 3 — Logging decisions + open loops

Your Ops agent should write to daily memory: - what was decided - what is pending - who owns the next action

This creates continuity and makes the system feel reliable.

---

8) Two end-to-end workflows (what it looks like in reality)

Workflow A — New lead comes in

1) Customer messages your business line. 2) Routing sends it to Receptionist. 3) Receptionist drafts: - a reply - 1–2 clarifying questions - proposed scheduling windows 4) Owner approves the draft. 5) Ops logs: - lead name/contact - requested service - next follow-up date

Why this works: it matches a real office.
Front desk handles intake, owner approves sensitive communication, ops keeps records clean.

---

Workflow B — Weekly marketing push

1) Owner asks Marketing: “Plan next week’s content.” 2) Marketing produces: - 5 post ideas - 3 hooks each - 1 newsletter outline - 1 repurposing plan 3) Owner selects. 4) Marketing drafts final versions. 5) Owner approves and posts. 6) Ops logs what shipped and what’s next.

Why this works: Marketing stays creative, Ops stays organized.

---

9) Step-by-step: how to migrate from 1 agent to 3 agents

If you already have a single agent, you don’t need to start over.

Step 1 — Identify your “departments”

List what you repeatedly do. Example: - handle inbound leads - post content - track follow-ups

Group them into 2–3 roles.

Step 2 — Clone the workspace structure

Create new workspaces with the same file set. Keep consistency in filenames so you can maintain them easily.

Step 3 — Rewrite SOUL.md per role

Don’t just copy/paste. Make the tone and boundaries *role-appropriate*.

Step 4 — Move rules into the right place

- Receptionist rules: questions, tone, escalation - Marketing rules: claims, compliance, brand voice - Ops rules: checklists, logging, clarity

Step 5 — Add a default routing fallback

Always have a “General” handler. Some messages won’t match.

Step 6 — Run a 1-week pilot (draft-only)

For one week: - no auto-sending - no auto-posting - you review everything

Track:
- how often routing was wrong
- what recurring mistakes happened

Step 7 — Patch, then scale

Only after the pilot: - add automations (internal first) - relax approvals in very limited, low-risk cases

---

10) Common failure modes (and how to prevent them)

Failure mode 1: “Agent ping-pong”

A task bounces between agents.

Fix: define ownership.
- Receptionist owns customer intake.
- Ops owns tracking + logging.
- Marketing owns content.

If it crosses departments, it’s a handoff, not ping-pong.

Failure mode 2: Unclear escalation rules

The agent guesses.

Fix: write escalation triggers.
Examples:
- refunds
- legal threats
- angry tone
- medical/financial advice

Failure mode 3: Too many agents too soon

You create 7 agents and none are well-trained.

Fix: start with 1, then 3.
Only add a new agent if it owns a *department*, not a micro-task.

Failure mode 4: Memory contamination

The receptionist remembers internal pricing discussions and references them externally.

Fix: separate workspaces, plus strict “draft-only + approval” for external.

---

11) Scaling beyond 3 agents (when it’s actually worth it)

Only do this when your core system works.

Common additions:
- Finance agent: invoice follow-up drafts, payment reminders (still approval)
- Customer success agent: post-job check-ins, review requests, referral prompts
- Hiring/HR agent: job posts, screening questions, interview scorecards
- Research agent: competitor scans, vendor comparisons

Rule of thumb:
- one agent per department
- not one agent per tiny task

---

FAQ

Do multi-agent systems cost more?

They can. You may run more prompts and more tool calls. But the payoff is reliability: less rework and fewer mistakes.

How do I know routing is working?

Keep a simple log for a week: - correct routing? - corrections needed? - time saved?

If routing is wrong often, tighten your rules or reduce ambiguity.

Can two agents share memory?

They *can*, but they usually shouldn’t. Shared memory is where tone mixing and leakage happens.

Instead:
- let Ops summarize and copy only the necessary “decision” into a shared place

What’s the safest default for customer-facing agents?

- Draft-only - Approval required - Escalation rules - No direct tool actions that send messages without permission

---

Quick start checklist (copy/paste)

If you want a simple plan for this week:

1) Keep your existing agent as “General.”
2) Create a Receptionist agent workspace.
3) Create an Ops agent workspace.
4) Add routing rules (keywords + channel).
5) Set both to draft-only.
6) Run for 7 days.
7) Review mistakes and write new rules.
8) Add Marketing only after the first two feel stable.

---

Related Guides

- Workspace Files Explained: /guides/02-workspace-files - SOUL.md Deep Dive: /guides/04-soul-md - Skills Explained: /guides/06-skills - HEARTBEAT.md Deep Dive: /guides/03-heartbeat-md