# Schedule 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 %}

A day at <code class="expression">space.vars.Theme\_park\_name</code> is full of interactions—families calling to confirm arrival times, guests checking in at the gate, safety briefings before rides, and follow-up messages after their visit. For the Reyes family, this includes confirming Sofia and Caleb’s ride waivers and making sure Marcus receives the right reminders before they arrive.

Some interactions happen *in the moment* and need to be **logged**. Others must be planned ahead of time and need to be **scheduled** to ensure the day runs smoothly.

You should create a Scheduled <code class="expression">space.vars.activity</code> when an interaction hasn’t happened yet, such as confirming ride waivers before a visit. When Marcus Reyes purchased tickets for his children, Sofia and Caleb, <code class="expression">space.vars.Theme\_park\_name</code> schedules a **Ride Waiver Confirmation** <code class="expression">space.vars.activity</code>. This ensures Guest Services can verify waiver completion and prepare wristbands ahead of time, allowing the kids to head straight to the rides upon arrival.

A Scheduled <code class="expression">space.vars.activity</code> like this typically includes details such as:

* **Type:** Ride Waiver Confirmation
* **Date & Time:** Morning of the visit
* **Assigned To:** Guest Services staff member Jacob Mulligan
* **Notes:** “Confirm both children’s waivers. Prepare wristbands to speed up ride access. Link to ticket records.”
* **Contacts:** Sofia and Caleb Reyes

### **Why This Matters**

Keeping <code class="expression">space.vars.activities</code> up to date ensures that <code class="expression">space.vars.Theme\_park\_name</code> staff always know:

* What happened
* What’s planned
* Who handled each touchpoint
* Whether follow-ups are still pending

When <code class="expression">space.vars.activities</code> are logged and scheduled correctly, the guest experience feels seamless, even on the busiest weekends. This guide walks through how to schedule an <code class="expression">space.vars.activity</code> using the Reyes family’s visit as a simple, day-in-the-life example.

### Before You Begin

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

* The Contact record exists for Marcus Reyes
* Sofia Reyes Ride Waiver and Caleb Reyes Ride Waiver <code class="expression">space.vars.entities</code> have been created
* The <code class="expression">space.vars.activity</code> type you plan to schedule (such as Ride Waiver Confirmation) is available
* The assigned team member exists in <code class="expression">space.vars.Kizen\_company\_name</code> and has the appropriate permissions
* You have permission to schedule <code class="expression">space.vars.activities</code> and send notifications

Having these items ready ensures <code class="expression">space.vars.activities</code> can be scheduled, assigned, and connected correctly to <code class="expression">space.vars.timelines</code> and <code class="expression">space.vars.workflows</code>.

***

## Scheduling an Activity

{% stepper %}
{% step %}

#### Navigate to **Contacts**

&#x20;From the top navigation, select **Data** > **Contacts**.

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

{% step %}

#### Select the Contact Record

On the **Contacts** page, select Marcus Reyes, as he is the person needing the Scheduled <code class="expression">space.vars.activity</code>.
{% endstep %}

{% step %}

#### Schedule an <code class="expression">space.vars.activity</code> on your Contact Record

On the Action panel in Marcus's <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> select **SCHEDULE ACTIVITY**.&#x20;

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

A Schedule <code class="expression">space.vars.activity</code> modal appears.
{% endstep %}

{% step %}

#### Choose the Activity and fill out the fields

On the Schedule <code class="expression">space.vars.activities</code> modal, you can choose your <code class="expression">space.vars.activity</code> and fill out various fields.

Select **Ride Waiver Confirmation** from the Choose <code class="expression">space.vars.activity</code> dropdown (the topmost field).

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

{% step %}

#### Assign a Team Member

Assign the <code class="expression">space.vars.activity</code> to the team member. Under **Assign Team Member**, be sure to choose via a dropdown Jacob Mulligan, your trusty guest service staffer.&#x20;

