# Log Your Activity | 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 %}

When an interaction has already happened, log it as an <code class="expression">space.vars.activity</code>. Logged <code class="expression">space.vars.activities</code> capture real interactions—such as purchases, conversations, or questions—and place them on the <code class="expression">space.vars.timeline</code> so teams can see what happened and when.

During their visit, Marcus stops at the snack stand to buy fried dough for his kids. While ordering, he chats with a staff member and asks whether the fried dough contains nuts, since his son Caleb has a nut allergy.

This interaction should be logged as an <code class="expression">space.vars.activity</code>. Logging it records where the family stopped, what they purchased, and important context like allergy concerns. Over time, these entries create a shared, accurate view of the guest experience across teams.

### Why This Matters

Small interactions often carry important context. In the Reyes family’s visit, a simple snack purchase also included a question about nut allergies. When that interaction is logged, it becomes more than just a transaction.

Logged Activities help teams:

* See purchases alongside guest questions or concerns
* Anticipate needs before issues arise, such as allergies or accessibility requests
* Maintain continuity as guests interact with different staff members or departments
* Turn everyday moments into data that supports reporting, staffing, and operational decisions

Without logged <code class="expression">space.vars.activities</code>, these details exist only in the moment. By capturing them on the <code class="expression">space.vars.timeline</code>, <code class="expression">space.vars.Kizen\_company\_name</code> helps teams understand, share, and improve the guest experience across the entire operation.

### Before You Begin

Before logging <code class="expression">space.vars.activities</code>, make sure the following are in place:

* You’ve completed [Scheduling Your Activities & Timelines](/docs/kizen-basics/kizen-in-action/scheduling-your-activity-and-timelines-or-kizen-in-action.md)
* The **Reyes family Contacts and Guests** have already been created
* An <code class="expression">space.vars.activity</code> exists for **Concessions Purchase**
* A **Concession** <code class="expression">space.vars.object</code> exists
* You have permission to log <code class="expression">space.vars.activities</code> on <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code>

If these items are set up, you’re ready to begin logging real guest interactions.

***

## Logging An Activity

{% stepper %}
{% step %}

#### Go to a Contact Record and select LOG ACTIVITY

Assuming you're still on Marcus Reyes's <code class="expression">space.vars.contact</code> page, go to the Notes panel. From there, select **LOG ACTIVITY**. The dropdown will give you various <code class="expression">space.vars.activities</code> to use. Select **Concessions Purchase**.

<div align="left" data-with-frame="true"><figure><img src="/files/sf597S2W5FXvuPCmhSSU" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Fill out Log Activity fields

On the Log <code class="expression">space.vars.activity</code>'s panel you can see various fields.

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

Complete the **Concession Purchases Activity** using the details below.

**Verify Associations**

* **Contacts:** Marcus Reyes
* **Concessions:** In the drop down, select **Fried Dough**.
* **Lost Item Requests:** *Blank*
* **Ride Waivers:** *Blank*
* **Tickets:** Select **Marcus Reyes - Flywheel Ticket**

In the Notes section, Write:  Marcus Reyes purchases a Fried Dough for his two kids.
{% endstep %}

{% step %}

#### Select **COMPLETE**

{% endstep %}
{% endstepper %}

Now you should see that the logged <code class="expression">space.vars.activity</code> appear on Marcus’s <code class="expression">space.vars.timeline</code> with the selected date and time, assigned staff member, <code class="expression">space.vars.activity</code> details, related <code class="expression">space.vars.entities</code>, and any notes.

It will look like this:

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

***

## Apply What You've Learned

Now that you’ve logged one <code class="expression">space.vars.activity</code>, apply what you’ve learned. Log another <code class="expression">space.vars.activity</code> using the same steps. This time, log the <code class="expression">space.vars.activity</code> of Marcus buying a soda for his wife Elena.

You can complete **Concession Purchases Activity** using the details below:

**Verify Associations**

* **Contacts:** Marcus Reyes
* **Concessions:** Soda
* **Lost Item Requests:** Leave blank
* **Ride Waivers:** Leave blank
* **Tickets:** Marcus Reyes - Flywheel Ticket

**Complete Activity**

* **Notes:** Marcus purchases a soda for his wife Elena.

When you're finished, your logged <code class="expression">space.vars.activity</code> should appear on the <code class="expression">space.vars.timeline</code> like this:

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

***

## How This Fits Into Agentic Workflows

Logged <code class="expression">space.vars.activities</code> do more than <code class="expression">space.vars.entity</code> history. They become triggers and data inputs for <code class="expression">space.vars.workflows</code> and <code class="expression">space.vars.automations</code> across <code class="expression">space.vars.Kizen\_company\_name</code>.

