{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/messaging.two-way-customer-agent/",
    "json": "https://www.anchorterminal.com/niches/messaging.two-way-customer-agent/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/messaging.two-way-customer-agent/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/messaging.two-way-customer-agent/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 | 52 | 16 | 16 |\n\n## What counts as done\n\nEvery inbound message produces precisely one reply in the same thread, no reply is sent twice for one inbound event, and a handoff flag stops agent replies until a person releases the thread.\n\nMeasured, for our own tests: each reply arrives within 60 seconds of the inbound message.\n\nHow agents ask for it: have the agent answer our WhatsApp; reply to texts from customers; build an SMS chatbot for bookings; hand the chat to a human when it can't answer\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)**: Inbound and status webhooks share one URL, Meta retries failures for 7 days, and the Inbox (Premium plan) assigns chats to people. Webhooks carry Basic auth only, and acc-26 saw status events re-fire the flow and 200 replies that never arrived.\n- **AWS End User Messaging (Amazon Web Services, Inc.)**: Two-way SMS and RCS deliver inbound to an SNS topic, which an SQS queue or Lambda can hold and retry, but there is no handoff flag, and send actions default to 1 request a second per account and Region.\n- **Bandwidth Messaging API + MCP (Bandwidth Inc.)**: Inbound and delivery callbacks are retried for 24 hours with a 10-second timeout and may arrive twice; listMessages filters by direction, so missed inbound can be read back. No callback signing found and no handoff primitive.\n- **Bird API + MCP (Bird B.V.)**: Signed webhooks keep a stable webhook-id across retries (eight attempts over about 27.5 hours) and POST /v1/webhooks/{id}/replay redelivers failures without duplicates. A WhatsApp handoff guide exists, but no API flag pauses agent replies; the team inbox does that.\n- **ClickSend SMS API + MCP (ClickSend Pty Ltd)**: Inbound SMS can be pulled with GET /v3/sms/inbound and marked read, or pushed by inbound automation rules, but there is no handoff flag, and no retry policy or event id for pushed inbound was found.\n- **Infobip API + MCP (Infobip Ltd)**: Inbound arrives at a defined endpoint in real time or can be pulled with Get incoming messages, across SMS, WhatsApp and RCS in the Messages API. No handoff flag, and the reference pages for retry policy render by script.\n- **Kudosity (Known Pty Ltd)**: Inbound and delivery callbacks are retried four times (1 minute to 24 hours) and the list endpoints read messages back. WhatsApp sends are template-only in the API, so free-text replies inside the window aren't available, and there is no handoff flag.\n- **Linq (Linq App Inc.)**: Webhooks are Standard Webhooks signed with a webhook-id for dedupe and retried with backoff for up to 30 minutes; message details read a whole thread back. No handoff flag, and a per-pair limit of 30 messages a minute stops reply loops.\n- **Photon (Something Great Inc.)**: iMessage arrives over a gRPC stream with catchUp for missed events, and WhatsApp Business events carry resumable cursors; webhooks are signed and deduped. No handoff flag, and acc-64 saw the stream stop after a rate-limit refusal until a restart 20 hours later.\n- **Plivo API (Plivo Inc.)**: Inbound SMS and WhatsApp hit a message URL, and List All Messages filters by message_direction=inbound, so missed inbound can be read back. No handoff flag, and no inbound retry policy or event id was found in the pages read.\n- **Prelude (DING SAS)**: Inbound WhatsApp and RCS arrive as inbound.message.received webhooks with a message id, replies go through a dedicated endpoint, and webhooks retry for up to 2 weeks. No inbound list for replay found and no handoff flag.\n- **Sendblue (Round One, Inc.)**: Inbound posts to a receive webhook, and GET /api/v2/messages filters by direction and date for catch-up; the AI Agent plan allows 1,000 inbound contacts a line a day. No handoff flag, no idempotency key on sends, and acc-59 reports replies regularly over 20 seconds.\n- **Sinch Messaging APIs + MCP (Sinch AB (publ))**: MESSAGE_INBOUND and MESSAGE_DELIVERY are separate triggers, callbacks are signed and retried with backoff, and messages and conversations can be listed by API. Sinch warns of duplicate callbacks with best-effort dedupe only, and no handoff flag is documented.\n- **Telegram Bot API (Telegram Messenger Inc.)**: Updates carry a stable update_id and are held up to 24 hours for getUpdates or webhook redelivery. No handoff primitive (acc-31 asks how to hold one per chat_id), and acc-57 logged about 20 single-bot 502 outages in one day.\n- **Telnyx API + MCP (Telnyx LLC)**: Inbound and status webhooks are Ed25519-signed, carry meta.attempt, and are retried up to 3 times per URL before a failover URL. No inbound list endpoint for replay was found, and no handoff flag.\n- **Twilio API + MCP (Twilio Inc.)**: Inbound webhooks are signed and the Messages list reads history back; acc-65 acknowledges webhooks at once and replies from a worker. No idempotency key on sends and no handoff flag; acc-24 had WhatsApp replies fail silently until it added status callbacks.\n- **Vonage Messages API + MCP (Vonage Holdings Corp.)**: Inbound and status webhooks are signed JWTs with a payload_hash, over SMS, WhatsApp, RCS and more. The Messages API has no read endpoint for messages, so missed inbound can't be listed, and there is no handoff flag.\n- **Wati (Clare.AI Limited)**: Inbound and status webhooks, GET messages per conversation, assign-operator and conversation-status calls give a reply loop with handoff to a person. Webhooks need the Pro plan (Growth has none), and no inbound retry policy or event id was found.\n- **WhatsApp Business Platform (Cloud API) (Meta Platforms, Inc.)**: Inbound and status webhooks are signed and retried for up to 7 days, with duplicates possible. acc-27 had a verified webhook that never fired, acc-28 a trigger firing only on the first message, and acc-40 could not get WAF-blocked messages replayed; no handoff flag.\n- **YCloud (YCloud International Pte. Ltd.)**: Webhooks are signed with YCloud-Signature, retried, and carry an event id to dedupe; inbound messages support typing indicators. No inbound list endpoint for replay and no handoff flag in the API (the inbox is for people).\n\n## What stops agents finishing\n\n- webhook verified but real inbound events never arrive\n- status events and redeliveries trigger the agent as if they were new messages\n- inbound lost during downtime or blocked by a firewall with no replay\n- unofficial WhatsApp clients get the number restricted within messages\n\n## Around it\n\nBefore: messaging.get-sender-approved. After: support.handoff-to-person, crm.log-activity.\n\n## Where this comes from\n\nWeight 16 of 100 in Messaging APIs: 16 of 69 accounts; the n8n forum's most frequent production story (sales and order agents on WhatsApp) and most inbound-webhook failures\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/messaging.two-way-customer-agent.json, or the MCP tool get_use_case with id messaging.two-way-customer-agent. 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": "Answer customers who message the business, with handoff to a person",
        "url": ""
      }
    ],
    "description": "Answer customers who message the business, with handoff to a person: 0 companies fully do it, 20 with a limit, 52 carry the tag. Every listing in Messaging APIs with the reason and a source.",
    "facts": null,
    "h1": "Answer customers who message the business, with handoff to a person",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/messaging.two-way-customer-agent/",
    "published": "",
    "section": "agents",
    "title": "Answer customers who message the business, with handoff to a person |…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/messaging.two-way-customer-agent/"
  },
  "tokens": {
    "markdown": 2000,
    "slim": 380
  },
  "version": 1
}
