Use separate transport and business states
AWS SES documents Send and Delivery as different events; a Delivery event means delivery to a recipient mail server. It does not establish that a customer read or accepted the quote. Synthetic N-309 has mail-server delivery evidence and Q-309 still awaits a response. Another message has a send event with no delivery evidence. The local reconciliation keeps these states separate rather than deriving CRM stages from transport events.
| Notification | Transport evidence | Business evidence | Reconciled state |
|---|---|---|---|
| N-309 | Delivery to mail server | No customer response | Delivered transport; awaiting quote response |
| N-310 | Send event only | No customer response | Delivery unconfirmed; response absent |
| N-311 | No delivery evidence available | Separate valid acceptance recorded | Accepted quote; transport evidence incomplete |
Reconcile both records without inventing a link
- Locate message evidence
- Locate quote response evidence
- Classify each state independently
- Investigate missing transport evidence if needed
Do not resend an already accepted quote merely because delivery evidence is absent; check whether a further notification is actually required.
N-309 is delivered to the mail server. Can the opportunity linked to Q-309 be marked won?
Show the worked answer
No. The quote has no customer response. Delivery supports the transport record only; the acceptance gate remains unmet.
Only the cited SES event meaning is factual provider documentation. The local CRM states are synthetic; no SES setup, webhook handler or delivery guarantee is implemented here.