{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/messaging.ask-and-wait/",
    "json": "https://www.anchorterminal.com/niches/messaging.ask-and-wait/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/messaging.ask-and-wait/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/messaging.ask-and-wait/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 20 | 48 | 3 | 2 |\n\n## What counts as done\n\nThe reply from that recipient in that thread is matched to the paused step and resumes it, or a timeout fires at a set time.\n\nMeasured, for our own tests: the step resumes within 10 seconds of the reply arriving.\n\nHow agents ask for it: text me to approve this before you continue; ask the customer for their address and wait; check with me before running tonight\n\n## Does the job, with a limit\n\nIt 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.\n\n- **360dialog WhatsApp API + MCP (360dialog GmbH)**: Replies arrive in the same wa_id thread by webhook or the Inbox API's message list, so a workflow can match them, but there is no pause, resume or timeout primitive.\n- **AWS End User Messaging (Amazon Web Services, Inc.)**: Inbound replies land on SNS with origination and destination numbers, so an SQS consumer can match by number and resume; no thread id or wait primitive.\n- **Bandwidth Messaging API + MCP (Bandwidth Inc.)**: Replies arrive by callback or listMessages with source and destination numbers, so a workflow can match by number; no thread or wait primitive.\n- **Bird API + MCP (Bird B.V.)**: Inbound events arrive signed with a stable id and can be replayed, so a reply can be matched by sender; no wait or correlation primitive.\n- **ClickSend SMS API + MCP (ClickSend Pty Ltd)**: Inbound can be polled or pushed, and replies carry the original message id (GET /v3/sms/inbound/{original_message_id}), so a reply can be tied to the question; no wait primitive.\n- **Infobip API + MCP (Infobip Ltd)**: Replies can be pushed or pulled and callbackData rides on sends, but no reply-to-question correlation or wait primitive.\n- **Kudosity (Known Pty Ltd)**: RCS suggested replies carry postback_data tied to a message_ref, which can match an answer to its question; SMS replies match by number only. No wait primitive.\n- **Linq (Linq App Inc.)**: Replies arrive in the same chat id by signed webhook, so a workflow can match them, but no wait or timeout primitive.\n- **Photon (Something Great Inc.)**: Replies arrive in the same chat on the stream with a checkpoint, so a workflow can match them; no wait or timeout primitive.\n- **Plivo API (Plivo Inc.)**: Replies arrive at the message URL or the inbound list with from and to numbers, so a workflow can match by number; no wait primitive.\n- **Prelude (DING SAS)**: Inbound webhooks carry the sender and a message id, and replies thread as WhatsApp quoted messages, so a workflow can match them; no wait primitive.\n- **Sendblue (Round One, Inc.)**: Replies come to the receive webhook with from_number and can be listed by number, so a workflow can match them; no wait primitive.\n- **Sinch Messaging APIs + MCP (Sinch AB (publ))**: Replies arrive in the same conversation_id with correlation_id and message metadata, so a workflow can match them; no wait primitive.\n- **Telegram Bot API (Telegram Messenger Inc.)**: ForceReply makes the user reply to the bot's question and reply_to_message ties the answer to it, with long polling needing no public URL. No timing figure against the 10-second bar.\n- **Telnyx API + MCP (Telnyx LLC)**: Inbound webhooks carry from and to numbers, so a workflow can match by number; a public URL is needed and there is no wait primitive.\n- **Twilio API + MCP (Twilio Inc.)**: Replies come by webhook or the Messages list by number; acc-29 notes there is no wait-for-reply primitive like Telegram's, so correlation is the workflow's job.\n- **Vonage Messages API + MCP (Vonage Holdings Corp.)**: Replies arrive by signed inbound webhook with the sender, so a workflow can match by number; a public URL is needed and there is no wait primitive.\n- **Wati (Clare.AI Limited)**: Replies come by webhook or the conversation's messages list, so a workflow can match them to the thread; no wait primitive.\n- **WhatsApp Business Platform (Cloud API) (Meta Platforms, Inc.)**: Replies arrive by webhook from the same wa_id, so a workflow can match them by contact; a public HTTPS URL is needed and there is no wait primitive.\n- **YCloud (YCloud International Pte. Ltd.)**: Replies arrive by signed webhook from the same contact, so a workflow can match them; a public URL is needed and there is no wait primitive.\n\n## What stops agents finishing\n\n- no way to correlate a reply with the question that asked it\n- SMS reply webhooks need a public URL the agent may not have\n\n## Around it\n\nAfter: human-in-the-loop.approval.\n\n## Where this comes from\n\nWeight 3 of 100 in Messaging APIs: 2 of 69 accounts; thin, kept because human-in-the-loop by text recurs in Telegram bot tools\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/messaging.ask-and-wait.json, or the MCP tool get_use_case with id messaging.ask-and-wait. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Ask a person a question by message and wait for the answer",
        "url": ""
      }
    ],
    "description": "Ask a person a question by message and wait for the answer: 0 companies fully do it, 20 with a limit, 48 carry the tag. Every listing in Messaging APIs with the reason and a source.",
    "facts": null,
    "h1": "Ask a person a question by message and wait for the answer",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/messaging.ask-and-wait/",
    "published": "",
    "section": "agents",
    "title": "Ask a person a question by message and wait for the answer | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/messaging.ask-and-wait/"
  },
  "tokens": {
    "markdown": 1450,
    "slim": 380
  },
  "version": 1
}
