GHL Close sync proof.
A mock two-way sync proof for Close appointment events and GHL contact changes. It uses a contact map, field policy, dedupe guard, conflict review queue, and written handoff before any live CRM write. No live GHL or Close writes are used.
Sync Ledger CSV
Conflict Review Queue CSV
Error Log CSV
Contact Map CSV
Field Policy CSV
Close Events CSV
GHL Changes CSV
Handoff
Runbook
Source Script
Close To GHL
Appointment events become reviewed GHL activity updates when the contact map and appointment fields are stable.
GHL To Close
Allowed contact changes become reviewed Close updates only after field policy and source-of-truth checks pass.
Conflict Policy
Missing contact matches, duplicate correlation ids, and identity-field changes are blocked before either CRM is touched.
| Event | Direction | Decision | Destination | Reason |
|---|---|---|---|---|
| close-evt-2301 | Close to GHL | Ready for reviewed GHL update | ghl-501 | Stable contact match and appointment status field. |
| ghl-evt-2305 | GHL to Close | Ready for reviewed Close update | close-102 | Lead source is allowed by the field policy. |
| close-evt-2304 | Close to GHL | Conflict review | blocked | Duplicate correlation id would replay the same side effect. |
| ghl-evt-2306 | GHL to Close | Conflict review | blocked | Email identity changes require a human source-of-truth decision. |