Hermes WhatsApp group chat support earns a solid verdict for access control and a weaker one for platform risk: the permission model is careful and deny-by-default, but groups only run on an unofficial bridge.

This review rates it from the official Hermes docs, criterion by criterion, so you can see where it fits and where it falls short.

If you want a view on whether it suits your business, book a free SEO strategy session with my team.

The Verdict In One Paragraph

For a team that already works in WhatsApp groups and is willing to run a dedicated bot number, Hermes gives you tight control over which groups, which people and which messages reach the agent.

The cost is the platform. Groups need the Baileys bridge, which emulates WhatsApp Web, and the docs themselves flag a small risk of account restrictions.

The official Cloud API adapter, which removes that risk, doesn't do groups yet.

Rating overall: 7 out of 10. Strong for internal team groups, weaker for customer-facing ones.

Scorecard

Ratings are editorial judgement from the documentation, out of 10.

CriterionRatingWhy
Group access control9Four group policies, deny-by-default, group JID allowlist
Sender control inside groups9Participants still checked against the sender allowlist or pairing
Noise control8Mention-only mode with per-chat exemptions
Context handling8Per-sender sessions by default, shared session as an option
Scheduled posting8Cron delivery to a group JID, plus a home channel
Setup effort6Node.js, QR pairing, two config files, manual JID handling
Multiple agents per number3One number is one session; profiles can't split chats
Official platform support for groups4Groups need the unofficial bridge; Cloud API is DMs only in v1

How to read it: the top five rows are about what Hermes itself controls, and they score 8 or 9. The bottom three are about setup and platform, and they pull the average down.

The overall 7 isn't a straight average. It weights the platform limit heavily, because a business can tune every setting perfectly and still be exposed by the bridge.

What This Review Covers

The scope is groups only: how Hermes Agent decides whether to read, answer or ignore a WhatsApp group message.

Sources are the WhatsApp (Baileys) page, the WhatsApp Business Cloud API page, the environment variables reference, the configuration page and the FAQ.

Each rating ties back to a documented behaviour. Where the docs are silent, such as on any cap on group size or group count, the review says nothing rather than guess.

DM setup, voice notes and the Hermes Desktop group rooms are outside this review. Those Desktop rooms are a separate Bot Mode feature, not WhatsApp groups.

Strength: Deny-By-Default Group Intake

This is the best design choice here.

The group policy starts on pairing, and that value forwards nothing from groups. A freshly paired bot can be added to any group and still won't act on a single message.

From there you move up one step at a time: allowlist for named group JIDs, or open for every group the bot is a member of. A fourth value, disabled, shuts groups off explicitly.

The docs state the rule in one line: "Groups are gated by group policy, not by the DM allowlist."

That separation is right. Trusting a person in DMs shouldn't automatically trust every group they drag the bot into.

๐Ÿ”ฅ Want to build agents the careful way? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members to compare setups with. โ†’ Join the AI Profit Boardroom

Strength: Two Layers Of Permission

Group admission is layer one. Sender checks are layer two.

With a sender allowlist set, each participant must be on it or paired, even inside an admitted group.

The open policy doesn't skip this. Participants still need pairing or the allow-all flag.

The one place the second layer relaxes is allowlist with no sender list, where every participant of a listed group is admitted. That's a reasonable default for a closed staff group, and it's documented, so nobody is surprised.

Also worth noting: with no access control at all, the gateway denies every incoming message.

Strength: Mention Gating With Exceptions

By default, every admitted message gets a reply. In a group, that's rarely what you want.

WHATSAPP_REQUIRE_MENTION=true narrows it to @mentions, replies to the bot and slash commands.

The free_response_chats list lets chosen groups opt back into full replies. One setting, one exception list, clear behaviour.

Two smaller touches help in busy groups. A rapid burst of messages from one chat is batched into a single request after a short quiet period, 0.3 seconds by default, so the bot replies once. And when Hermes needs a multiple-choice answer, it can send a native poll; approval prompts are never turned into polls.

Points off because the WhatsApp page documents only this switch. The richer group options on the Telegram page, such as custom mention patterns, aren't documented for WhatsApp, so don't expect them.

Strength: Per-Sender Sessions

group_sessions_per_user defaults to true, giving each participant their own session when the platform supplies a user ID.

That stops one person's long, tool-heavy task from bloating everyone else's context.

Flip it to false for one shared room session, with the documented trade-off: shared token costs, interrupt state and context growth.

Quoted replies add useful context too. Quoting an earlier image, voice note, video or document attaches that file to the turn, so "what is this?" under a quoted photo works.

WhatsApp IDs are canonicalized across JID and LID alias changes, per the session lifecycle docs, so people don't get split into duplicate sessions.

Limit: An Unofficial Bridge

This is the biggest mark against it.

The Baileys bridge emulates WhatsApp Web. The docs say WhatsApp doesn't officially support third-party bots outside the Business API, and using a bridge carries a small risk of account restrictions.

