One message per person, not one per record
A message saying your results are ready is useful, until the same person gets three in five minutes. Here is the simple rule we use to send one per visit, and why it applies to any notification system.
Telling people by text that something is ready saves them a trip and saves the front desk a phone call. But a notification only helps if people trust it. When the same person gets several messages within a few minutes, they stop reading them, including the one that matters.
Why one visit can mean several messages
In most operations, one visit can produce more than one record. In a laboratory, one visit can mean more than one lab number: tests are ordered at different points, added after the first request, or entered separately even though they run on the same sample. That is normal practice, and it exists for good reasons such as billing, sections and referrals.
The trouble starts when the notification system treats every record as a separate event. A person with three records from one visit gets three "ready" messages, often minutes apart. Nothing is broken, yet the experience feels like spam.
The rule: one message per phone per visit
Before sending, the system asks one more question: has this phone number already had a message for a different record a few minutes ago? If it has, the new message is skipped, because the person has already been told about this visit.
- A phone that has been quiet for a while can be messaged again. That is a new visit.
- Every skipped message is logged with its reason, so the rule can be checked rather than taken on trust.
- The check also covers items that become ready in the same run, so two messages cannot slip out together.
- Items that are on hold or cancelled never count as ready, so they never send a message at all.
What we kept on purpose
We still message as soon as something is ready, rather than waiting until everything in the visit is done. A person should have whatever is ready without delay. The aim was fewer pointless messages, not slower useful ones.
If you run notifications
- Notify the person, not the record. Internal IDs are for your team. People think in visits.
- Pick a window that matches how you work. The right window depends on how work moves through your operation. Pick one that matches it.
- Log what you don't send. A skipped message with a reason is easy to audit. A silent skip is not.
- Never hold back something that is ready to make the messages tidier.
It is a small rule, but it decides whether people trust a notification or learn to ignore it.