Master Vs Sub Agents: Telegram AI Agent Architecture

A Telegram AI agent on its own is fine — but the real unlock is the master agent + sub-agents architecture.

Most Telegram AI agent tutorials show you how to build ONE agent.

That's fine for casual users.

For real business use, you need multiple agents working as a team.

That's where master + sub-agents come in.

This post is the architecture deep-dive.

What Is A Master Agent?

A master agent sits at the top of your Telegram AI agent stack.

It listens to every incoming message.

It decides which sub-agent should handle the message.

It routes accordingly.

You don't talk to the master directly (usually).

It's the dispatcher.

What Are Sub-Agents?

Sub-agents are specialists.

Each one has ONE job.

Examples:

Welcome sub-agent — greets new community members.
FAQ sub-agent — answers common questions.
Sales sub-agent — handles pricing and buying questions.
Support sub-agent — handles existing customer issues.
Spam filter sub-agent — identifies and dismisses spam.
Escalation sub-agent — routes complex issues to a human.

Each sub-agent has a focused system prompt.

They don't try to do everything.

That's why they're good at what they do.

Why Architecture Matters

Single agents fail because:

They're trying to do too many things.
Their system prompts get bloated and contradictory.
They make decisions outside their expertise.

Master + sub-agents fix this:

Each sub-agent has clear, narrow scope.
Master agent's only job is routing.
Easier to test each component.
Easier to update one without breaking others.

This is the same multi-agent pattern from OpenClaw computer use and ClawX OpenClaw — applied to Telegram.

Designing Your Architecture

Three steps.

1 — List the message types you receive

Categorise:

New member welcomes.
Common questions (top 5).
Pricing / sales questions.
Existing customer issues.
Spam / off-topic.
Complex issues that need YOU.

2 — Map each type to a sub-agent

One sub-agent per type.

Don't combine.

Even if two types are similar, separate them.

3 — Build the master prompt

The master's job is simple:

"For each incoming message, decide which sub-agent should handle it. Route accordingly."

Give it explicit rules:

"If the message is from a new member, route to Welcome sub-agent."
"If the message asks about pricing, route to Sales sub-agent."
"If the message looks like spam, route to Spam Filter sub-agent."
"If unsure, route to Escalation sub-agent."

🔥 Want my full master + sub-agent prompt templates? Inside the AI Profit Boardroom, I share my exact master prompts, sub-agent specs for community, sales, support, and escalation. Plus weekly live coaching where you can share your screen for help. 2,800+ members. → Get the templates

How Lobster Father Implements This

Lobster Father supports the master + sub-agent pattern natively.

Setup flow:

Build each sub-agent as a separate agent in your platform (Tealaw, GPT agents, Lazy AI).
Create a master agent in Lobster Father.
Configure routing rules in the master.
The master uses your Lobster Father token to invoke sub-agents as needed.

The platform handles the orchestration.

You handle the prompt design.

Common Architecture Mistakes

1. Master doing real work.

The master's only job is routing.

If it starts answering questions itself, you've lost the architectural benefit.

2. Too many sub-agents.

5-7 sub-agents is plenty for most use cases.

20+ becomes hard to maintain.

3. Overlapping sub-agent jobs.

Each sub-agent should have ONE job.

If two overlap, your master gets confused about routing.

4. No fallback.

Always have a fallback (usually an Escalation sub-agent that loops in a human).

If the master is uncertain, route to fallback.

A Worked Example — Community Manager Setup

Real architecture I run.

Master agent prompt:

"You're the dispatcher for Julian's Telegram community. For each message, decide:

New member? → Welcome sub-agent.
Pricing/buying question? → Sales sub-agent.
Question about courses? → Course FAQ sub-agent.
Existing customer issue? → Support sub-agent.
Spam/off-topic? → Spam sub-agent.
Anything else? → Escalation sub-agent (Julian)."

Welcome sub-agent prompt:

"You greet new community members. Ask their name and what they're looking to learn. Suggest the most relevant intro resource. Keep it warm but brief."

Sales sub-agent prompt:

"You handle pricing and buying questions. Refer to my pricing page. Don't quote numbers from memory. Direct serious buyers to book a discovery call."

Course FAQ sub-agent prompt:

"You answer common questions about my AI Profit Boardroom courses. If unsure, escalate to Julian."

Each sub-agent is short.

Focused.

Predictable.

That's why the system works.

Scaling The Architecture

When your business grows:

Add specialised sub-agents.

E.g. one for affiliate questions, one for partnership requests, one for podcast/media inquiries.

Add tiered routing.

Master → Tier 1 dispatcher → specific sub-agent.

For high-volume operations.

Add cross-platform agents.

Same master logic, but routes to agents on Slack, Discord, email — not just Telegram.

I cover the cross-platform side in Hermes Open Web UI.

Maintenance

Architectures need maintenance.

Weekly:

Read 10 random conversations.
Look for routing mistakes (master sent to wrong sub-agent).
Look for sub-agent mistakes (right sub-agent gave wrong answer).
Update prompts to fix.

Monthly:

Review the routing rules.
Are any sub-agents underused?
Are any sub-agents overloaded?
Adjust scope as needed.

How To Test The Architecture

Before going live:

Send 20 test messages of different types.
Confirm each routes to the right sub-agent.
Confirm each sub-agent gives a sensible response.
Adjust where needed.

Don't deploy untested.

What This Architecture Doesn't Do

Be honest.

It can't make complex business decisions.
It can't replace nuanced sales conversations.
It can't handle highly emotional customer situations.

For these, escalation is the right answer.

When Single-Agent Is Enough

You don't always need multi-agent.

Single agent is fine if:

You only have one clear use case (e.g. just FAQ).
Volume is low (<10 messages/day).
You're testing the waters.

Once you're past that, master + sub-agents is the upgrade.

🚀 Want my full Telegram AI agent architecture templates? The AI Profit Boardroom has my exact master + sub-agent templates, daily training, weekly live coaching, and 2,800+ members. → Join here

FAQ — Telegram Master + Sub Agents

Do I need multiple sub-agents on day one?

No — start with 2-3, add more as you find gaps.

Can the master agent itself reply?

Yes, but it's a design smell.

Keep master as router only.

How does the master decide where to route?

Based on rules in your master prompt.

LLM-based routing usually works well.

Will sub-agents see each other's conversations?

Depends on your platform.

Most don't share by default — by design.

Can sub-agents call each other?

Yes — Telegram supports agent-to-agent communication on the new infrastructure.

How many sub-agents are too many?

Past 7-10 it gets hard to maintain.

What if my routing is wrong?

Update the master prompt.

Iterate weekly.