Messaging

Receive SMS & reply,
two-way.

Give customers a number to text. Receive inbound SMS — plus WhatsApp, Viber and Telegram — in real time via webhooks, fire keyword auto-replies, and keep every two-way conversation logged and threaded.

Contact Sales →All products

Receive SMS · Real-time inbound webhooks · Keywords, auto-reply & logs

Live conversation

What you get

Inbound, handled end to end

⚡

Real-time webhooks

Every inbound message is normalised and POSTed to your endpoint as a message.inbound event — signed, retried, at-least-once.

📋

Message logs

Inbound and outbound in one log, filterable by channel, direction, sender, status, app and date — newest first.

💬

Unified inbox

See conversations across channels in one place, with a complete, auditable record for support and compliance.

SMSWhatsAppViberTelegram

Don’t lose the reply

When customers reply, your systems should already know

Customers reply on the channel they prefer. TextCall ingests inbound across channels, reacts in real time, and keeps every message visible — so support, bots and CRMs all stay in sync.

✓ Inbound normalised into one model across channels — no provider quirks leaking through.
✓ Standard signed webhooks with retry on timeout, 5xx and 429.
✓ Every inbound message stored and shown in logs, even if your webhook is down.
✓ Automatic per-country billing and auditable records for finance.

Talk to our team →

How it works

Real-time

Inbound webhooks

Channels in one inbox

100%

Inbound logged

Signed

Secure delivery

See it in action

An inbound text, handled in a heartbeat

A customer texts your number, we fire a real-time message.inbound webhook, and your auto-reply goes straight back — every message logged and threaded.

Inbound SMSfrom +44 7700 900 123 · to 12345

JOIN

POST /webhook · message.inbound ✓

Welcome! You’re subscribed. Reply STOP to opt out any time.

For developers

Built for developers — read the docs

Every inbound message across SMS, WhatsApp, Viber and Telegram is normalised into one model and POSTed to your endpoint — signed, retried, at-least-once. Reply on any channel over one API.

✓ One message.inbound model across every channel.
✓ Signed webhooks with retry on timeout, 5xx and 429.
✓ Reply over one API on the channel the customer used.
✓ Every message stored and shown in logs and the inbox.

Read the documentation →

inbox.sh

# Reply to an inbound message on any channel
curl -X POST https://api.textcall.com/v2/messages \
  -H "Authorization: Bearer $TEXTCALL_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+35799000000",
    "channel": "whatsapp",
    "text": "Thanks \u2014 all sorted!"
  }'

# → 200 OK · queued · reply threaded in the inbox

Contact Sales

Turn replies into conversations

Tell us which channels you want to receive on — we’ll set up inbound webhooks, logging and your inbox.

Contact Sales →Explore all products

Receive SMS & reply,two-way.