In the Reyes family example, logging a fried dough purchase can automatically initiate follow-up actions, such as updating inventory levels, flagging allergy-related notes, or contributing to concession sales reports. Because each <code class="expression">space.vars.activity</code> is connected to <code class="expression">space.vars.contacts</code>, Tickets, and staff members, <code class="expression">space.vars.workflows</code> can respond to real interactions as they happen.

When <code class="expression">space.vars.activities</code> are logged, you can use them to:

* Trigger <code class="expression">space.vars.automations</code> based on <code class="expression">space.vars.activity</code> type, completion status, or timing
* Update related <code class="expression">space.vars.entities</code>, such as Tickets or <code class="expression">space.vars.objects</code>
* Route information to the right teams, such as notifying Guest Services about allergy-related notes
* Power reporting and <code class="expression">space.vars.dashboards</code> with accurate, real-world interaction data

By logging Activities consistently, Timelines become actionable. Instead of static <code class="expression">space.vars.entities</code>, they drive <code class="expression">space.vars.automation</code>, insights, and coordinated responses across teams.

***

## Logging Activities Capabilities By Role

{% columns %}
{% column %}

#### Admins

* Configure <code class="expression">space.vars.activity</code> types that can be logged, including required fields and associations
* Define which <code class="expression">space.vars.objects</code> (<code class="expression">space.vars.contacts</code>, Guests, Tickets, <code class="expression">space.vars.objects</code>) appear on logged <code class="expression">space.vars.activities</code>
* Control permissions for who can log, edit, or complete <code class="expression">space.vars.activities</code>
* Ensure logged <code class="expression">space.vars.activities</code> display correctly on <code class="expression">space.vars.timelines</code> and in reports
* Maintain consistency in how interactions, purchases, and notes are recorded across teams
  {% endcolumn %}

{% column %}

#### Technical Builders

* Log <code class="expression">space.vars.activities</code> programmatically using the API
* Trigger <code class="expression">space.vars.workflows</code> and <code class="expression">space.vars.automations</code> based on logged <code class="expression">space.vars.activity</code> events
* Enrich logged <code class="expression">space.vars.activities</code> with data from external systems or integrations
* Update related <code class="expression">space.vars.entities</code> automatically when <code class="expression">space.vars.activities</code> are logged
* Use logged <code class="expression">space.vars.activity</code> data as inputs for reporting, <code class="expression">space.vars.dashboards</code>, and downstream processes
  {% endcolumn %}
  {% endcolumns %}

***

## Tying It Back Into Your Industry

In the <code class="expression">space.vars.Theme\_park\_name</code> example, logging the fried dough purchase captures more than a completed transaction. It captures who was involved, what happened, when it happened, and any important context, such as a guest’s allergy-related question. That logged interaction becomes part of the family’s <code class="expression">space.vars.timeline</code> and informs future decisions.

The same logging pattern applies across industries where completed interactions, conversations, and outcomes need to be preserved and understood in context.

{% tabs %}
{% tab title="Insurance" %}
Logging a fried dough purchase is similar to logging completed client interactions in insurance.

Examples include:

* A call where a policyholder asks about coverage limitations
* A completed claim discussion with notes on next steps
* A client question that signals potential risk, coverage gaps, or follow-up needs

Just as the allergy question adds important context at <code class="expression">space.vars.Theme\_park\_name</code>, logged insurance Activities capture details that support compliance, continuity of service, and accurate reporting.
{% endtab %}

{% tab title="Healthcare" %}
At <code class="expression">space.vars.Theme\_park\_name</code>, logging captures what happened during a guest visit. In healthcare, logging <code class="expression">space.vars.activities</code> documents completed care interactions and patient communication.

Examples include:

* A completed appointment with provider notes
* A patient question about medication, allergies, or side effects
* A follow-up conversation after a procedure or lab result

Logging these interactions ensures care teams share the same patient history and can make informed decisions over time.
{% endtab %}

{% tab title="Financial Services" %}
The fried dough interaction represents a completed moment with meaningful context. In financial services, Logged <code class="expression">space.vars.activities</code> capture completed client touchpoints and decision history.

Examples include:

* A client meeting discussing portfolio changes
* A completed compliance or suitability review
* A conversation revealing new financial goals or concerns

By logging <code class="expression">space.vars.activities</code> consistently, financial teams preserve decision context, support regulatory accountability, and maintain accurate client <code class="expression">space.vars.timelines</code>.
{% endtab %}
{% endtabs %}

***

## What's Next?

Next, we’ll cover [Reporting in Kizen](/docs/kizen-basics/kizen-in-action/reporting-in-kizen-or-kizen-in-action.md), where you’ll learn how to build, customize, and analyze reports to gain visibility into your data, <code class="expression">space.vars.activity</code> performance, and <code class="expression">space.vars.automation</code> outcomes.


---

# 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/tracking-your-activity-in-timelines-or-kizen-in-action.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.