Problem
Incoming contact webhook payloads currently include the contact displayName and vcard, but the phone number is only embedded inside the vcard. Consumers need to parse the string manually to recover the number.
Current payload
{
"contact": {
"displayName": "Alice",
"vcard": "BEGIN:VCARD...TEL;type=Mobile:+62 812 3456 7890..."
}
}
Requested change
Expose the contact phone number explicitly in the webhook payload, for example as:
contact.phone_number for single contacts
- each item in
contacts_array should also include a phone number field
Why this helps
- Avoids consumers needing to parse
vcard manually
- Makes webhook integrations simpler and less error-prone
- Keeps the payload easier to use for automation and CRM syncs
Acceptance criteria
- Single contact webhooks include a structured phone number field
- Multi-contact webhooks include a structured phone number field for each contact
- Existing
vcard behavior remains unchanged for backward compatibility
- Documentation examples are updated accordingly
Problem
Incoming
contactwebhook payloads currently include the contactdisplayNameandvcard, but the phone number is only embedded inside thevcard. Consumers need to parse the string manually to recover the number.Current payload
{ "contact": { "displayName": "Alice", "vcard": "BEGIN:VCARD...TEL;type=Mobile:+62 812 3456 7890..." } }Requested change
Expose the contact phone number explicitly in the webhook payload, for example as:
contact.phone_numberfor single contactscontacts_arrayshould also include a phone number fieldWhy this helps
vcardmanuallyAcceptance criteria
vcardbehavior remains unchanged for backward compatibility