FORMS NOT SENDING — FICTIONAL RECONCILIATION EXAMPLE

Original editorial exercise. All identifiers, timestamps, queues and records are invented. No email, form, CRM, sales workflow or customer was accessed.

Snapshot: 2026-10-20 12:00 UTC. Seven eligible source submissions and seven destination rows. The destination rows represent enquiry work items, not contacts. The example expects one work item per eligible submission.

Example rules: allow ten minutes after submission for destination receipt. Review an assigned work item without an acknowledgement more than thirty minutes after receipt. These are teaching assumptions, not service promises or platform defaults. The classifier reports the first applicable exception for each submission.

Join using submission_id. Contact identity is not a submission key. E01 and E07 legitimately share CONTACT-1. E02 has two work items. E03 is absent after the example window. E04 has no owner. E05 lacks an acknowledgement after its example window. E06 is only two minutes old, so remains pending. E99 is unexplained in this source export and requires investigation rather than deletion.

Expected report: five review exceptions, one pending submission, two expected records. Eight report rows represent the union of observed identifiers. The three CSVs can be opened as tables; these are not production import instructions.