{% hint style="info" %}
**Note**: Jacob Mulligan should be created for this step. If you don't see him, please read our [Configure Your Business](/docs/kizen-basics/kizen-in-action/configure-your-business-settings-or-kizen-basics.md) page.
{% endhint %}
{% endstep %}

{% step %}

#### Set Date and Time

* **Due Date:** Day of the visit (for our purposes, set it to two days ahead of the present date).
* **Time:** Morning (use 9:00 AM)
* **Why?** This ensures staff prepare waivers and wristbands before the family arrives.
  {% endstep %}

{% step %}

#### Add a Note

Add a note regarding the current Scheduled <code class="expression">space.vars.activity</code>: “Confirm both children’s waivers. Prepare wristbands to speed up ride access. Link to ticket <code class="expression">space.vars.entities</code>.”
{% endstep %}

{% step %}

#### Set your Associations

&#x20;Set associations for this Scheduled <code class="expression">space.vars.activity</code>.

* **Contacts** Contacts field is the person who needs to fill out this ride waiver (in this case, Marcus Reyes)
* **Concession:** *Blank*
* **Lost Item Requests:** *Blank*
* **Ride Waivers:** Sofia Reyes Ride Waiver
* **Tickets field:** This is connecting the waiver to a specific ticket (in this case, Marcus's purchase of Sofia's ticket). In the Tickets dropdown, select **Marcus Reyes - Flywheel Ticket**.

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

{% step %}

#### Add Notifications

Select **+ADD NOTIFICATION**.

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

You'll want to remind Marcus of the waiver form is due a couple times before he comes with the family to <code class="expression">space.vars.Theme\_park\_name</code>. So you're going to create two notifications

* You can choose whether or not to send a text or an email. For our purposes, leave it as an email.
* In the dropdown where you see **Minute(s)**, change it to **Days(s)**. These indicate the timelines before the Activity is due. We want to give Marcus some time to sign the waivers!
* Set the first notification to **1 Day** and the second to **4 hours**.
  {% endstep %}

{% step %}

#### Select **SCHEDULE** to save

{% endstep %}
{% endstepper %}

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

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

***

## Apply What You've Learned

Now that you’ve scheduled one <code class="expression">space.vars.activity</code>, apply what you’ve learned. Schedule another <code class="expression">space.vars.activity</code> using the same steps and the Ride Waiver <code class="expression">space.vars.object</code>. This time, create the <code class="expression">space.vars.activity</code> for **Caleb’s waiver** instead of Sofia’s.

Use the information below to set it up.

**Activity Settings**

* **Activity:** Ride Waiver Submissions
* **Assignment Type:** Team Member
* **Assign Team Member:** Jacob Mulligan
* **Due Date:** Two days from today (visit date)
* **Time:** 9:00 AM
* **Notes:** Confirm both children’s waivers. Prepare wristbands to speed up ride access. Link to ticket <code class="expression">space.vars.entities</code>.

**Associations**

* **Contacts:** Marcus Reyes
* **Concession:** *Blank*
* **Lost Item Requests:** Leave blank
* **Ride Waivers:** Caleb Reyes Wide Waiver
* **Tickets:** Marcus Reyes - Flywheel Ticket

**Notifications**

Create two notifications:

* **Notification 1:** Send email **1 day before** activity is due
* **Notification 2:** Send email **4 hours before** activity is due

When you've finished, this should be present on Marcus Reyes's <code class="expression">space.vars.timeline</code>:

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

***

## How This Fits Into Agentic Workflows

Scheduled <code class="expression">space.vars.activities</code> represent planned touch points and are central to proactive <code class="expression">space.vars.automations</code> in <code class="expression">space.vars.Kizen\_company\_name</code>. In the Reyes family example, scheduling Ride Waiver Confirmation <code class="expression">space.vars.activities</code> ensures required steps happen before the family arrives. Once scheduled, these <code class="expression">space.vars.activities</code> can trigger reminders, assign tasks to staff, and prepare systems for the visit—helping teams address needs in advance rather than at check-in.

