Webhooks for every update
Receive messages, delivery updates and connection status at your endpoint.
message.delivered
message.read
message.received
New MCP tools — operate your workspace from your agent
Context-aware
Context-aware
WhatsApp infrastructure
for developers.
Send alerts with the data behind them, receive replies by webhook and let customers ask relevant follow-up questions.
Uses WhatsApp Linked Devices — no Meta Business approval required. How it works
Replies grounded in your data
Per-recipient delivery state
Failure reasons, not red dots
Session monitoring & re-pair
Playing
Your app sends the alert with data attached · your AI policy answers from that data — your key, your rules · your webhook receives everything else.
Start here
Connect, automate and respond
Connect your numbers, add relevant context and manage the workflow from one workspace.
Pair any WhatsApp number by QR
No templates, no approval queue
Text, media, documents, locations
Multiple numbers, one workspace
AI replies are optional
What ChatRail does
WhatsApp messaging, without the setup mess
Send messages, receive replies and see what happened in one place.
See every delivery
Know who received, read or missed each message.
Read
Delivered
Sent
Automatic retries
If something fails, ChatRail tries again and records the result.
1502 from your webhook
2502 from your webhook
3Accepted
Check numbers before sending
Find invalid or unreachable numbers before starting a campaign.
+1 (415) •••-0118registered
+1 (212) •••-4409landline — not on WhatsApp
+1 (646) •••-0042registered
1,284 checked · 37 rejected before the first send
Inside the workspace
One place to manage everything
Check connections, schedule messages, review deliveries and test your setup.
01Connections
01 — Connections
See which numbers are connected
Spot a disconnected number and pair it again before messages are missed.
- One webhook URL per connection
- Re-pair by QR without touching the others
HFHomefinder+1 (415) •••-0118 Connected
SSStudio Shop+1 (310) •••-0907 Connected
WPWeekend Picks+1 (646) •••-0042 Re-pair
02Scheduler
02 — Scheduler
Schedule messages
Choose when messages should go out and let ChatRail handle the rest.
- Fixed, recurring or relative to a record
- Pause a schedule without deleting it
Weekly digestFri 09:00412
Rent due notice1st, monthly64
Appointment reminder24h beforeauto
Restock alerton trigger—
03Log
03 — Message log
Find failed messages
See the message, its status and the reason it failed.
- Searchable by number, status or connection
- Failure reason, not just a red dot
08:58Invoice INV-9F24 is due on 30 Sept not_registered
08:41Your table is booked for 8:00 pm media_too_large
08:12Shipment CR-2048 cleared customs delivered
04Sandbox
04 — Sandbox
Test before going live
Send a test message and check the response before reaching customers.
- Throwaway number, no production traffic
- Replay any logged payload against it
POST /v1/messages/text { "connection": "sandbox", "to": "14155550118", "body": "Ping" }
200 OK 86ms { "id": "wamid.S4nDb0x…", "status": "sent" }
Edit the body, then send
How it works
Go live in four steps
Connect a number, send a message and start receiving replies.
Waiting for scan
- 1 Open WhatsApp on the phone that owns the number
- 2 Settings → Linked devices → Link a device
- 3 Scan this code. The phone keeps working as normal.
Session persists until the phone unlinks itlinked-device · session
POST https://api.chatrail.dev/v1/messages/text // Authorization: Bearer $CHATRAIL_KEY { "connection": "homefinder", "to": "14155550118", "body": "A 2-bed just came up in your saved area." }
201 Created 94ms { "id": "wamid.A1xK9p…", "status": "sent", "queued_at": "2026-09-13T10:22:04Z" }
No SDK — any HTTP client workscurl · fetch · requests
message.delivered
message.read
message.received
session.disconnected
Signed with X-ChatRail-Signatureidempotency-key on every event
+1 (415) •••-0118
+1 (310) •••-0907
Per recipient, not per batchexportable as CSV
The API
Send a message with one API call
- REST over JSON with a bearer token. Nothing to install.
- connection picks the number you're sending from.
- Attach a context object and AI replies answer from it.
- Signed webhooks with an idempotency key on every event.
api.chatrail.dev/v1 · bearer token, JSON in and out
Optional layer
Let customers ask about any alert
Attach the relevant data when you send an alert. If someone replies with a question, AI answers using that information.
context · invoice_9F24
attached
{
"invoice": "INV-9F24",
"total": "USD 1,840",
"paid_to_date": "USD 600",
"due_date": "2026-09-30",
"late_fee": "2% of the outstanding balance"
}
What happens if I pay after the 30th?
AI replyYou'd owe the $1,240 still outstanding plus a 2% late fee — about $24.80. Paying on or before September 30 avoids it.
- Grounded in your data. The model only sees the context object you attach to that conversation.
- Scoped and expiring. Context belongs to one thread and drops after a window you set.
- Hand-off built in. When the answer isn't in the context, ChatRail says so and fires a webhook instead of inventing one.
- Your key or ours. Bring your own model key, or use metered usage on the ChatRail account.
Fits your stack
Connect the tools you already use
Use your preferred AI model and trigger messages from your app, store, CRM or automation tool.
Bring your own model
Point AI replies at your own provider account, or use metered usage on ours. Choose a model for each connection and change it at any time.
Anthropic
OpenAI
Google Gemini
DeepSeek
◇ Any OpenAI-compatible endpoint
◇ Self-hosted — set your own base URL
Works with your existing stack
Your app triggers the message. ChatRail delivers it through WhatsApp, then posts replies and delivery updates to your webhook.
Shopify
Stripe
HubSpot
Zendesk
Cal.com
Airtable
Sheets
Supabase
Make
n8n
Zapier
↗ anything that can POST
Manage ChatRail from your coding assistant
Use MCP to check connections, investigate failed deliveries and manage schedules without leaving your editor.
Your agent
Why did message 9F24 fail?Claude Code · Cursor · Codex
request
CHATRAILMCPAuthenticated workspace access
context + action
Live workspace
Connections3 live
Delivery1 failed
Message logPayload found
Schedules4 active
✓
Cause found: recipient is not registered on WhatsApp.
Replay in sandbox →Customer story
MarketPulse runs its private alert desk on ChatRail.
A paying customer turns continuously monitored events into structured WhatsApp alerts—without asking its private group to watch another dashboard.
Customer outcomeLess time spent checking alerts across systems—and a conversational way to understand the data behind client behaviour.
2,400+alerts delivered60 daysrunning62 / 62recent sends accepted24 msmedian API response
MarketPulse is the privacy-safe name of a paying ChatRail customer. Identifying details and message data have been anonymised. The 62/62 acceptance rate and 24 ms median reflect one inspected provider log window, not end-to-end WhatsApp delivery.
Pricing
Simple pricing per connected number.
Start free and upgrade when you are ready.
Messaging
Sandbox
$0/ month
For testing and personal automations.
- 1 connected number
- 500 messages / month
- Basic API and webhooks
- 7-day message log
Messaging
Core
$15/ month
For production alerts and workflows.
- 1 connected number
- 10,000 messages / month
- Media, groups and scheduling
- Retries, logs and session monitoring
Recommended
Messaging + AI
Core + AI
$29/ month
For replies grounded in your alert data.
- Everything in Core
- Context-aware replies
- Expiring thread memory
- Bring your own model key
- MCP tools for your coding assistant
Teams
Team
$79/ month
For agencies and multi-client workspaces.
- 5 connected numbers
- 50,000 messages / month
- Per-client webhooks and credentials
- Member access and priority support
Extra number: $8/month · BYOK is included with Core + AI · Managed AI: provider cost + 25% · Annual billing: 2 months free.
Build your first WhatsApp workflow.
Sign in to the dashboard and tell us what you want to connect.
What’s included
Messaging, scheduling, webhooks, workspace monitoring and MCP tools. AI is optional.
How it connects
A linked-device session against a normal WhatsApp account — not Meta's Business Platform. What that means →
Security
Bearer-token API access, signed webhooks and isolated credentials for each connection.