Approving Every WhatsApp Join by Hand: The Hours It Really Costs

The Switch That Turns Members Into Tickets

WhatsApp gives group admins one setting against unwanted joins: Approve new members, under Group info → Group permissions. It is off by default. Switch it on and everyone who opens your invite link lands in a Pending requests list instead of the group, and stays there until an admin approves or rejects them. It applies to invite-link joins too, which is the whole point.

It is the most common advice for groups that have been hit by bots, and it works in the narrow sense that nothing gets in without a person saying yes.

The catch is that the person is you.

---

What One Approval Actually Involves

On paper it is a single tap. In practice it looks like this:

1. A banner appears in the group, or you notice the pending count
2. Open Group info, then Pending requests
3. Look at what you have: a display name, a profile photo if there is one, a phone number
4. If you are unsure, open the contact or message the person to ask who they are
5. Approve or reject
6. Repeat, in every group that has the setting on, because each group keeps its own queue

Step 3 is the uncomfortable one. A name, a photo and a number tell you almost nothing. A bot account with a stock photo and a plausible name looks like a newcomer. A real newcomer who never set a profile picture looks like a bot. The decision is mostly a guess, made in a spare minute, usually by a volunteer.

---

The Arithmetic Nobody Does

Here is the queue in hours. The per-request time is an assumption, so pick your own: an obvious request takes about 30 seconds, one where you check the profile or message the person takes two minutes or more. At an average of one minute per request:

Join requests per day	Per month	Per year
3	~1.5 hours	~18 hours
8	~4 hours	~49 hours
20	~10 hours	~122 hours

At eight requests a day, which is roughly where a busy local community sits (see the case study below), that is more than a working week a year spent tapping approve.

And the minutes are the cheap part.

Interruptions. Requests do not arrive in a batch at 9am. They arrive at 23:40 and on Sunday morning, one at a time, and each one is a context switch.

Waiting newcomers. Someone asks to join the hiking group on Friday night for Saturday's hike. The approval lands Saturday at noon. They missed it, and the cost of the queue fell on exactly the kind of person the community exists for.

Whoever is online. Approvals move at the speed of the admin who happens to be awake. When the main organizer goes on holiday, the queue becomes a backlog.

It multiplies with groups. A community with one group has one queue. A community with twenty activity groups has twenty, and nobody watches all twenty equally.

---

Manual Approval vs Filtering at the Link

The alternative is to move the check from the group to the link: share a protected link instead of the raw invite, and let it decide who receives the invite at all.

	Manual approval in WhatsApp	Gated invite link
Who does the work	An admin, for every request	The server, on every click
When	Whenever an admin gets to it	Instantly, at the click
What it checks	A name, a photo, a number, and a hunch	Human verification, plus a country rule, time window, visit cap or password if you set them
The real newcomer waits	Minutes to a day	A few seconds
Bots	Reach the queue; an admin has to spot them	Stopped before they ever see the invite
Cost grows with	Every request, in every group	Nothing: set once per link

These are not mutually exclusive, and that matters.

---

What the Gate Does Not Replace

A captcha proves the visitor is a person. It does not prove they are the right person.

Some groups need judgement about membership itself: a women-only group, a housing group where scammers post fake listings, a group for paying members. For those, keep approval on as well. The gate then removes the automated noise from the queue, so what is left is a short list of real people who are worth a proper look.

For everything else, the hobby groups, the event chats, the sports groups, approval was mostly a bot filter run by hand. That job can move to the link.

---

Case Study: Zurich Together

Zurich Together is a social community in Zurich, founded in 2017. By its own count it has more than 50,000 members across its social channels and runs 10 to 14 events a week. Much of the day-to-day life happens in WhatsApp groups organized by activity: racket sports, via ferrata, board games, comedy, foodies, housing, buy and sell, and more.

Before, every join request in those groups waited for an organizer to approve it by hand.

Since February 2026 the community's bio page has run on ShieldmyLinks:

• 28 links, of which 22 are WhatsApp group invites
• Every WhatsApp invite sits behind reCAPTCHA v2
• 21 of the 22 also carry a country allow-list: Switzerland and its four neighbours (Austria, France, Germany, Italy)

Now the filtering happens before a join request exists. A visitor who is not a person, or not in the region, never receives the invite, so there is nothing for an organizer to review.

The numbers

From the Zurich Together dashboard, as of October 18, 2026:

Metric	Value
Visitors verified and handed a WhatsApp invite	1,016
Attempts on the WhatsApp links that were blocked	102
Verified invite clicks in July and in August	~250 a month, about 8 a day
Share of logged invite clicks coming from Switzerland	78%
Views of the bio page itself	1,396

What that means in time

We have not timed Zurich Together's organizers, so treat this as an estimate built on the assumptions above. 1,016 invite handouts at 30 seconds to 2 minutes each is between 8.5 and 34 hours of approving. At one minute each, about 17 hours, spread across 22 separate queues and every hour of the day.

Two corrections pull in opposite directions. Not every verified click becomes a join (some people are already members, some change their mind), so 1,016 is an upper bound on requests. On the other hand, the estimate leaves out the interruptions, the waiting newcomers, and the 102 blocked attempts that an organizer would otherwise have had to recognise and reject one by one.

The summer rate, about eight a day, is the middle row of the table above. That is what a busy local community looks like, and it is why the queue never quite clears.

---

The One Rule That Makes It Work

A gate only filters the people who go through it.

If the raw invite is still published somewhere else, an old bio page, a forum post, a PDF from last year, bots walk around the gate and you are back to a queue, or worse, to no queue at all. Before you rely on the gate, and certainly before you switch approval off:

1. Reset each group's invite link. In WhatsApp, a reset link cannot be restored, so every copy of the old one dies at once.
2. Set "Invite via link" so only admins can create links. Otherwise any member can mint a fresh raw invite and post it.
3. Protect the new invite and publish only the protected link. Never paste the raw one anywhere public again.

Skip step 1 and you have built a front door next to an open wall.

---

Setting It Up

1. In each group, reset the invite link and restrict link creation to admins
2. Create one protected link per group, not one for the whole community, so the dashboard shows which groups attract blocked attempts
3. Add a country rule if your community is local, and a visit cap or end date for groups with a fixed size or season
4. Put the links on a bio page, so members have a single address to remember
5. Decide group by group: keep approval where membership needs judgement, switch it off where it was only ever a bot filter

Approval queues are a tool for judgement. Most of what passes through them needs none.