Review and quarantine
Every removal, explained.
A removal is not the end of a decision, it is the start of one. Every automated removal opens a case with the full evidence, and a person decides what happens next.
On every case
The reviewer sees exactly what the engine saw.
Score, threshold, every contributing rule, the numbers behind each one, and whether the action was carried out or simulated.
Message excerpts are attached where your retention settings allow. If a rule fired on something that has since been purged, the case says so rather than showing a gap.
| Rule | Running total | Contribution |
|---|---|---|
Repeated content The same message had already been posted twice in the last hour.
| 30 | +30 |
Repeated links The same link appeared in each copy.
| 60 | +30 |
Group invite spam An invite link to another WhatsApp group, posted by a member who is not an admin.
| 95 | +35 |
Message flooding Six messages inside the five-second window.
| 115 | +20 |
Previous warning Warned nine days ago; the weight has decayed from 30.
| 135 | +20 |
| Total | threshold 100 | 135 |
The score reached 135 against a threshold of 100. The group is in monitor mode, so the member was removed only on paper. Nothing changed in WhatsApp.
Two queues
Because they are two different jobs.
A spam case asks “was this fair?”. An inactivity case asks “should this person still be here?”. Putting both in one table with a filter would make a reviewer work out which question they are answering.
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
Quarantine
What “moved to a review group” really means.
Nothing here is hidden behind a friendly word. WhatsApp has no atomic move, so Sedge reports each step of the attempt as it goes.
placement
Added
The member was removed from the source group and added to the review group. Both steps succeeded.
placement
Invitation sent
Their privacy settings do not allow being added, so an invitation was sent. Waiting for them to accept.
placement
Failed
The placement could not be completed. The reason is on the case, and the case stays open.
placement
Not attempted
No review group is configured for this queue, so the case lives only in Sedge.
A review group is optional
Decisions
What a moderator can do, and what each one changes.
- Restore member
- Sedge adds the member back to the group they were removed from, or invites them if their privacy settings block a direct add.
- Keep removed
- The removal stands. The member can be restored later from the audit trail.
- Ban member
- The strongest outcome. Use it for repeat, deliberate abuse.
- Whitelist member
- Trust offsets future signals for this member by the whitelist rule weight.
- Dismiss
- Closed with no change to the member.
- Request information
- The member is asked (your note is the question), and the case stays open for their reply.
- Change classification
- Closes the case, noting for the record that the engine had the reason wrong.
Every decision is written to the audit trail with the reviewer, the time, the note they left and the case it belonged to. An appeal raised later reopens the same evidence rather than starting from nothing.
Nobody is removed without a case.
And no case is closed without a reason attached to it.