Ask a person to approve or acknowledge and wait for the answer
One company's docs show a full fit.
What counts as done
The push carries approve and reject actions or an acknowledgement, and the agent reads the answer back by receipt, callback or reply topic without the person opening a terminal; an unanswered emergency message repeats until acknowledged or expired.
Measured, for our own tests: answer readable by the agent within 10 seconds of the tap. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: ask me before you run that
, page me until I acknowledge
, get my OK on my phone
, wait for my approval
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Pushover C Pushover, LLC | Priority 2 repeats every retry seconds (at least 30) until acknowledged or expire (3 hours max, 50 retries); the receipt gives acknowledged, acknowledged_at and acknowledged_by, polled every 5 seconds or pushed to a callback URL. acc-08 built Approve and Reject on it. source |
Does the job, with a limit 1
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
Doesn't do this job 10
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Amazon SNS BB Amazon Web Services, Inc. | Publish is one-way; no action buttons or acknowledgement receipt come back to the publisher. source |
| Courier B trycourier.com, Inc. | No documented push action that returns a person's answer to the sender or repeats until acknowledged. source |
| Expo Push Notifications B 650 Industries, Inc. | Tickets and receipts report hand-off to APNs or FCM only; nothing returns a person's tap to the sender or repeats until acknowledged. source |
| Firebase Cloud Messaging BB Google LLC | FCM sends downstream only; any action button and reply path must be built into your app. source |
| Knock A Knock Labs, Inc. | No documented action-button answer path or acknowledgement receipt that returns a person's tap to the trigger caller. source |
| MagicBell C MagicBell, Inc. | No action-reply or acknowledgement receipt in the OpenAPI; in-app read and seen state is the only feedback. source |
| Novu B Noti-Fire Apps Ltd. | In-app Inbox actions and agent tool approvals exist, but nothing documented returns a tap on a phone push to the triggering agent or repeats until acknowledged. source |
| OneSignal BB OneSignal, Inc. | Up to 3 action buttons are shown on mobile push, but the answer is a click event in your app, not a receipt or callback the sender reads, and nothing repeats until acknowledged. source |
| Pingram C Pingram | No push channel left, so no push actions; inbound SMS replies arrive by webhook, which is a different flow. source |
| SuprSend BB SuprStack Inc | Push templates carry buttons and action URLs, but nothing documented returns the tap to the triggering agent or repeats until acknowledged. source |
What stops agents finishing
- no way to read the tap back, only to send
- approval spoofable on an unauthenticated topic
Around it
Before: notifications.alert-operator, agent-harnesses.permission-request. After: human-in-the-loop.record-decision.
Where this comes from
Weight 11 of 100 in Notifications: 3 accounts build approval on push (acc-01, acc-08, acc-09); weighted above its count because each was a tool built to fill the gap
The same as data: /api/v1/use-cases/notifications.ask-approval.json, or the MCP tool get_use_case with id notifications.ask-approval. Other jobs in this category: /api/v1/niches?category=notifications.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.