# When Everyone Needs to Confirm the Ping

> Keep one important update open until every original recipient confirms it. PingRoom’s new confirmation modes make the rule explicit for CLI, SDK, MCP, OpenClaw, and webhook sends.

- Published: 2026-09-10
- Author: PingRoom
- Category: Product
- Topics: group notification confirmation, everyone acknowledgement, PingRoom confirmation mode, acknowledged push notification
- Canonical: https://pingroom.io/blog/everyone-confirms-one-ping
- Cover image: https://pingroom.io/blog/everyone-confirms-one-ping.webp
- Cover description: Pingo the Pigeon waits beside a venue side entrance as three gray clay pigeons arrive through the open door.

For this example, the main entrance has closed early. Three shift leads are already on their way, and each one needs to know that tonight’s handoff is happening at the side door.

A confirmation from one person does not settle that update. You need all three.

PingRoom now lets a builder choose the rule for a confirmation-required Ping: close it after **any** eligible recipient confirms, or keep it open until **all** original eligible recipients have confirmed.

That turns one shared update into a visible roll call without sending “Did you see this?” three times.

## Choose the rule before you send

The two modes answer different questions.

| Mode    | The Ping closes when                       | Use it for                                       |
| ------- | ------------------------------------------ | ------------------------------------------------ |
| **Any** | The first eligible recipient confirms      | One person needs to take ownership               |
| **All** | Every original eligible recipient confirms | Each person needs to acknowledge the same update |

**Any** remains the default. It fits a request such as “Who can unlock the hall?” because one person taking the job is enough.

Use **All** for an update such as “Tonight, enter through the side door.” Nobody is volunteering to own the information. Every person in the small Room needs to confirm they received it.

Urgency is a separate choice. It controls how the Ping asks to arrive; confirmation controls the response rule. Our guide to [urgent delivery and confirmation](/blog/urgent-is-not-confirmation) explains that distinction.

## Put only the relevant people in the Room

Everyone mode uses the eligible recipients at the moment the Ping is sent. People who join the Room later are not added to that confirmation count.

For the entrance change, use a private Room containing the three shift leads who need the update. Do not send it to a broad volunteer Room and treat silence from an off-duty member as a failed handoff.

The Room defines the audience. The confirmation mode defines what completion means for that audience.

## Send one all-recipient confirmation

With PingRoom CLI 0.11.0, an incoming webhook can send the update like this:

```bash
pingroom ping -w "$PINGROOM_WEBHOOK_URL" \
  -m "Tonight: use the side entrance for the 18:00 handoff" \
  --require-ack --ack-mode all --ack-timeout 600
```

The same rule is available as `ack_mode: "all"` with `requires_ack: true` through the SDK, MCP, and regular incoming webhooks. OpenClaw 0.2.0 uses `requireAck: true` with `ackMode: "all"`.

The ten-minute timeout in this example is a boundary, not proof that someone confirmed. Pick a duration that leaves time for a direct follow-up before the handoff.

## Read progress without guessing

For everyone mode, PingRoom reports the confirmation rule, the confirmed count, and the required count. A partial result stays open: **2 of 3 confirmed** is progress, not completion.

Through MCP, `get_notification` and `wait_for_ack` return those counts without exposing recipient IDs. Only an `acked` status proves the rule was met. A wait call ending because its timeout elapsed does not.

![Pingo the Pigeon inspects three unmarked wooden tokens in a shallow tray while three gray clay pigeons walk into the venue.](/blog/everyone-confirms-one-ping-1.webp)

[Pingo the Pigeon](/Pingo), our fictional Chief Marketing Officer, has placed three blank wooden tokens by the door. He is not leaving until all three have moved into the tray. The human team chose the rule; Pingo is providing the stare.

If one person has not confirmed, check the real situation. Their phone may be away, their plans may have changed, or they may no longer be part of the handoff. PingRoom records the response it receives. It does not turn silence into consent.

## Use everyone mode for shared acknowledgement

Everyone mode is useful when each member of a small, known group must acknowledge the same fact:

- a venue entrance or meeting point changed;
- a short operating note applies to every person on the current shift;
- each member of a trip group needs to confirm a revised departure time;
- every on-call responder needs to acknowledge a planned handover.

It is not a poll, attendance system, or substitute for an emergency procedure. If the group needs to choose among options, use a Question. If one person needs to accept a job, use any-mode confirmation or a Question whose first answer closes the request.

## Where the new mode is available

Everyone confirmation is live through PingRoom’s API, MCP tools, and regular incoming webhooks. It is published in [PingRoom CLI 0.11.0](https://www.npmjs.com/package/@pingroom/cli), SDK 0.5.0, and OpenClaw 0.2.0. The [MCP connection guide](/connect-mcp.md) documents the send and progress fields.

The public PingRoom mobile release already supports confirmation-required Pings. The new native sender selector and detailed everyone-progress controls are not in the current App Store or Google Play builds. For now, choose the all-recipient rule from one of the builder surfaces above; available notification actions still vary by device.

For the side-door update, the useful finish is simple: three required recipients, three confirmations, one handoff that no longer depends on guessing.