Contact sync
Contacts sync both directions. A change on the booking platform updates the matching HighLevel contact, and a change in HighLevel pushes back to the platform — matched by ID first, then by email, so the same person never turns into two records.
Which way data flows
- Mindbody / Booker → HighLevel — client created / updated webhooks create or update the contact.
- HighLevel → Mindbody / Booker — contact create / update pushes identity back to the platform.
AutoSync writes 67 fields onto each contact (53 Standard + 14 Pro). Every one is prefixed with
⇌ — the full list is in the custom fields reference.
How each field updates
| Behavior | What it means |
|---|---|
| Always | Every newer event overwrites the current value. |
| Write-once | The first non-null value wins and is never changed — used for start date, first-visit date, waiver date, source IDs, and UTM fields. |
| One-way upgrade | The value only moves forward, never back — used for Client Type (Prospect → Member). |
Client Type: once a member, always a member
The ⇌ Client Type field is either Prospect or Member. It flips to Member the first time
the client buys one of the pricing options you marked as a membership, and it never reverts — even
after every membership expires. For finer distinctions (active vs. lapsed), use
⇌ Overall Status or the membership fields instead. See Memberships.
Marketing permissions (DND)
HighLevel stores consent as Do-Not-Disturb flags with inverted logic — DND Email = true means
"don't email." AutoSync maps your platform's permission flags onto HighLevel's DND flags and the
⇌ Allow Permissions checkbox (Email / SMS × Account / Schedule / Promotion). Mindbody's six
granular flags and Booker's three broader flags both normalize cleanly.
Duplicate & household contacts
When a new client shares a phone or email with an existing contact — common for couples and
families — AutoSync keeps the first person as the primary and creates the second as a linked
contact with a synthetic email, tagging both ⇌ Shared Phone or ⇌ Shared Email. Nothing is
overwritten, and the built-in AI assistant can disambiguate household members on request.
If a purchase or membership event arrives before the client record exists, AutoSync fetches the full profile from the platform and creates the contact with proper fields — so out-of-order events heal themselves.
Last updated July 2026