> 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/kizen-basics/kizen-in-action/update-a-contact-record-or-kizen-basics.md).
# Update A Contact Record | Kizen Basics
Learn how to modify a Contact Record by adding Custom Fields so you can connect guest Activity to operational events and power timely Agentic Workflows.
## Overview
While guest services helped Marcus recover Sofia’s backpack, the staff member reviewing the request noticed something missing from the space.vars.contact space.vars.entity.
The **Lost Item Request** is linked to Marcus’s space.vars.contact space.vars.entity, but the **visit date** for the Reyes family is missing. Without that information, staff cannot easily confirm when the family entered the park or trigger future space.vars.automations tied to guest visits.
To correct this, the staff member updates Marcus’s space.vars.contact space.vars.entity to include the **Visit Date**.
### Why This Step Matters
Capturing the **Visit Date** allows Flywheel Adventure Park to connect operational events, such as lost item requests, to the guest’s actual park visit.
This information will also be used in other tutorials when creating space.vars.automations that respond to guest activity.
For example, space.vars.automations could:
* Send reminders before a guest’s visit
* Assign operational tasks to park staff
* Send follow-up messages after a visit
Accurate space.vars.entity data ensures that these space.vars.automations run at the correct time.
### Before You Begin
Before updating Marcus’s space.vars.contact space.vars.entity, make sure you have:
* Permission to edit space.vars.contacts and create space.vars.fields
* Access to **Data** > **Contacts**
* A space.vars.contact space.vars.entity for Marcus already created (see [Create Your First Record](/docs/kizen-basics/kizen-in-action/create-your-first-record-or-kizen-basics.md))
***
## Update a Contact Record
{% stepper %}
{% step %}
#### Open the Contact Columns Editor
1. Navigate to **Data** > **Contacts**.
2. Locate the **Edit Columns** icon on the right side of the table header and select **Edit Columns**.
This opens the **Edit My Columns** configuration screen.
{% endstep %}
{% step %}
#### Open Object Field Settings
1. In the **Edit My Columns** screen, scroll to the bottom of the **Available Columns** section.
2. Select **Customize Fields**.
This opens the **Editing Object – Contacts** configuration page
{% endstep %}
{% step %}
#### Create the Visit Date Field
Select **+ Add New Field**.
In **Field Settings**, enter the following:
* **Field Name:** Visit Date
* **Category:** Contact Info
* **Description:** Visit Date for Guests
* Under **Choose Field Type**, select **Date**.
* Select **SAVE**.
The **Visit Date** field is now added to the space.vars.contact space.vars.object. Select **BACK TO COLUMNS**.
{% endstep %}
{% step %}
#### Add the Field to the Contact Table
After creating the field, it must be added to the visible table columns.
1. In **Available Columns**, locate **Visit Date** and drag it into the **Active Table Columns** section.
3. Position the field where you want it to appear in the table, and drop it. There is a **Column Preview** that indicates how columns will be displayed.
4. Select **SAVE**.
{% endstep %}
{% endstepper %}
If you go back to the **Contacts** page, the **Visit Date** column now appears in the **Contacts table**, allowing staff to view and manage guest visit dates directly from the contact list.
Select the Visit Date for each Contact in the Reyes family and specify the date: 6/15/2026. The information can later be used in space.vars.automations or reporting, for example to identify guests who visited on the same day an item was reported lost.
***
## What’s Next
Next, you can create an space.vars.automation that moves requests through stages. For example, when a request moves from **Reported** to **Searching**, an space.vars.automation could assign the task to the appropriate team or notify staff responsible for the ride area where the item may have been lost.
Learn how to create this process in the [Create Your First Agentic Workflow](/docs/kizen-basics/kizen-in-action/create-your-first-agentic-workflow-or-kizen-basics.md) topic.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://developer.kizen.com/docs/kizen-basics/kizen-in-action/update-a-contact-record-or-kizen-basics.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