Scheduled <code class="expression">space.vars.activities</code> can be used to:

* Send reminders or notifications before a visit
* Assign preparation tasks based on timing or ticket type
* Ensure required steps, like waiver completion, aren’t missed
* Feed planning data into staffing and operational reports

By Scheduling <code class="expression">space.vars.activities</code> consistently, teams move from reactive to proactive. Guests receive timely communication, staff know what’s coming, and <code class="expression">space.vars.automations</code> handle preparation ahead of time. When the work is completed and logged, the <code class="expression">space.vars.timeline</code> closes the loop between planning and execution.

***

## Scheduling Activities Capabilities By Role

{% columns %}
{% column %}

#### Admins

* Create and manage <code class="expression">space.vars.activity</code> types used for scheduling
* Configure required fields, defaults, and associations
* Control permissions for scheduling <code class="expression">space.vars.activities</code> and sending notifications
* Define standard scheduling patterns for common <code class="expression">space.vars.workflows</code>
* Ensure scheduled <code class="expression">space.vars.activities</code> appear correctly on <code class="expression">space.vars.timelines</code> and reports
  {% endcolumn %}

{% column %}

#### Technical Builders

* Automatically schedule <code class="expression">space.vars.activities</code> based on triggers or conditions
* Integrate <code class="expression">space.vars.activity</code> scheduling into <code class="expression">space.vars.automations</code>
* Schedule <code class="expression">space.vars.activities</code> programmatically using the API
* Configure notifications and follow-up actions
* Connect scheduled <code class="expression">space.vars.activities</code> to downstream systems and reporting
  {% endcolumn %}
  {% endcolumns %}

***

## Tying It Back Into Your Industry

In the <code class="expression">space.vars.Theme\_park\_name</code> example, scheduling a Ride Waiver Confirmation ensures required steps are completed before the family arrives. The same scheduling pattern applies across industries where preparation, compliance, or follow-up must happen before a key event.

{% tabs %}
{% tab title="Insurance" %}
Scheduling a Ride Waiver Confirmation is similar to scheduling policy-related follow-ups in insurance.

For example:

* A policy renewal reminder scheduled before expiration
* A document collection task scheduled after a quote is issued
* A compliance review scheduled before coverage becomes active

Just as Guest Services prepares wristbands ahead of time, insurance teams prepare documentation and approvals before a policy milestone.
{% endtab %}

{% tab title="Healthcare" %}
At <code class="expression">space.vars.Theme\_park\_name</code>, waiver confirmation happens before the visit. In healthcare, Scheduled <code class="expression">space.vars.activities</code> support patient readiness before appointments or procedures.

For example:

* Appointment reminders scheduled before a visit
* Insurance verification tasks scheduled ahead of check-in
* Pre-procedure instructions scheduled for patients

In both cases, scheduling ensures staff and patients are prepared before arrival.
{% endtab %}

{% tab title="Financial Services" %}
The Ride Waiver Confirmation <code class="expression">space.vars.activity</code> parallels scheduled client touchpoints in financial services.

For example:

* Annual review meetings scheduled in advance
* Follow-up tasks scheduled after account changes
* Compliance check-ins scheduled around key financial events

Just as <code class="expression">space.vars.Theme\_park\_name</code> schedules preparation before a visit, financial teams schedule <code class="expression">space.vars.activities</code> to ensure readiness before client decisions or regulatory deadlines.
{% endtab %}
{% endtabs %}

***

## **What’s Next?**

Next, you’ll learn about [Logging your Activities](/docs/kizen-basics/kizen-in-action/tracking-your-activity-in-timelines-or-kizen-in-action.md), including how <code class="expression">space.vars.activity</code> <code class="expression">space.vars.entities</code> appear, update, and stay connected to your data.


---

# 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/scheduling-your-activity-and-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.