ChangelogWhat changed in ChatRail
Newest first. Anything that changes how an existing integration behaves is listed under Changed, with how to keep the old behaviour. Subscribe with the RSS feed.
24 September 2026 — AI replies that hold a whole conversation
New
- Context carries through the conversation. Each AI reply keeps the context of the message it answered, so a follow-up that quotes nothing — or arrives days later — is still answered about the same listing, order or booking. Correlation reported to your webhooks stays strict.
- A person can take over. When your team answers a lead by hand, automatic replies pause in that conversation for
human_takeover_minutes (a day by default; 0 turns it off). Replies skipped during the pause arrive as ai.reply_blocked with reason human_takeover. Messages with context (alerts) and scheduled sends do not pause; send pause_ai to decide explicitly. - Bursts get one answer. "hi" / "is the flat" / "still available??" now gets one reply that answers all three. Replies wait
reply_delay_seconds (5 by default) for the rest of a burst; the earlier runs show as superseded. - Edit what the AI answers from.
PATCH /v1/messages/{id} takes context with or without new text. A context-only edit has no time limit, never reaches WhatsApp, and also updates AI replies that carried the old context forward. Guide → - Group reply setting. The AI policy's
group_replies: addressed, all or off. Guide → - Nested context reaches the model.
{"property": {"address": …}} is flattened to property.address, up to four levels. Arrays are still left out and listed in omitted_keys. - API keys can manage webhooks and read usage.
/v1/webhook-endpoints accepts a key with webhooks:read / webhooks:write, so a deploy script can register its own receiver; every change is audited. The new usage:read scope opens GET /v1/usage.
Changed — check these if you use AI replies
- Automatic replies now wait 5 seconds before answering. Set
reply_delay_seconds: 0 for the old behaviour. - A hand-written reply to a lead who wrote in the last day pauses AI replies in that conversation for a day. Set
human_takeover_minutes: 0 to turn this off. - In a WhatsApp group, the AI now answers only messages addressed to your number — an @-mention, or a reply to one of your messages. Set
group_replies: "all" to answer every message as before. - A nested context field used to be left out of AI replies; it is now sent. To keep a field from the model, mark the context
context_sensitivity: "restricted".
Fixed
- Webhook signatures now verify. Deliveries were signed with the encrypted form of the endpoint's secret rather than the
whsec_… secret you were given, so signature checks failed. No change is needed on your side. Deliveries your endpoint rejected in that time are not retried; anything it accepted was genuine.
23 September 2026 — Richer WhatsApp messaging, managed AI, and social sign-in
New
- Managed AI on Core + AI: 10,000 AI replies a month on ChatRail's model key — no API key of your own needed. Team includes 50,000 and MCP.
- Quote, mention, polls and contact cards on
POST /v1/messages/text: reply_to, mentions (including "all" in groups), link_preview, poll, contact. Guide → - Act on sent messages: reactions, mark read, edit (15 minutes) and delete for everyone. Guide →
- Typing indicator via
POST /v1/connections/{c}/presence, and AI replies that mark the question read and show typing first (humanize, on by default). - New webhook events:
message.reaction, message.edited, message.revoked, poll.vote, group.participants_changed, call.received, and automatic call rejection per connection. - Group management: create groups, add and remove members, promote admins, change settings and invite links — with a limit of 20 member adds per hour to protect the number. Guide →
- Link a number with a pairing code instead of a QR. Guide →
- Group discovery over REST and MCP.
- Sign in with Google or GitHub in the dashboard.
Fixed
- The retention sweep no longer fails on alerts that had replies.
- Deleting a connection now also ends its WhatsApp session.
22 September 2026 — Unlimited messaging on paid plans
Changed
- Paid plans have no monthly message cap; number-safety limits still apply.
New
- Webhook endpoints can be scoped to one connection on any plan with more than one number — Core and Core + AI with an extra number, not just Team.
New
- Send WhatsApp messages with delivery tracking, scheduling, media, context attached to alerts and replies correlated to them, signed webhooks, AI replies, and MCP tools. Documentation →
