Use idempotency keys and durable event records so retries never become duplicate customer alerts.
Developer guide for duplicate messages. Validate the behavior in your own stack before production rollout.Derive one key from the source event revision and recipient before the first send.
Send the same key on every retry and store the resulting message ID against the source event.
Treat timeouts as unknown outcomes; retry with the original key and cap attempts.
Measure duplicate conflicts, retry count and dead-lettered sends.
Reliable messaging is an operational system, not only an API call.
Gain AccessStart with the documentation or review the practical answers below.
No. ChatRail uses a WhatsApp Linked Devices session. Review the transport trade-offs before production use.
Yes. Sending, delivery tracking and webhooks work without enabling AI.
Use the Quickstart for your first request, then choose a workflow tutorial.
