Skip to main content

Summary

Use this page as the quick reference for which contact fields matter most during import or sync setup.

Why this page matters

The current app explicitly tracks fields such as:
  • email column
  • phone column
  • contact name column
  • timezone column
That means field mapping is not a minor detail. It is one of the main reasons an import can technically succeed but still be operationally wrong.

High-priority fields

FieldWhy it matters
EmailRequired for email-based communications and identity quality
PhoneRequired for SMS or call workflows
Contact nameSupports personalization and contact readability
TimezoneHelps communications happen at the right local time

What this page should include later

  • provider-specific mapping examples
  • CSV header examples
  • fallback expectations when a field is missing
  • common bad-mapping patterns and how they appear in the product