What syncs

Contacts and owners provide identity, lifecycle, and ownership context. With additional permissions, ZoeRelay can also cache bounded company identity, deal stage/value, and ticket metadata. ZoeRelay does not import every CRM property, email, activity, or note.

Permissions

Contact read/write and owner read are required. Company, deal, and ticket access is optional. ZoeRelay shows unavailable capabilities as requiring permission instead of failing the Inbox.

Contact matching and ownership

Contacts match by normalized email inside one ZoeRelay workspace. HubSpot remains authoritative for CRM fields. ZoeRelay remains authoritative for support conversations, internal notes, SLA state, and ZoeRelay tickets.

Companies, deals, tickets, and notes

Related CRM records are shown only when HubSpot associates them with the mapped contact. Sending a ZoeRelay conversation summary as a HubSpot note is optional, explicit, bounded, and retry-safe.

Reliability

Synchronization uses durable database jobs, cursor checkpoints, retry with backoff, a dead-letter queue, signed webhook ingestion, deduplication, and daily reconciliation. Disconnect stops provider processing and removes local OAuth credentials without deleting support history.

Privacy and troubleshooting

ZoeRelay stores only the CRM context needed for support. A HubSpot record deletion clears the provider mapping but does not erase ZoeRelay support history. If authorization expires, reconnect from ZoeRelay Integrations. For persistent sync or permission issues, contact [email protected] with a safe timestamp and workspace name—never send tokens or customer messages.