Hello Alex Docs

Connect Your CRM

Authenticate providers, map fields, and maintain reliable contact sync. Read the CRM guide in Hello Alex documentation.

Overview

CRM integration is important because disconnected data creates audience mismatches and weak reporting.

Provider authentication establishes secure access, then field mappings decide how CRM attributes populate Hello Alex contact records.
Sync logs expose drift and failures early, so campaign imports can be corrected before launch.

Good to know: mapping phone and identity fields carefully prevents silent drop-offs during campaign audience creation.

Connection health is the foundation for dependable CRM data flow.

Open field mappings for the connected provider and validate core contact fields.

You select a provider and authenticate, which establishes tokenized access for sync operations.
Status indicators reveal whether imports can run successfully or need reconnection.
Connection status: Healthy connections sync on schedule.
Good to know: starting with one provider simplifies troubleshooting before multi-system workflows.
First-time CRM linkage
Connection recovery after credential rotation

Mappings define data meaning, so clean mapping directly improves launch quality and personalization.

Trigger a manual sync and inspect resulting records in Contacts.

Fields are aligned between systems, ensuring phone, name, and custom metadata are interpreted correctly downstream.
Saved mappings become the schema for future syncs, which keeps campaigns consistent over time.
Field mappings: Control which CRM fields flow into contacts.
Good to know: mismapped phone fields are a common cause of missing or invalid contacts during import.
Custom field personalization
Standardized contact schema across teams

Sync policy controls freshness and reliability of CRM-backed audiences.

Confirm stable sync behavior, then use Import from CRM in campaign setup.

Auto or manual sync cadence determines how quickly source updates reach Hello Alex.
Logs surface partial failures and API issues, enabling fixes before they impact launch audiences.
Sync logs: Successes and errors after each sync.
Good to know: checking logs after schema or permission changes prevents stale data from propagating silently.
Nightly contact refresh
Pre-launch sync validation

Run a test sync and verify imported contact count before using CRM audiences in production campaigns.