# Inbox sync

How Zernio matches inbox contacts to HighLevel contacts and logs every conversation, call and delivery status on the contact.

Once a sub-account is connected, every message the profile's inbox receives or sends, and every call it makes or takes, lands on the matching HighLevel contact within seconds. There is nothing to call.

## Match a contact

For each message or call, Zernio finds the HighLevel contact for the person, in this order:

1. The contact it already linked for this person.
2. A contact with the same phone number, read from the person's WhatsApp, SMS, RCS or iMessage channel (or the caller's number).
3. A contact with the same email address: the person's email, else the address of their Gmail, Outlook or IMAP channel.
4. Otherwise, with `syncContacts` on, a new contact with the person's name, phone and email, source `Zernio`. A TikTok or Telegram user, with neither, is created by name.

The match is remembered, so later messages go to the same contact. Zernio never overwrites a matched contact's name or fields.

## Log a conversation

With `logMessages` on, the messages are logged on the contact as one note per channel and UTC day. Telegram, LINE, WeChat, iMessage and RCS go to [Conversations](/platforms/gohighlevel/conversations) instead while `mirrorConversations` is on.

```text
WhatsApp conversation · 2026-11-21
09:00 ← Hola, ¿tenéis plazas para diciembre?
09:02 → Sí, te paso las fechas · ✓ read 09:03
```

`←` is a message the person sent, `→` one the business sent. Attachments are listed as links. A busy day continues in `(part 2)` notes. Each message is logged once.

Channels: WhatsApp, SMS, RCS, iMessage, Instagram, Messenger, Telegram, X, Bluesky, Slack DMs, TikTok, LINE, WeChat, Gmail, Outlook and IMAP.

## Delivery status

With `logDeliveryStatus` on, each outgoing line shows how far the message got: `✓ sent`, `✓ delivered`, `✓ read` or `✗ failed`, with the time. A status never goes backwards.

## Calls

Every WhatsApp and phone call on the profile becomes a note on the caller's contact: direction, outcome, duration, and the transcript when transcription is on. Calls follow `logMessages`.

## Push a contact from a workflow

Add a `gohighlevel_upsert_contact` node to a [workflow](/products/automations/workflows) to write to HighLevel at a chosen step, for example after a qualifying question:

```json
{ "id": "crm", "type": "gohighlevel_upsert_contact", "config": { "email": "{{answer}}", "tags": ["whatsapp-lead"], "properties": { "companyName": "{{company}}" } } }
```

It finds the linked contact, else one with the same email, then phone and writes only the fields the node sets. A new contact also takes the Zernio contact's name, email and phone.

- `tags` are added to the contact's tags, never replacing them.
- `properties` takes standard contact fields (`companyName`, `source`, `city`, `state`, `country`, `postalCode`, `address1`, `website`, `timezone`, `dateOfBirth`, `assignedTo`) or custom field keys.

The node saves `{ id, created }` to `gohighlevelContact` (or `saveAs`) and follows `success`, or `error` when HighLevel is not connected or refuses the write.

## How it behaves

- Messages sync for conversations linked to a Zernio contact; others are skipped.
- With `syncContacts` off and no match, the message is skipped rather than creating a contact.
- If the contact or its note was deleted in HighLevel, Zernio finds or creates the contact again and starts a new note.
- Zernio stays well under HighLevel's limit of 100 requests per 10 seconds per sub-account. When HighLevel rate limits a sub-account anyway, the sync waits and retries, so a busy sub-account can lag by a few minutes.
- Only messages from after the connection sync. Earlier conversations are not backfilled.
- An existing connection starts syncing after its settings are saved once or the app is reinstalled.

## Related

- [Settings](/platforms/gohighlevel/settings)
- [Update HighLevel settings](/accounts/update-gohighlevel-settings)
- [Conversations](/platforms/gohighlevel/conversations)