# Create Your First Contact Record | Kizen Basics

## Overview

{% hint style="warning" %}
**Caution:** This setup reflects <code class="expression">space.vars.Kizen\_company\_name</code>'s default configuration. Your administrator may have customized your layout, so columns or navigation may appear differently. Trial accounts may have limited features.
{% endhint %}

In <code class="expression">space.vars.Kizen\_company\_name</code>, a [Contact](/docs/concepts/objects/contacts.md) represents a single person you plan to communicate with through emails, SMS messages, or other outreach. <code class="expression">space.vars.contacts</code> are part of <code class="expression">space.vars.Kizen\_company\_name</code>’s built-in data model and work like a standard <code class="expression">space.vars.entity</code> type.&#x20;

Email acts as the primary identifier for communication purposes, but it is not required. If left blank, it may limit certain lookup or messaging scenarios.

{% hint style="info" %}
**Note:** Storing people in <code class="expression">space.vars.contacts</code> allows you to **message** them through <code class="expression">space.vars.Kizen\_company\_name</code>’s SMS or email <code class="expression">space.vars.automations</code>. You should always store people as <code class="expression">space.vars.contacts</code> even if you don't plan to message them.
{% endhint %}

### Why This Matters

<code class="expression">space.vars.contacts</code> are the standard way to store people in <code class="expression">space.vars.Kizen\_company\_name</code>. Every individual your organization interacts with should be stored as a <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code>, regardless of whether you plan to communicate with them directly.

Using <code class="expression">space.vars.contacts</code> consistently ensures that you:

* Maintain a single, centralized <code class="expression">space.vars.entity</code> for each person
* Enable email and SMS <code class="expression">space.vars.automations</code> when communication is required
* Track activities, interactions, and history tied to that individual
* Keep operational data organized separately within <code class="expression">space.vars.objects</code>

As your data model grows, storing all people in <code class="expression">space.vars.contacts</code> helps maintain a clear structure between individuals and the operational <code class="expression">space.vars.entities</code> associated with them. This makes <code class="expression">space.vars.automations</code>, reporting, and integrations more predictable and easier to manage.

In Contacts, Email acts as the unique identifier for communication purposes — but it is **not required**, and some users may leave it blank which can cause data retrieval issues if trying to use it for anything other than messaging customers.&#x20;

### Before You Begin

Before creating your <code class="expression">space.vars.contacts</code>, you must have the following:

* **Admin** role and permissions to create and edit <code class="expression">space.vars.entities</code>
* A Business workspace in <code class="expression">space.vars.Kizen\_company\_name</code> (See: [Create Your First Business Workspace](/docs/kizen-basics/kizen-in-action/create-your-first-business-workspace-or-kizen-basics.md))

***

## Meet The Reyes Family

To help you understand how <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> work, we’ll follow the Reyes family, who are visiting <code class="expression">space.vars.Theme\_park\_name</code> for the first time. We introduced the following family in the [Kizen Basics in Action](/docs/kizen-basics/kizen-in-action.md) topic.

* **Marcus Reyes:** Planner of the family trip; books tickets online.
* **Elena Reyes:** Manages communication and receives all confirmation emails.
* **Sofia Reyes** *(age 12):* Loves roller coasters; needs a wristband waiver.
* **Caleb Reyes** *(age 8):* Signs up for the Junior Explorer scavenger event.

Marcus purchases tickets through the <code class="expression">space.vars.Theme\_park\_name</code> online form. When he submits the booking, you’ll store him as a <code class="expression">space.vars.contact</code> because <code class="expression">space.vars.Theme\_park\_name</code> needs to send him:

* A confirmation email
* Instructions on the Day of Park entry
* A survey after the visit

Elena, Sofia, and Caleb will also be stored as <code class="expression">space.vars.contacts</code>, even though they do not need to receive emails directly. In this lesson, you will create Marcus’ <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> in <code class="expression">space.vars.Kizen\_company\_name</code>. You will then apply the same steps to create <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> for Elena, Sofia, and Caleb.

***

## Creating Contact Records

{% stepper %}
{% step %}

#### In Kizen, navigate to **Contacts**

