Phone Number Format

Overview

Many Talqui Session mechanics depend on a phone number as the channel identity of the contact. This is especially common in channels such as WhatsApp API Official and WhatsApp Business, where the contactExternalID sent to Talqui is usually the destination phone number that identifies the user in that channel.

Because of that, it is important to understand the number format expected by Talqui when your application sends phone numbers to Talqui endpoints. Talqui follows the international numbering logic defined by the E.164 standard, which provides a globally unique format for telephone numbers across countries.

What Is E.164

E.164 is the international public telecommunication numbering plan used to represent phone numbers in a globally unique way. In practice, it organizes a phone number into:

• a country code
• a national destination code, also known as area code
• a subscriber number

According to the E.164 standard, a phone number:

• uses only decimal digits
• has a maximum length of 15 digits
• is internationally represented with a leading +
• never starts with 0 in the country code portion

How Talqui Expects Phone Numbers

When a Talqui endpoint expects a phone number, the value should always represent the full international number. In other words, the number should include:

1. the country code
2. the area code when applicable
3. the subscriber number

For Brazil, for example, that means using values like:

• 5511912345678
• 556298800883

When working with Talqui API payloads, use the canonical international number without spaces, hyphens, parentheses, or local formatting. Even though the E.164 notation is commonly shown with a leading +, Talqui request payloads commonly use the same international structure as a digits-only value inside fields such as contactExternalID.

Where This Matters

You should follow this format whenever a Talqui endpoint expects a phone number, especially in fields such as:

• contactExternalID
• contactPhone
• any plugin-specific field that identifies a contact by telephone number

This is important because Talqui uses that normalized value to identify the contact in the target channel and to decide whether a contact already exists or whether it must create one before opening the session.

Examples

Correct

• 5511912345678
• 14155552671
• 442071838750

Avoid

• (11) 91234-5678
• 11 91234 5678
• [phone]
• 0912345678

Validation Guidance

Do not rely only on a simple regular expression to decide whether a number is valid. A string may look correct and still not correspond to a real phone number. The safest approach is to normalize the user input to the international structure expected by Talqui and validate the number with a proper phone-number validation strategy in your own application before sending the request.

Summary

Whenever you send a phone number to Talqui, use the international E.164 numbering logic as the reference model and send the number in its normalized API-friendly form: full international number, digits only, no local mask formatting.