Define the evidence for each message state
Use separate states for prepared, submitted, delivery reported, failed and awaiting review. Provider terminology differs, so ask what each status actually establishes. Even a delivery report does not establish that the intended person read or understood the message. Keep patient confirmation separate. Staff should see the appointment reference and message purpose alongside the state, without opening a technical log to work out whether further action is needed.
Put failures into an owned queue
Assign a reception role to review unsuccessful messages during its staffed hours, with cover for absence. Show when the failure occurred, which administrative task it relates to and what staff should check next. An alert email is a prompt to open the task, not the task itself. Keep unresolved items visible across shifts and flag overdue review against the clinic agreed process, without inventing a universal response deadline.
Check contact details through the approved process
A rejected number or address may be outdated, mistyped or temporarily unavailable. Use the clinic verification process before changing a patient record or selecting another destination. Do not guess a corrected email address or send appointment details to a number found elsewhere. Record whether a contact correction was verified and who made it. If the identity or destination remains uncertain, leave the item for authorised staff review.
Choose a next action without blind retries
Decide which failure types can be retried and which require staff attention. A temporary service interruption differs from an invalid destination. Before retrying an uncertain send, check whether it already completed. Use only approved alternative channels and current communication preferences. Keep message content limited to the administrative purpose. Questions about symptoms, treatment or clinical priority belong in the clinic existing clinical process, not this delivery queue.
Rehearse one fictional failure from start to finish
For a fictional test, a reminder for an internal appointment returns an invalid-number status. Reception opens the failure task, verifies the test contact using the approved procedure and records the correction. The authorised resend then receives a delivery report. The task records delivery, but does not mark the appointment confirmed unless the separate confirmation step occurred. Use fictional details and a controlled destination, then remove test appointments through the normal process.
Close the task with a meaningful result
Record whether the contact was corrected, an approved alternative was used, staff made contact or further action is still pending. Preserve the original failure and subsequent attempts so another staff member can understand the history. Review repeated failures for the same destination before increasing retries. Report attempted sends, delivery reports and confirmed responses separately. A cleared queue should mean the required administrative action was completed or explicitly handed to an accountable owner.