A Minimal Lead Schema for WhatsApp CRM (Fields You Actually Need)

Disclosure: I build these handoffs at NxFlowAI.

WhatsApp CRM automation for multi-person teams collapses when the schema is either a novel or a single notes blob. Here is a minimal field set that has survived contact with real inboxes.

Required

• wa_id / phone (unique merge key)
• display_name
• last_inbound_at
• window_open_until (derived from last inbound)
• intent
• owner_user_id (nullable only if in triage queue)
• next_action + next_action_at
• approval_state (none|pending|approved|rejected)
• crm_record_id

Nice to have

• language_hint
• source_campaign
• risk_flags[]
• last_template_name

Provider-agnostic note

We integrate with all major CRMs (for example HubSpot, Zoho, Salesforce, Pipedrive and Freshsales, plus custom CRMs or Google Sheets setups) and work with all major WhatsApp Business providers and the official WhatsApp Business API (for example Meta Cloud API, Twilio, Gupshup, Interakt and WATI).

Process before schema: audit guide. NxFlowAI ≠ NexFlow/Nexusflo