# Reach the person wherever they are and get the answer in time

> Reach the person wherever they are and get the answer in time: 0 companies fully do it, 5 with a limit, 16 carry the tag. Every listing in Human approval & handoff with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/human-in-the-loop.reach-approver/
- Markdown: https://www.anchorterminal.com/niches/human-in-the-loop.reach-approver/index.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/niches/human-in-the-loop.reach-approver/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/human-in-the-loop.reach-approver/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 5 | 16 | 19 | 7 |

## What counts as done

The request arrives on at least one of the person's channels, carries enough of the payload to decide or a link to it, can be answered from that channel, and a delivery failure is reported to the agent.

Measured, for our own tests: it arrives within 30 seconds.

How agents ask for it: ping me on my phone when the agent needs me; send the approval to Slack; notify me on Telegram

## Does the job, with a limit

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.

- **gotoHuman (gotoHuman UG (haftungsbeschränkt))**: Web inbox, email and a Slack channel post per request, each with a link; external reviewers get a unique link with no account. Answers are given on the review page, not in Slack, and no notification latency or delivery-failure report is documented.
- **Orkes Conductor Human tasks (Orkes, Inc.)**: Assignees can be Conductor or external users and groups, but there is no built-in Slack or email prompt: a trigger policy (PENDING, ASSIGNED) starts a second workflow that notifies. Answers go through the UI or API, and no delivery latency or failure report is documented.
- **Permit MCP Gateway (Permit Inc.)**: Email and Slack incoming-webhook notifications carry context and a dashboard link (Slack omits tool arguments); decisions are made only in the admin dashboard, approvers must be gateway admins, and no delivery failure is reported to the agent.
- **Pushary (RalphNex OÜ)**: Phone push with lock-screen approve or deny, Mac notch, Slack buttons and modals, and a browser page, each answerable in place; noDevices and sent: 0 tell the agent nothing was reached. The body is cut at 180 characters and no delivery time is stated beyond 'instantly'.
- **withHuman (Metoro Inc)**: Email, SMS, WhatsApp, Slack, Discord, phone app and Mac app per reviewer rules, with immediate phone pushes. Slack messages omit arguments and cannot decide (only the apps can), and a failed channel falls back to email without telling the agent; no delivery time is stated.

- not this job: Big Arrow (Franz Enzenhofer (individual, Vienna)): Answers come only from the local Mac screen (an arrow or floating card, optionally spoken). No chat, email or phone channel, which is the map's named blocker for this listing.
- not this job: Hatchet (Hatchet Technologies, Inc.): No approver inbox, chat, email or phone channel; answers arrive only as events pushed by SDK or incoming webhook.
- not this job: Inngest (Inngest Inc): No reviewer inbox, Slack app or email; the guide's Slack message is the builder's own sendSlackMessage code.
- not this job: Restate (Restate GmbH): No inbox, Slack app or email; the guide says the agent sends the callback ID to Slack, email or a dashboard itself.
- not this job: Temporal (Temporal Technologies Inc.): No inbox, notifications or routing; the page says the pattern needs a separate approval interface that sends the Signal.
- not this job: Trigger.dev (API Hero Ltd): No reviewer UI, notifications or routing; the builder sends the token or its public access token to their own app.

## What stops agents finishing

- no chat, email or phone channel (durable-execution listings, bigarrow)
- message over the channel's size limit dropped silently
- approver must be a product user or admin seat

## Around it

Before: human-in-the-loop.approve-action. After: notifications.push.

## Where this comes from

Weight 19 of 100 in Human approval & handoff: 7 of 26 accounts (approve from phone, Slack and Discord routing, Telegram, missed prompts, length limits)

As data: https://www.anchorterminal.com/api/v1/use-cases/human-in-the-loop.reach-approver.json, or the MCP tool get_use_case with id human-in-the-loop.reach-approver. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
