Log Your Activity | Kizen Basics
Overview
Caution: This setup reflects Kizen's default configuration. Your administrator may have customized your layout, so columns or navigation may appear differently. Trial accounts may have limited features.
When an interaction has already happened, log it as an Activity. Logged Activities capture real interactions—such as purchases, conversations, or questions—and place them on the Timeline 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 Activity. 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 Activities, these details exist only in the moment. By capturing them on the Timeline, Kizen helps teams understand, share, and improve the guest experience across the entire operation.
Before You Begin
Before logging Activities, make sure the following are in place:
You’ve completed Scheduling Your Activities & Timelines
The Reyes family Contacts and Guests have already been created
An Activity exists for Concessions Purchase
A Concession Object exists
You have permission to log Activities on Contact Records
If these items are set up, you’re ready to begin logging real guest interactions.
Logging An Activity
Fill out Log Activity fields
On the Log Activity's panel you can see various fields.
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.
Now you should see that the logged Activity appear on Marcus’s Timeline with the selected date and time, assigned staff member, Activity details, related Records, and any notes.
It will look like this:
Apply What You've Learned
Now that you’ve logged one Activity, apply what you’ve learned. Log another Activity using the same steps. This time, log the Activity 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 Activity should appear on the Timeline like this:
How This Fits Into Agentic Workflows
Logged Activities do more than Record history. They become triggers and data inputs for Workflows and Agentic Workflows across Kizen.
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 Activity is connected to Contacts, Tickets, and staff members, Workflows can respond to real interactions as they happen.
When Activities are logged, you can use them to:
Trigger Agentic Workflows based on Activity type, completion status, or timing
Update related Records, such as Tickets or Objects
Route information to the right teams, such as notifying Guest Services about allergy-related notes
Power reporting and Dashboards with accurate, real-world interaction data
By logging Activities consistently, Timelines become actionable. Instead of static Records, they drive Agentic Workflow, insights, and coordinated responses across teams.
Logging Activities Capabilities By Role
Admins
Configure Activity types that can be logged, including required fields and associations
Define which Objects (Contacts, Guests, Tickets, Objects) appear on logged Activities
Control permissions for who can log, edit, or complete Activities
Ensure logged Activities display correctly on Timelines and in reports
Maintain consistency in how interactions, purchases, and notes are recorded across teams
Technical Builders
Log Activities programmatically using the API
Trigger Workflows and Agentic Workflows based on logged Activity events
Enrich logged Activities with data from external systems or integrations
Update related Records automatically when Activities are logged
Use logged Activity data as inputs for reporting, Dashboards, and downstream processes
Tying It Back Into Your Industry
In the Flywheel Adventure Park 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 Timeline 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.
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 Flywheel Adventure Park, logged insurance Activities capture details that support compliance, continuity of service, and accurate reporting.
At Flywheel Adventure Park, logging captures what happened during a guest visit. In healthcare, logging Activities 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.
The fried dough interaction represents a completed moment with meaningful context. In financial services, Logged Activities 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 Activities consistently, financial teams preserve decision context, support regulatory accountability, and maintain accurate client Timelines.
What's Next?
Next, we’ll cover Reporting in Kizen, where you’ll learn how to build, customize, and analyze reports to gain visibility into your data, Activity performance, and Agentic Workflow outcomes.
Last updated
Was this helpful?