Select **Data** > **Contacts** in your navigation.

<div data-with-frame="true"><figure><img src="/files/SrlJcCRjmNdQdSg52omX" alt="" width="563"><figcaption></figcaption></figure></div>

The <code class="expression">space.vars.contacts</code> page appears.
{% endstep %}

{% step %}

#### Select **NEW CONTACT**

<div data-with-frame="true"><figure><img src="/files/siQJ8HaFWA72a3gbbcTk" alt="" width="563"><figcaption></figcaption></figure></div>

The **Add Contact** modal appears.
{% endstep %}

{% step %}

#### Add all Contact details

Fill out the form using our example. Since Marcus submitted an online booking form to purchase tickets, he is the first <code class="expression">space.vars.contact</code> we will add.

<div data-with-frame="true"><figure><img src="/files/xp9tAZLfNYzf1wRgjW1r" alt="" width="375"><figcaption></figcaption></figure></div>

Enter the following:

* **First Name:** Marcus
* **Last Name:** Reyes
* **Email:** <marcus.reyes@example.com>
  * Not a required field, but necessary for email communications and is the unique identifier for the <code class="expression">space.vars.entity</code>.
* **Email Status:** Opt In
  * This is required for messaging as all other statuses will prevent emails from being sent by <code class="expression">space.vars.Kizen\_company\_name</code>.
* **Home Phone:** 123-456-7890
  * Not a required field, but necessary for SMS communications.
* **Custom Fields:** Any fields <code class="expression">space.vars.Theme\_park\_name</code> configured for guest communication.&#x20;

{% hint style="info" %}
**Note:** These are fields that are customizable and can capture any field data you specify. By default Primary Company <code class="expression">space.vars.entity</code> and Additional Company <code class="expression">space.vars.entities</code> are visible. For now we will leave these blank.
{% endhint %}

For this example we will use the following:

* **Title:** Mr.

{% hint style="success" %}
Titles help you label <code class="expression">space.vars.contacts</code> with options like Dr., Mr., Mrs., Ms., or Miss. You can add a new one from the dropdown using **Add Title**.
{% endhint %}

* **Tags:** Leave it Blank

{% hint style="success" %}
Tags let you organize <code class="expression">space.vars.contacts</code> into meaningful groups, like “CloudCon 2021 Signups,” “Drip Campaign 2.1 Beta,” or “Joe’s Hand-Curated Prospects.”
{% endhint %}

* **Birthday:** 12/15/1983
* **Timezone:** America/Chicago
  {% endstep %}

{% step %}

#### Select **SAVE**

After saving Marcus' <code class="expression">space.vars.entity</code>, you will see:

* **All visible fields:** (standard + custom)
* **Timeline:** where future activities and emails will appear
* **Activity Panel:** where staff can log calls, notes, or reminders in the future
* **Agentic Workflows:** which can send Marcus a confirmation email or create a follow-up task once it's set up.
  {% endstep %}
  {% endstepper %}

***

## Applying What You've Learned

With Marcus's <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> complete, it’s time to create <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> for the rest of the family using the same steps. Use the information below to set it up.

| Field             | Elena Reyes               | Sofia Reyes               | Caleb Reyes               |
| ----------------- | ------------------------- | ------------------------- | ------------------------- |
| **First Name**    | Elena                     | Sofia                     | Caleb                     |
| **Last Name**     | Reyes                     | Reyes                     | Reyes                     |
| **Email**         | <reyes.elena@yopmail.com> | <sofia.reyes@yopmail.com> | <caleb.reyes@yopmail.com> |
| **Email Status**  | Opt In                    | Opt In                    | Opt In                    |
| **Home Phone**    | 234-567-8911              | —                         | —                         |
| **Title**         | Mrs.                      | —                         | —                         |
| **Tags**          | —                         | —                         | —                         |
| **Birthday**      | 03/08/1986                | 07/14/2012                | 09/02/2016                |
| **Timezone**      | US/Central                | US/Central                | US/Central                |
| **Custom Fields** | Blank                     | Blank                     | Blank                     |

***

## Editing Your Viewable Columns

