Guide · 07 Mar 2026
Email + WhatsApp: frequency, consent, and a practical guide for South African teams
Operational guidance for coordinating promotional and transactional messaging — not legal advice, but the product discipline that keeps trust and deliverability intact.
Important caveat
This is not legal advice. POPIA, consent rules, and platform policies deserve proper review with counsel for your specific context. What follows is product and operations discipline we use to reduce risk and customer annoyance.
Separate transactional from promotional intent
Customers tolerate — and often want — transactional messages when they are accurate:
- order confirmations,
- dispatch updates,
- delivery delays explained plainly.
Promotional messages compete for attention and trust. Treat them as a budgeted channel with caps.
One policy for frequency
Define a weekly cap for promotional touches across email and WhatsApp, and enforce suppression rules when:
- a customer is in an active support escalation,
- a delivery is late and emotions are high,
- or a refund is in flight.
Practical coordination patterns: Omnisend + WhatsApp same customer journeys.
WhatsApp: clarity beats clever automation
WhatsApp feels personal. That is why bad automation feels offensive faster than a generic email.
Use structured flows, explicit handover, and logs your team can trust: WhatsApp lead capture and handover.
Email: deliverability is a behaviour problem
List hygiene and honest subject lines beat tricks. If your lifecycle strategy is strong, you will send fewer-but-better emails — see Omnisend flows.
Ops alignment
Marketing should not surprise support. If campaigns spike tickets, your segmentation is wrong — or your site/checkout promises are wrong.
Services: Omnisend · WhatsApp bots · WhatsApp automation (ZA)
Next step
Share your current touch map (even rough). We will propose a coordinated cadence and the integration hooks to support it.
Contact: Contact.