WhatsApp group moderation
Keep your WhatsApp groups in order without reading every message.
Sedge catches repeated posts, invite spam, unwanted links and flooding in the groups your organisation runs. When it removes someone, a person makes the final call, with the reasons in front of them.
- Every group starts in monitor mode. Nobody is removed until you turn enforcement on.
- Sedge never looks at “last seen”. Activity counts only what your connected account saw in the group.
Who this is for
Organisations that ended up running a WhatsApp group, and now have to moderate one.
Not because they wanted a moderation problem: that is where their members already are. The groups below are the shape of the ones Sedge was built against.
A committee that has to reach a decision
One question, forty replies, and three of them are the same forwarded message. The thread is unreadable by the time the people who needed it get to their phones.
Repeated content
A society with a members’ group
Someone drops an invite link to a group nobody asked about, and two members mention everybody at once to be sure they are seen. Neither person is malicious.
Group invite spam
A club with a Saturday morning
Four hundred people, a dozen who post every week, and a long tail who joined in March and have not said anything since. Somebody has to decide what to do about that.
Inactivity schedule
The collage was generated for this site and shows no Sedge customer. Image credits.
What it does
Five jobs, done consistently, at a volume nobody can match by hand.
Sedge is not trying to replace your moderators. It is trying to hand them a shorter, better-ordered list of decisions.
Keep communities clean
Every message in a protected group is scored against the rules you configured, as it arrives.
Read moreReduce spam
Flooding, repeated content, invite links, blocked domains and mass mentions, weighted rather than absolute.
Read moreIdentify inactive members
Warn on a schedule you set, then remove into a review queue at the day count you choose.
Read more- Give moderators controlEvery removal opens a case a person decides. Restore, ban, whitelist, exempt or extend.
- Automate the repetitive partWarnings, strike expiry, inactivity scans and review placement run on their own schedule.
- Show the workingA score, the rules behind it, the evidence numbers, the threshold and the action. Recorded for every event.
Monitor first
See what Sedge would do before you let it do anything.
Every group begins in monitor mode. Rules run and events are recorded, and a removal shows as “would have removed”. Nobody leaves a group until an admin turns enforcement on. Try the switch.
Member ending ··31in Riverside Residents
Free trading signals, last few places. Join here: chat.whatsapp.com/K3f…9pQPosted three times, in two groups
- Group invite spam+35
- Repeated content+30
- Message flooding+20
- 2 more reasons in the full record+50
135removes at 100
Would have removed this member.
Nothing happened in the group. In monitor mode Sedge records what enforcement would do and leaves the member where they are.
Scoring
No single signal removes anybody.
Weights add up. A member has to trip several rules, or one rule repeatedly, before the score reaches the removal band. That is what keeps one noisy heuristic from turning into a false-positive machine.
Default thresholds
- 0+No action
- 40+Logged
- 60+Warned
- 80+Sent to review
- 100+Removed
Every band, and every weight behind it, is yours to change: per organisation, per WhatsApp account, per community, or per group.
The rules Sedge ships with
Message flooding
FloodingMany messages sent in a short burst.
+20Repeated content
Repeated contentThe same or near-identical message posted more than once.
+30Repeated links
LinksThe same URL posted repeatedly, or an unusual number of links at once.
+30Group invite spam
LinksInvite links to other WhatsApp groups, posted by a non-admin.
+35Blocked domain
LinksA link to a domain on the organization blocklist.
+50Mass mentions
MentionsTagging a large number of members at once.
+20Media flooding
Media floodingRapid runs of images, stickers, voice notes or video.
+20Promotional language
Words and phrasesWording characteristic of advertising and recruitment spam.
+20Automated posting pattern
Posting patternMachine-like regularity, or the same content across many groups. Posting often is not enough on its own.
+20New member probation
New membersStricter handling during a new member’s first hours in the group.
0Previous warning
HistoryThe member has been warned before.
+30Known offender
HistoryThe member has been removed for spam before.
+40Trusted member
HistoryA whitelisted member. Negative weight, so trust actively offsets signals.
−100
These are the platform defaults, exactly as a new organisation receives them. Trust carries a negative weight, so a whitelisted member’s score is actively pulled down.
- 135
The score reaches the line
Removal is set at 100. One rule alone never gets there.
- Case
The member is removed and a case opens
Under enforcement only. In monitor mode it is recorded as “would have removed”.
- You
A person decides
Restore member or keep removed, with every reason in front of them.
Review queues
A spam removal and an inactivity removal are different decisions.
So they are different queues, with different evidence and different outcomes. One table with a filter would make a reviewer work out which kind of case they are looking at.
Spam review
Members removed because a rule scored past the removal threshold.
What the reviewer sees
- The score and the threshold it crossed
- Every rule that fired, with its weight and evidence
- Message excerpts, where retention allows
- Links and domains seen
- Active strikes against the member
- Whether the action was carried out or simulated
Decisions offered
- Restored
- Kept removed
- Banned
- Whitelisted
- Dismissed
- Information requested
- Reclassified
Inactive review
Members removed for going quiet past your inactivity limit.
What the reviewer sees
- Days since the member last took part
- When they were last observed, and what they did
- When they joined the group
- Total messages, and messages in the last 30 and 90 days
- Warnings already sent, and when
- Whether they are a group admin
Decisions offered
- Restored
- Kept removed
- Exempted
- Extended
- Banned
- Dismissed
How it works
Watch first. Enforce when the numbers look right.
A new group starts in monitor mode. You see exactly what Sedge would have done, on your real traffic, before it does anything at all.
Connect a WhatsApp account
Pick a provider, authenticate, and let Sedge discover the groups it can see. The wizard is resumable: leave it and come back.
Choose the groups to protect
Only the groups you select are watched. Everything else is left alone, including groups the same account is in.
Tune the rules
Start from the defaults, then change weights, thresholds and windows. A change can be tested against a real recent message before you save it.
Run in monitor mode
Rules run, events are recorded, nothing is removed. Every event shows what would have happened and why.
Turn on enforcement
One group at a time, with an explicit confirmation. Removals open a review case; a moderator can reverse any of them.
Inactive members
Find the members who quietly stopped taking part.
Warn them on a schedule, then remove them into a queue where somebody decides. Nothing here is about behaviour, only about how long since the member last took part.
- day 60Early notice
- day 75Inactive warning
- day 85Final reminder
- day 90Removed, sent to review
Group admins are never removed for inactivity. Members who joined in the last 7 days are not counted.
That schedule is the default. Periods from a week to a year are supported, subject to a platform maximum, and any warning in the sequence can be switched off.
Being straight with you
WhatsApp limits what any tool can do. We publish the list.
Sedge connects to WhatsApp two ways, and neither is unlimited. What each one can and cannot do is on the integrations page, so you see it before you buy, not after.
- The official Cloud API caps a group at 8 participants and only works in groups the business itself created. It cannot delete a message or change an admin role.
- The linked-device adapter works in real groups with full admin capability, and it is not an official Meta integration. The number you link may be restricted by WhatsApp. You acknowledge that before connecting.
- There is no atomic “move member”. A move is a removal plus an invitation, and if the member’s privacy settings block being added, the case says “invitation sent, waiting for them to accept” rather than claiming success.
Pricing
Priced by accounts, groups and how long history is kept.
Every plan includes monitor mode, review queues and the full explanation behind each action. Those are not upsells.
Paying yearly saves up to 17%.
Starter
Most commonUS$29per month
14-day trial, once per organisation.
For a single community getting its first spam protection in place.
Pro
US$79per month
For active communities that need inactivity management and review workflows.
Business
US$249per month
For organizations running many groups across several WhatsApp accounts.
Enterprise
Let’s talk
Custom limits, long retention and single sign-on.
Questions
The things people ask first.
- Does it use AI?
- No. Sedge applies rules a person configured (thresholds, weights, rolling windows and word lists) and shows the arithmetic behind every decision. Where a signal is statistical, such as the posting-pattern rule, the confidence and the sample size are shown alongside it and it never acts alone.
- Will it remove someone the moment I connect a group?
- No. A newly protected group starts in monitor mode. Rules run and events are recorded with the action they would have taken, but nothing is removed and no message is deleted until you switch that group to enforce, which takes an explicit confirmation.
- Can a decision be undone?
- Yes. A removal opens a review case, and a moderator can restore the member, keep the removal, whitelist them, ban them, or ask for more information. An event can also be overridden directly, with a reason, which reverses the action and revokes any strike it added.
- Does Sedge store our conversations?
- No. Message bodies pass through the analysis queue and are not written to the database. What is stored is counters, content hashes, and a bounded excerpt, only when a rule actually fires, and only for as long as your retention setting allows.
Quiet work on busy groups.
Connect an account, protect a group, and watch a week of monitor mode before anything changes.