إرسال بطاقة جهة اتصال (vCard)

Professional Identity: Mastering the Contact Card (vCard) Engine

In a professional ecosystem, sharing contact information shouldn't be about typing out phone numbers. The /v2/send/contact endpoint allows you to share digital business cards (vCards) that are interactive, easy to save, and high-fidelity. By automating the sharing of contact cards, you can streamline the "Agent Handoff" process, provide instant access to emergency helplines, or share specialized technician details with a single API call.

🏗️ The VCard Serialization Pipeline

Sharing a contact via Wawp is more than just sending a name. Our engine manages a sophisticated serialization process to ensure compatibility with both Android and iOS contact managers:

1. vCard Specification Encoding: Wawp takes your JSON contact array and transcribes it into the standard vCard (VCF) v3.0 format. This format is universally recognized by mobile operating systems, ensuring that when the user clicks "Save," the fields map correctly to their local address book.
2. Identity Verification: The whatsappId field is critical. Our engine uses this to link the vCard directly to a WhatsApp profile. This allows the recipient to immediately see the contact's profile picture and start a one-click message thread without even saving the number first.
3. Multi-Contact Batching: Wawp supports sending multiple contacts in a single "Message Bubble." This is handled by concatenating the serialized VCF blocks into a single payload, providing a clean "Team" or "Directory" view for the user.

🛡️ Strategic Best Practices for Digital Identity

1. The "Wholesale Profile" Strategy

A bare-bones contact card looks suspicious to users. To build brand authority:

• Rich Metadata: Always provide the organization and fullName.

• Professionalism: If the contact is an agent, include their department (e.g., "Sarah - Senior Consultant").

• Formatting: Ensure phoneNumber includes the international + prefix. This is distinct from the whatsappId, tips: [ { type: 'info', title: 'Format', content: 'Sends a vCard (VCF) file that can be saved directly to contacts.' }, { type: 'info', title: 'Fields', content: 'Supports multiple phone numbers, emails, and addresses.' } ], recommendations: [ "Include a properly formatted name (N, FN properties) for best compatibility.", "Use this to share support line numbers efficiently." ]

  which is just the numeric digits used for network routing.

2. Streamlining the Agent Handoff

In a bot-to-human transition:

• Implementation: Instead of the bot saying "Now talking to Mark, his number is 123," have the system automatically trigger a /v2/send/contact call for Mark's vCard.
• UX Impact: This gives the customer a clear "Professional Point of Contact" bubble that they can refer back to later, increasing the transparency of your support flow.

3. Validation and Filename Integrity

• Character Limits: Keep the fullName under 40 characters. Longer names can be truncated in the chat preview or result in messy address book entries.
• Emoji Usage: While emojis are supported in the name field, use them sparingly. Excessive emojis in a vCard name can sometimes interfere with search indexing in a user's local contact app.

🧩 Advanced Use Cases

Corporate Staff Directories

Send a "Support Directory" message containing three distinct contact cards: "Billing Support," "Technical Desk," and "Human Resources." By sending these as a single array, the user receives one clean interactive list rather than three separate messages.

Referral and Loyalty Programs

Automate your referral system. When a user qualifies for a partner offer, send the partner's professional contact card via Wawp. The reply_to parameter can be used to link this contact card to the specific "Reward Earned" text message, making the context immediately clear.

🛠️ Common Pitfalls and Solutions

• Malformed WhatsApp IDs: If the whatsappId doesn't match a real account, the "Message" button on the vCard will be disabled on the recipient's phone. Always verify your agent IDs before sharing.
• Header Discrepancies: If you provide a vcard string directly (via the legacy fields), ensure it starts with BEGIN:VCARD and ends with END:VCARD. Wawp will return a Serialization Error if the block is malformed.
• Phone Number Confusion: Users often forget the + in the phoneNumber field. While Wawp attempts to normalize this, provide it explicitly to ensure the user's phone recognizes it as a clickable dialer link.

Summary of Capabilities:

• Deliver interactive, native-style WhatsApp contact cards (vCards).
• Support for batching multiple contacts (Staff/Directory) in a single message.
• One-click "Save Contact" and "Message" functionality for the end-user.
• Automated VCF v3.0 serialization for universal iOS/Android compatibility.
• Seamless integration with threading/replies via the reply_to parameter.
• High-fidelity identity sharing with full support for Organization and Job Title fields.