{
  "listings": [
    {
      "slug": "360dialog",
      "name": "360dialog WhatsApp API + MCP",
      "company": "360dialog GmbH",
      "grade": "D",
      "fit": "caveat",
      "why": "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.",
      "source": "https://docs.360dialog.com/docs/inbox/inbox-api/api-ref/messages.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/360dialog"
    },
    {
      "slug": "aws-end-user-messaging",
      "name": "AWS End User Messaging",
      "company": "Amazon Web Services, Inc.",
      "grade": "BB",
      "fit": "caveat",
      "why": "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.",
      "source": "https://docs.aws.amazon.com/sms-voice/latest/userguide/llms.txt",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/aws-end-user-messaging"
    },
    {
      "slug": "bandwidth",
      "name": "Bandwidth Messaging API + MCP",
      "company": "Bandwidth Inc.",
      "grade": "BB",
      "fit": "caveat",
      "why": "Replies arrive by callback or listMessages with source and destination numbers, so a workflow can match by number; no thread or wait primitive.",
      "source": "https://dev.bandwidth.com/spec/messaging.yml",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/bandwidth"
    },
    {
      "slug": "bird",
      "name": "Bird API + MCP",
      "company": "Bird B.V.",
      "grade": "A",
      "fit": "caveat",
      "why": "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.",
      "source": "https://bird.com/docs/guides/webhooks.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/bird"
    },
    {
      "slug": "clicksend",
      "name": "ClickSend SMS API + MCP",
      "company": "ClickSend Pty Ltd",
      "grade": "D",
      "fit": "caveat",
      "why": "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.",
      "source": "https://github.com/ClickSend/clicksend-python-v2/blob/HEAD/docs/SmsApi.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/clicksend"
    },
    {
      "slug": "infobip",
      "name": "Infobip API + MCP",
      "company": "Infobip Ltd",
      "grade": "BB",
      "fit": "caveat",
      "why": "Replies can be pushed or pulled and callbackData rides on sends, but no reply-to-question correlation or wait primitive.",
      "source": "https://www.infobip.com/docs/api/platform/messages-api",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/infobip"
    },
    {
      "slug": "kudosity",
      "name": "Kudosity",
      "company": "Known Pty Ltd",
      "grade": "B",
      "fit": "caveat",
      "why": "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.",
      "source": "https://developers.kudosity.com/openapi/public-openapi.yaml",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/kudosity"
    },
    {
      "slug": "linq",
      "name": "Linq",
      "company": "Linq App Inc.",
      "grade": "BB",
      "fit": "caveat",
      "why": "Replies arrive in the same chat id by signed webhook, so a workflow can match them, but no wait or timeout primitive.",
      "source": "https://docs.linqapp.com/channel/imessage/guides/webhooks/index.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/linq"
    },
    {
      "slug": "photon",
      "name": "Photon",
      "company": "Something Great Inc.",
      "grade": "C",
      "fit": "caveat",
      "why": "Replies arrive in the same chat on the stream with a checkpoint, so a workflow can match them; no wait or timeout primitive.",
      "source": "https://photon.codes/docs/advanced-kits/imessage/events.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/photon"
    },
    {
      "slug": "plivo",
      "name": "Plivo API",
      "company": "Plivo Inc.",
      "grade": "B",
      "fit": "caveat",
      "why": "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.",
      "source": "https://plivo.com/docs/messaging/api/messages.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/plivo"
    },
    {
      "slug": "prelude",
      "name": "Prelude",
      "company": "DING SAS",
      "grade": "B",
      "fit": "caveat",
      "why": "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.",
      "source": "https://docs.prelude.so/notify/v2/documentation/whatsapp.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/prelude"
    },
    {
      "slug": "sendblue",
      "name": "Sendblue",
      "company": "Round One, Inc.",
      "grade": "B",
      "fit": "caveat",
      "why": "Replies come to the receive webhook with from_number and can be listed by number, so a workflow can match them; no wait primitive.",
      "source": "https://docs.sendblue.com/llms.txt",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/sendblue"
    },
    {
      "slug": "sinch",
      "name": "Sinch Messaging APIs + MCP",
      "company": "Sinch AB (publ)",
      "grade": "B",
      "fit": "caveat",
      "why": "Replies arrive in the same conversation_id with correlation_id and message metadata, so a workflow can match them; no wait primitive.",
      "source": "https://developers.sinch.com/_bundle/docs/conversation/api-reference/conversation.yaml",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/sinch"
    },
    {
      "slug": "telegram-bot",
      "name": "Telegram Bot API",
      "company": "Telegram Messenger Inc.",
      "grade": "D",
      "fit": "caveat",
      "why": "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.",
      "source": "https://core.telegram.org/bots/api/types/forcereply.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/telegram-bot"
    },
    {
      "slug": "telnyx",
      "name": "Telnyx API + MCP",
      "company": "Telnyx LLC",
      "grade": "BB",
      "fit": "caveat",
      "why": "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.",
      "source": "https://developers.telnyx.com/docs/messaging/messages/receiving-webhooks.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/telnyx"
    },
    {
      "slug": "twilio",
      "name": "Twilio API + MCP",
      "company": "Twilio Inc.",
      "grade": "A",
      "fit": "caveat",
      "why": "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.",
      "source": "https://community.n8n.io/t/267989",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/twilio"
    },
    {
      "slug": "vonage",
      "name": "Vonage Messages API + MCP",
      "company": "Vonage Holdings Corp.",
      "grade": "B",
      "fit": "caveat",
      "why": "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.",
      "source": "https://developer.vonage.com/llms.txt",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/vonage"
    },
    {
      "slug": "wati",
      "name": "Wati",
      "company": "Clare.AI Limited",
      "grade": "D",
      "fit": "caveat",
      "why": "Replies come by webhook or the conversation's messages list, so a workflow can match them to the thread; no wait primitive.",
      "source": "https://docs.wati.io/llms.txt",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/wati"
    },
    {
      "slug": "whatsapp-cloud-api",
      "name": "WhatsApp Business Platform (Cloud API)",
      "company": "Meta Platforms, Inc.",
      "grade": "B",
      "fit": "caveat",
      "why": "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.",
      "source": "https://developers.facebook.com/documentation/business-messaging/whatsapp/webhooks/overview.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/whatsapp-cloud-api"
    },
    {
      "slug": "ycloud",
      "name": "YCloud",
      "company": "YCloud International Pte. Ltd.",
      "grade": "B",
      "fit": "caveat",
      "why": "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.",
      "source": "https://docs.ycloud.com/en/api-reference/guides/api-fundamentals/configure-webhooks.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/ycloud"
    }
  ],
  "marks": "yes: the docs show it does the job as the success test says. caveat: it does the job with a limit an agent should know. no: it doesn't do this job. unchecked: we couldn't read it.",
  "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"
  },
  "useCase": {
    "accounts": 2,
    "after": [
      "human-in-the-loop.approval"
    ],
    "area": "communication",
    "asks": [
      "text me to approve this before you continue",
      "ask the customer for their address and wait",
      "check with me before running tonight"
    ],
    "before": [],
    "blockers": [
      "no way to correlate a reply with the question that asked it",
      "SMS reply webhooks need a public URL the agent may not have"
    ],
    "capabilities": [
      "messaging.inbound",
      "messaging.sms"
    ],
    "category": "messaging",
    "categoryName": "Messaging APIs",
    "checked": "2026-11-15",
    "companies": {
      "fit": 0,
      "fitWithLimit": 20,
      "tagged": 48
    },
    "competition": "none",
    "fits": null,
    "fitsWithLimit": [
      "360dialog",
      "aws-end-user-messaging",
      "bandwidth",
      "bird",
      "clicksend",
      "infobip",
      "kudosity",
      "linq",
      "photon",
      "plivo",
      "prelude",
      "sendblue",
      "sinch",
      "telegram-bot",
      "telnyx",
      "twilio",
      "vonage",
      "wati",
      "whatsapp-cloud-api",
      "ycloud"
    ],
    "id": "messaging.ask-and-wait",
    "listings": {
      "caveat": 20,
      "no": 0,
      "notRead": 0,
      "tagged": 49,
      "unchecked": 0,
      "yes": 0
    },
    "name": "Ask a person a question by message and wait for the answer",
    "status": "draft",
    "success": "The reply from that recipient in that thread is matched to the paused step and resumes it, or a timeout fires at a set time. Measured: the step resumes within 10 seconds of the reply arriving.",
    "url": "https://www.anchorterminal.com/api/v1/use-cases/messaging.ask-and-wait.json",
    "weight": 3,
    "weightBasis": "2 of 69 accounts; thin, kept because human-in-the-loop by text recurs in Telegram bot tools"
  }
}
