# WhatsApp to Attio demonstration field dictionary

Six fictional records illustrate documented sync attributes and a proposed follow-up process. They are not exported CRM records, import-ready files, or evidence of a live connection. Only the six whatsapp-prefixed attributes below use documented WhatSync slugs. Other columns are demonstration representations or proposed configuration.

| Column | Classification | Type | Meaning and mapping |
| --- | --- | --- | --- |
| demo_record_id | Demonstration identifier | Text | Example record identifier; not an Attio record ID or API field. |
| demo_person_name | Demonstration representation | Text | Fictional People record display name; not an API payload. |
| demo_company | Demonstration representation | Text | Fictional company context. A People-to-Company association would need workspace mapping. |
| contact_phone_e164 | Demonstration representation | Text | Example of a normalized standard contact number. This column name is not the standard Attio attribute slug. |
| whatsapp_last_message_at | Documented WhatSync-created attribute | Timestamp | Documented slug. Constructed UTC time of the most recent message. |
| whatsapp_message_direction | Documented WhatSync-created attribute | Select | Documented slug. inbound and outbound are demo labels; verify actual option mapping before import or API use. |
| whatsapp_total_messages | Documented WhatSync-created attribute | Number | Documented slug. Illustrative count, not measured activity. |
| whatsapp_conversation_link | Documented WhatSync-created attribute | Text | Documented slug. wa.me link to a reserved example number; not a real customer chat. |
| whatsapp_phone_number | Documented WhatSync-created attribute | Text | Documented slug. Example raw number without formatting. Preserve as text. |
| whatsapp_agent_name | Documented WhatSync-created attribute | Text | Documented slug. Fictional teammate who handled the conversation; not necessarily the follow-up owner. |
| proposed_context | Proposed Techmark follow-up field | Text | Original summary for a reviewer. In a live setup it must be checked against the relevant source note. |
| proposed_next_action | Proposed Techmark follow-up field | Text | Specific work proposed after review. Empty when there is no open action. |
| proposed_owner | Proposed Techmark follow-up field | Text | Person responsible for review or the action. Map to a workspace member when implemented. |
| proposed_due_at | Proposed Techmark follow-up field | Timestamp | Constructed UTC deadline. Blank for a closed item; show in the reviewer timezone. |
| proposed_review_state | Proposed Techmark follow-up field | Select | Demo labels: Ready for a person to act, Needs identity review, Needs clarification, Awaiting client input, Closed. |
| proposed_match_state | Proposed Techmark control field | Select | Demo labels: Matched and Ambiguous phone. This is not a documented WhatSync match-status field. |

## Data conventions

Timestamps use ISO 8601 UTC. For example, 2026-10-12T15:00:00Z is 11:00 a.m. America/New_York and 10:00 a.m. America/Lima on that date. An empty due date means no open deadline, not midnight. Counts are illustrative integers. Phones and record IDs are text. The two rows sharing +12025550101 are deliberate matching exceptions; keep both visible for the demo.

Names and companies are fictional. Links point to reserved example numbers. They should not be used for messaging. The repeated WhatsApp values on DEMO-001 and DEMO-006 illustrate ambiguous mapping, not actual vendor behavior.

## Implementation mapping

Before using these structures in a workspace, map standard contact fields, custom attributes, list entries, workspace members, date types, and select options. The follow-up fields can live on a list entry linked to a People record. Phone match review, action assignment, and due dates are proposed process rules; the file does not claim WhatSync automatically provides them.

The sync source is described by [WhatSync’s setup guide](https://whatsync.app/docs/attio-crm). The proposed process uses the list concept described by [Attio](https://docs.attio.com/docs/objects-and-lists).