Niches · Messaging APIs

Ask a person a question by message and wait for the answer

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

0companies, full fit
20companies, fit with a limit
48companies carry the tag
3share of the category's work
2first-hand accounts

What counts as done

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, for our own tests: the step resumes within 10 seconds of the reply arriving. No docs we read state these figures, so they don't count against a listing here.

How 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

Does the job, with a limit 20

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.

ListingWhy
360dialog WhatsApp API + MCP D
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. source
AWS End User Messaging BB
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. source
Bandwidth Messaging API + MCP BB
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. source
Bird API + MCP A
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. source
ClickSend SMS API + MCP D
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. source
Infobip API + MCP BB
Infobip Ltd
Replies can be pushed or pulled and callbackData rides on sends, but no reply-to-question correlation or wait primitive. source
Kudosity B
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. source
Linq BB
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. source
Photon C
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. source
Plivo API B
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. source
Prelude B
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. source
Sendblue B
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. source
Sinch Messaging APIs + MCP B
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. source
Telegram Bot API D
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. source
Telnyx API + MCP BB
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. source
Twilio API + MCP A
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. source
Vonage Messages API + MCP B
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. source
Wati D
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. source
WhatsApp Business Platform (Cloud API) B
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. source
YCloud B
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. source

What stops agents finishing

  • no way to correlate a reply with the question that asked it
  • SMS reply webhooks need a public URL the agent may not have

Around it

After: human-in-the-loop.approval.

Where this comes from

Weight 3 of 100 in Messaging APIs: 2 of 69 accounts; thin, kept because human-in-the-loop by text recurs in Telegram bot tools

The same as data: /api/v1/use-cases/messaging.ask-and-wait.json, or the MCP tool get_use_case with id messaging.ask-and-wait. Other jobs in this category: /api/v1/niches?category=messaging.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

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.