For Marketing
Should this be marketed?
Not as a standalone feature. There is no new screen, setting, or capability — this PR fixes an invisible reliability bug in the Official WhatsApp integration. Nothing changes in what a clinic can see or do.
Where it's still useful material
If reliability of WhatsApp automation comes up (in a comparison, a case study, or a "why Dentolize" conversation), this is a legitimate, low-key data point:
"Dentolize's WhatsApp bot is built so that a burst of messages from a new patient — for example, two quick messages sent seconds apart before the clinic has ever spoken to them — doesn't cause any of them to be dropped."
Avoid quantifying this ("prevents X% message loss," "used to lose messages") — there is no telemetry cited in the PR quantifying how often the race actually occurred in production, and the fix has no test coverage yet (see For Quality). Describing the guarantee the fix provides is accurate; describing a before/after rate would not be honest without data to back it.
What not to say
- Don't imply this is a new feature ("now with reliable WhatsApp!") — reliable
message handling for a new contact's first message was always the intent; this closes a specific edge case in how it was implemented.
- Don't promise conversations are automatically merged when a contact is later
recognized under a second identifier (e.g., a masked and unmasked number, or WhatsApp Business ID vs. phone). That reconciliation is explicitly not part of this fix — see The race condition fix.