<div data-with-frame="true"><figure><img src="/files/pdd9zjTpbjbkpjeohNeo" alt="" width="563"><figcaption></figcaption></figure></div>

As you can see, Marcus Reyes has now been added as <code class="expression">space.vars.contacts</code> in <code class="expression">space.vars.Kizen\_company\_name</code>. By default the following columns are viewable:

* Full Name
* Email
* Mobile phone
* Titles
* Tags

Next, we are going to modify the columns to display the fields we want and in what order.

{% stepper %}
{% step %}

#### Click on **Edit Columns**

<div data-with-frame="true"><figure><img src="/files/rfzXbHT0AM2wGA17mxtV" alt=""><figcaption></figcaption></figure></div>

You will be taken to the Edit My Columns screen
{% endstep %}

{% step %}

#### Move your chosen columns into the **Active Table Columns**

For this example we will move:

* Home phone
* Birthday
* Email Status
* Timezone

We'll also remove the following by placing them into **Available Columns**:

* Mobile phone
* Tags

You can also reorder your columns on the table by placing them in the order you would like for them to display in **Active Table Columns**. In this example you can see the added and removed columns, and the new order.

<div data-with-frame="true"><figure><img src="/files/on0GIMuoNWcjsiWxgltT" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Select **SAVE**

This will save your column choices and take you back to the <code class="expression">space.vars.contacts</code> page.

<div data-with-frame="true"><figure><img src="/files/XHIDfdNKuD2VkI2lbOtW" alt="" width="563"><figcaption></figcaption></figure></div>

Now you can see the <code class="expression">space.vars.contacts</code> page display with your new column order.
{% endstep %}
{% endstepper %}

***

## How This Fits Into Agentic Workflows

Now that you’ve added Marcus Reyes and customized your <code class="expression">space.vars.contact</code> table view, the next step is to add the rest of the Reyes family as <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code>.

Even if Elena, Sofia, and Caleb are not the recipients of emails or SMS messages, they should still be stored as <code class="expression">space.vars.contacts</code> because they represent real people tied to park operations and guest history. In <code class="expression">space.vars.Kizen\_company\_name</code>, a <code class="expression">space.vars.contact</code> can exist without being used for messaging.

As you add Elena, Sofia, and Caleb Reyes:

* Create one <code class="expression">space.vars.contact</code> per person
* Leave Email blank for family members who should not receive communications
* Set messaging-related fields (such as Email Status) according to your business rules
* Use consistent names and information (like phone number or address) so the family can be associated correctly in later steps

When you finish, you should have four <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code>:

* Marcus Reyes (primary communication <code class="expression">space.vars.contact</code> with an email listed)
* Elena Reyes
* Sofia Reyes
* Caleb Reyes

<div data-with-frame="true"><figure><img src="/files/mIcK6XL5Er0opOOBOyoO" alt=""><figcaption></figcaption></figure></div>

In the next lesson, you’ll start building the data model that connects these <code class="expression">space.vars.contacts</code> to operational records such as tickets and <code class="expression">space.vars.activities</code>.

***

## How This Fits Into Agentic Workflows

As soon as Marcus and his family becomes a <code class="expression">space.vars.contact</code>, <code class="expression">space.vars.Kizen\_company\_name</code> can:

* Send a confirmation email
* Trigger a welcome SMS
* Create a pre-visit task for staff
* Add Marcus or his family to an email drip sequence
* Kick off <code class="expression">space.vars.workflows</code> tied to <code class="expression">space.vars.contact</code> creation

Adding people to <code class="expression">space.vars.contacts</code> also allows you to later build <code class="expression">space.vars.automations</code> such as:

* Sending reminders
* Assigning <code class="expression">space.vars.activities</code>
* Creating Scheduled <code class="expression">space.vars.activities</code>
* Tracking guest history
* Building <code class="expression">space.vars.dashboards</code> of guest engagement

***

## Contact Capabilities By Role

{% columns %}
{% column %}

#### **Admins**

* Configure <code class="expression">space.vars.contact</code> fields
* Manage permissions
* Set up <code class="expression">space.vars.workflows</code> and <code class="expression">space.vars.automations</code> connected to <code class="expression">space.vars.contacts</code>
  {% endcolumn %}

