Store the recipient relationship used to prepare the message
Synthetic N-331 was prepared for billing contact B-OLD on order O-331. Before release, the confirmed billing recipient becomes B-NEW. Do not silently replace the address on an old message: its greeting and content may refer to B-OLD’s role. The fixture holds N-331 for content review, then prepares a message for B-NEW if still needed. A notification already delivered to B-OLD cannot be recalled merely by editing the CRM recipient.
| Message | Preparation recipient | Current relationship | Action |
|---|---|---|---|
| N-331; queued | B-OLD | B-NEW confirmed | Hold and review greeting/content |
| N-332; queued | B-NEW | B-NEW confirmed | Continue normal content checks |
| N-330; already delivered | B-OLD | Now B-NEW | Retain actual delivery; decide follow-up |
Make a fresh recipient-content decision
- Read prepared recipient link
- Compare confirmed current contact
- Review role-sensitive content
- Release current message or record suppression
An unconfirmed new endpoint blocks sending; staff must not infer the intended recipient from a forwarded message alone.
Does changing O-331 to B-NEW make N-330’s delivery history show B-NEW?
Show the worked answer
No. It was delivered to B-OLD. Preserve that fact and separately decide whether B-NEW needs a current notification.
This is recipient-content consistency, not a consent-sync or account-permission example. The fixture cannot undo a message already sent.