Keep continuity
Continue using the established account and conversation identity.
Keep the number your customers already know, pair it as a linked device and add server-side sends, webhooks and connection monitoring.
Add automation without asking customers to learn a new phone number.Continue using the established account and conversation identity.
Trigger useful alerts from orders, properties, monitoring or internal systems.
Send inbound messages back to the application that owns the workflow.
The account owner scans a QR code from WhatsApp’s Linked Devices screen. ChatRail assigns the connection to one workspace and your application addresses it by a stable connection identifier. Access to pairing and session controls should be restricted to workspace administrators.
Use a dedicated operational number where possible, confirm recipient consent and begin at low volume. Existing conversations and reputation make careless automation more costly. Do not import scraped lists or allow untrusted users to choose arbitrary recipients.
Define which events may send automatically and which require review. Store the source event ID, outbound message ID and recipient together so a later reply can be correlated without guessing from message text.
Document how to pause automation, revoke credentials, unlink the device and export the application-owned event history. Your source data should remain in your system so changing the transport does not require rebuilding the workflow.
Yes, it remains the primary account while ChatRail operates as a linked device.
Do not assume historical conversations are imported. Design workflows around events and messages created through your connection.
Yes. An authorized owner can revoke the linked session and application credentials.
Validate the connection, delivery state and reply path before increasing traffic.
Gain Access