> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/concepts/objects/custom-fields/communication-field-types.md).

# Communication Field Types

{% hint style="success" %}
**Audience:** Administrators, Developers, Solution Architects

**Purpose:** Explains how communication field types capture validated contact data to support messaging, <code class="expression">space.vars.automation</code>, identity matching, and integrations.
{% endhint %}

## Overview

Communication fields are specialized field types designed to store <code class="expression">space.vars.contact</code> information used for messaging, notifications, and outreach. Unlike generic text or numerical fields, communication fields include built-in validation and formatting behaviors that help maintain data quality and support reliable system-driven communication.

These fields support:

* Email messaging and marketing <code class="expression">space.vars.automation</code>
* SMS and phone outreach
* <code class="expression">space.vars.contact</code> verification and identity matching
* Integrations with external third-party messaging and voice systems

Using dedicated communication fields instead of generic `text` fields improves:

* Data consistency
* Deliverability and formatting reliability
* <code class="expression">space.vars.automation</code> accuracy
* Integration compatibility

When communication workflows depend on a field, use the appropriate communication field type rather than freeform text.

{% hint style="warning" %}
**Note**: Avoid storing communication data in text fields, as doing so can compromise deliverability, <code class="expression">space.vars.automation</code>, and identity matching.
{% endhint %}

### Communication Fields vs. Text Fields

If the value powers outreach, validation, identity, or integration, use a communication field.

| Scenario                                                            | Use Communication Field                    | Use Text Field                                                                 |
| ------------------------------------------------------------------- | ------------------------------------------ | ------------------------------------------------------------------------------ |
| Sending emails                                                      | ✅ [Email](#email)                          | ❌ Text                                                                         |
| Sending SMS                                                         | ✅ [Phone Number](#phone-number)            | ❌ Text                                                                         |
| Storing <code class="expression">space.vars.contact</code> identity | ✅ [Email](#email) / [Phone](#phone-number) | ❌ Text                                                                         |
| Capturing descriptive notes                                         | ❌                                          | ✅ [Text / Long Text](/docs/concepts/objects/custom-fields/text-field-types.md) |
| Storing non-validated strings                                       | ❌                                          | ✅ [Text](/docs/concepts/objects/custom-fields/text-field-types.md)             |

***

## Email

The `email` field captures validated email addresses and often functions as a primary <code class="expression">space.vars.contact</code> identifier across communication, <code class="expression">space.vars.automation</code>, and integration workflows.

Only the <code class="expression">space.vars.contact</code>’s email and Team Member’s email fields can be used for system or <code class="expression">space.vars.automation</code> emails.

### Common Use Cases

Use this field when the value will:

* Send marketing or transactional emails
* Trigger email-based <code class="expression">space.vars.automation</code>s
* Serve as a login or unique <code class="expression">space.vars.contact</code> identifier
* Integrate with external email platforms
* Support lookup or upsert operations by email

The platform validates email formatting at the API and UI layers. Invalid values are rejected (for example, “Enter a valid email address.”), protecting <code class="expression">space.vars.automation</code> logic and outreach workflows from malformed data.&#x20;

### Behavior Considerations

The `email` field directly influences identity matching, <code class="expression">space.vars.automation</code> behavior, and integrations.

* Format validation is enforced at the API and UI layers
* Email may function as a unique identifier for <code class="expression">space.vars.contacts</code>
* Uniqueness constraints may apply
* Normalization standards should be defined to ensure consistent matching

Always use an `email` field instead of a `text` field when sorting email addresses. Freeform text does not enforce validation and can lead to <code class="expression">space.vars.automation</code> failures, integration errors, and deliverability issues.

***

## Phone Number

The `phonenumber` field captures validated telephone <code class="expression">space.vars.contact</code> data using standardized formatting to support voice, SMS, and telephony integrations.&#x20;

Only <code class="expression">space.vars.contact</code> and Team Member phone fields can be used for system calling or SMS workflows.

### Common Use Cases

Use this field when the value will:

* Support outbound or inbound calls
* Enable SMS messaging
* Power communication <code class="expression">space.vars.automations</code>
* Integrate with telephony providers
* Support <code class="expression">space.vars.contact</code> verification workflows

Structured phone data improves consistency across <code class="expression">space.vars.entities</code> and reduces formatting errors that can disrupt communication workflows.

### Behavior Considerations

The Phone Number field directly impacts delivery reliability, <code class="expression">space.vars.automation</code> behavior, and telephony integrations.

* **Standardized formatting supports downstream systems**: Consistent formatting improves integration reliability and reduces communication failures.&#x20;
* **API and upload values must use E.164 format:** When creating or updating phone fields via the API or bulk upload, values must be submitted in E.164 format (for example, `+14155552671`). E.164 is an international numbering standard that requires a leading `+`, country code, and full national number, with no spaces or formatting characters. See [E.164](#overview) for more information.
* **International numbers require a defined convention**: Establish requirements for country codes and extensions so integrations do not misinterpret values.
* **Reduce duplicates and ambiguity:** If you capture multiple phone numbers (mobile, work, home), make the “primary” number explicit so <code class="expression">space.vars.automations</code> don’t message the wrong channel.

Always use a `phonenumber` field instead of a `text` field when storing telephone data. Free form text can introduce formatting inconsistencies that disrupt integrations and messaging workflows.

***

## Additional Information

<details>

<summary>Schema Design Best Practices</summary>

### Email

Use an `email` field instead of a `text` field whenever:

* The data represents an actual email address
* Deliverability and formatting matter
* <code class="expression">space.vars.automation</code>s or integrations depend on the value

Avoid storing email addresses in generic text fields. Freeform text does not enforce validation and can lead to:

* Failed automations
* Integration errors
* Poor deliverability
* Inconsistent formatting

Validated email data improves automation reliability and protects downstream communication processes.

### SMS

Use a dedicated `phonenumber` field instead of freeform `text` when:

* The number will be used for calls or SMS
* Downstream systems require structured formatting
* <code class="expression">space.vars.automation</code>s rely on valid phone data

Storing phone numbers in generic text fields can introduce:

* Inconsistent formatting
* International number issues
* Failed SMS or call attempts
* Integration mismatches

Using the `phonenumber` field ensures cleaner data and more reliable communication execution.

</details>

***

## What’s Next

Before implementing schema changes, review the field-specific documentation and API definitions to ensure compatibility with <code class="expression">space.vars.automation</code> and integration requirements <code class="expression">space.vars.Kizen\_company\_name</code> API. To continue designing effective schemas, review our other Field topics:

<details>

<summary>Related Topics</summary>

* [Selection Field Types](/docs/concepts/objects/custom-fields/selection-field-types.md)
* [Date Field Types](/docs/concepts/objects/custom-fields/date-field-types.md)
* [Numerical Field Types](/docs/concepts/objects/custom-fields/numerical-field-types.md)
* [Text Field Types](/docs/concepts/objects/custom-fields/text-field-types.md)
* [Special Field Types](/docs/concepts/objects/custom-fields/special-field-types.md)

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.kizen.com/docs/concepts/objects/custom-fields/communication-field-types.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.