TumaFlow guides
Customer notifications on WhatsApp
Trigger templated updates from your systems when real customer events occur—paid invoices, shipped orders, or account changes.
Notifications work best when they are expected, concise, and actionable. Use utility templates when messaging is tied to an existing relationship and the content is primarily transactional; avoid smuggling promotional language into utility categories against policy.
Integration patterns that scale
Emit domain events from your monolith or services (“InvoicePaid”, “LoanApproved”), and let a dedicated worker call TumaFlow’s API with idempotency keys derived from business IDs. That limits duplicate notifications when upstream systems retry.
Read receipts and support
Delivery and read signals help support teams reassure customers that alerts were seen. Tie webhooks into ticketing so agents see send state without leaving their helpdesk context.