{% column %}

#### **Technical Builders**

* Use [Objects APIs](/docs/concepts/objects/object-apis.md) to create or update <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> programmatically
* Configure inbound webhooks when <code class="expression">space.vars.contacts</code> originate from external forms or systems
* Map incoming data to the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.object</code> through ETL or integration tools
  {% endcolumn %}
  {% endcolumns %}

***

## Tying It Back Into Your Industry

While the Reyes family example demonstrates how <code class="expression">space.vars.contacts</code> work in a theme park scenario, the same concepts apply across industries. A <code class="expression">space.vars.contact</code> is simply a <code class="expression">space.vars.entity</code> representing a person, whether you communicate with them directly through email, SMS, or automated <code class="expression">space.vars.workflows</code>, or not.

How you structure your [Contact Data Model](/docs/concepts/objects/contacts/contacts-data-model.md) determines how easily your organization can manage communication, track interactions, and automate processes as your system grows.

Below are examples of how <code class="expression">space.vars.contacts</code> function in three common industries supported by <code class="expression">space.vars.Kizen\_company\_name</code>.

{% tabs %}
{% tab title="Insurance" %}
In insurance, a <code class="expression">space.vars.contact</code> often represents a policyholder, applicant, or agent who needs to receive quotes, renewal notices, eligibility updates, or claims communications.

Example <code class="expression">space.vars.contact</code> <code class="expression">space.vars.automations</code>:

* Email a quote packet after an application is submitted
* Notify an agent when underwriting status changes
* Send renewal reminders or required-document checklists
* Trigger tasks for claims adjusters or verification teams

Use <code class="expression">space.vars.objects</code> to store structured data like applications, policies, beneficiaries, claims, and supporting documents, while <code class="expression">space.vars.contacts</code> remain the communication endpoint.
{% endtab %}

{% tab title="Healthcare" %}
In healthcare, a <code class="expression">space.vars.contact</code> often represents a patient, caregiver, or responsible party who must receive appointment reminders, care instructions, follow-up messages, or portal notifications.

Example <code class="expression">space.vars.contact</code> <code class="expression">space.vars.automations</code>:

* Send pre-visit instructions when a patient books an appointment
* Trigger SMS reminders 24 hours before a procedure
* Log follow-up calls or care-team activities directly on the <code class="expression">space.vars.contact</code> timeline
* Send discharge instructions or satisfaction surveys automatically

Use <code class="expression">space.vars.contacts</code> when communication is required. Use <code class="expression">space.vars.objects</code> for clinical <code class="expression">space.vars.workflows</code> like care plans, intake forms, encounters, or orders that you don’t message directly.
{% endtab %}

{% tab title="Financial Services" %}
In financial services, a <code class="expression">space.vars.contact</code> typically represents a client, borrower, investor, or account holder who needs time-sensitive updates or required disclosures.

Example <code class="expression">space.vars.contact</code> <code class="expression">space.vars.automations</code>:

* Send onboarding emails after a new account is created
* Trigger reminders for outstanding documentation
* Log advisor calls or follow-up tasks
* Send periodic statements, alerts, or investment updates

<code class="expression">space.vars.objects</code> store operational data such as accounts, transactions, loans, risk reviews, or KYC/AML <code class="expression">space.vars.entities</code>, while <code class="expression">space.vars.contacts</code> manage all direct communication.
{% endtab %}
{% endtabs %}

***

## What’s Next?

Now you’ll begin building the foundation of <code class="expression">space.vars.Kizen\_company\_name</code>’s data model. In [Create Your First Object](/docs/kizen-basics/kizen-in-action/create-your-first-object-or-kizen-basics.md), you will first create a Tickets <code class="expression">space.vars.object</code> to track purchases like Marcus’s park tickets. You will then create Concessions and Ride Waiver <code class="expression">space.vars.objects</code> to track food and merchandise purchases and store ride waiver information for guests.


---

# Agent Instructions: 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/kizen-basics/kizen-in-action/create-your-first-contact-record-or-kizen-basics.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.