WhatsApp also updates its Web protocol from time to time, which can break the bridge until Hermes updates the dependency and you re-pair.

The session itself needs care. The docs say the session folder contains full credentials for the WhatsApp account and should be protected like a password, never shared or committed.

The mitigations are sensible: a dedicated number, no bulk messages, no unsolicited outbound messages. But they reduce the risk rather than remove it.

Limit: Cloud API Stops At DMs

The official route exists. It just doesn't reach groups.

The Cloud API page says Hermes's whatsapp_cloud adapter "currently handles direct messages only" in v1, and tells readers to use the Baileys bridge for groups.

So the safest WhatsApp path and the group feature don't overlap today. That's the main reason the platform score sits at 4.

๐Ÿ“ž Weighing up AI tools for your team? Book a free SEO strategy session and we'll go through which agent setup fits the way your business already works. โ†’ Book your free session

Limit: One Number Per Agent

The FAQ is clear: one WhatsApp number is one Baileys session, and you can't bind several Hermes profiles to different chats on that number.

If you want one agent for the sales group and another for the ops group, you need two numbers, or a single profile that adapts with personality switching.

Telegram and Discord handle per-chat binding more naturally, according to the same FAQ.

A second profile on its own number is supported. You pair it with hermes -p work whatsapp, and if each profile runs its own gateway, each one needs a distinct bridge port in its config, per the WhatsApp page.

That works, but it means more numbers, more phones to keep linked and more sessions to protect. For most small teams, one well-configured profile is the better call.

Limit: Finding The Group JID

Allowlisting needs the group's JID, in the form shown in the docs, ending in @g.us.

The WhatsApp page doesn't document a dedicated lookup command. It documents a debug switch, WHATSAPP_DEBUG=true, that writes raw message events to bridge.log.

The rest of setup is ordinary for a self-hosted agent: Node.js v20 or newer, a pairing wizard that shows a QR code, and access settings split between ~/.hermes/.env and config.yaml.

Changing those settings later is painless. The docs say any bridge setting change restarts the bridge on the next connection without re-pairing.

That's workable for an operator, but it's the roughest edge in an otherwise tidy setup, and it's why setup effort scores 6.

Who Should Use It

  • Small teams that already coordinate in WhatsApp groups and want an agent answering inside them.
  • Operators comfortable with a terminal, a QR pairing step and editing config files.
  • Businesses happy to run a separate bot number apart from their main line.
  • Anyone who wants scheduled posts into a group, such as a daily digest, through cron delivery to a group JID.

Who Shouldn't

  • Businesses that can only accept the official Meta-supported path. For them, groups aren't available yet.
  • Teams that need several independent agents on one number.
  • Anyone planning bulk or cold outbound messaging, which the docs warn against outright.

For the DM side of the same integration, see the Hermes Agent WhatsApp verdict.

Final Verdict

Hermes treats a WhatsApp group as something you opt into, then filters by group, by person and by mention. That's the right model for an agent that can take actions.

What holds the score back is outside its control: groups depend on an unofficial bridge, and the official API path is DMs only for now.

For internal team groups on a dedicated number, it's a clear yes. For customer-facing groups on your main business line, wait for the official path to cover groups.

The sensible trial is small: one dedicated number, one test group, an allowlist with that group's JID, mention-only replies, and a week of real use before any staff group sees it.

Scheduled posting is the quiet winner in that trial. Cron jobs can deliver into a group with a whatsapp: target and the group's JID, as the cron docs show, which suits daily digests and reminders.

To learn how to set up and run agents like this end to end, the AI Profit Boardroom has the trainings.

Also On Our Network

FAQ: Hermes WhatsApp Group Chat Verdict

What is the overall rating for Hermes in WhatsApp groups?

7 out of 10 on our editorial scorecard. Access control scores highest; official platform support for groups scores lowest.

Is the Hermes group setup safe to use on my main number?

The docs advise a dedicated number, because the Baileys bridge is unofficial and carries a small risk of account restrictions.

Does open mode let anyone in a group use the bot?

No. Under open, participants still need to be paired or covered by WHATSAPP_ALLOW_ALL_USERS.

Will Hermes groups work on the WhatsApp Business Cloud API later?

The docs only say the adapter handles direct messages only in v1. No date for group support is published.

๐Ÿ“บ Video notes + links to the tools ๐Ÿ‘‰

๐ŸŽฅ Learn how I make these videos ๐Ÿ‘‰

๐Ÿ†“ Get a FREE AI Course + Community + 1,000 AI Agents ๐Ÿ‘‰

About Julian

I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

  • I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
  • I've grown a YouTube channel to 400,000+ subscribers.
  • I wrote "Link Building Mastery".
  • My Udemy courses have taught over 29,000 students.

โ†’ Get my best AI training inside the AI Profit Boardroom

Use it for internal team groups on a dedicated number, and if you want help deciding where it fits, book a free strategy session or learn the setup inside the AI Profit Boardroom before you commit to a Hermes WhatsApp group chat.