Glossary

Unified Data Access — Glossary

Product & Platform

AI Supervisor
Zowie's monitoring and performance interface for reviewing AI Agent interactions. The Supervisor tables in the shared dataset expose the same data visible in this UI.

Inbox
Zowie's human agent workspace for managing support conversations. The source of Inbox tables in the shared dataset.

GenAI
Zowie's generative AI layer powering the AI Agent's reasoning and responses. The source of AI Agent session events — messages, tool calls, and reasoning steps — in the Events table.

CRM
Zowie's customer data service, which stores end-user profiles. The source of the Users table.


Data Model Concepts

Unified data model
The normalized data hierarchy (Users → Tickets → Interactions → Events) that consolidates data from across Zowie's product services into a single consistent schema.

Environment ID (environment_id)
A unique identifier for a customer's Zowie account instance. Present as a primary identifier on all tables and used as a clustering key for query performance. All data in a linked dataset belongs to a single environment.

Chatbot ID (owner_user_id)
Unique identifier of the chatbot configuration instance that handles interactions. Each chatbot represents a specific AI agent setup.

Customer slug
A short identifier for a customer account (e.g., acme for "Acme Co.") used as a prefix in all table names in the shared dataset.

Linked dataset
The BigQuery dataset created on the customer's side when subscribing to Zowie's Analytics Hub listing. Provides a read-only view of Zowie's shared data.

Snapshot fields
Fields on the Tickets table (prefixed snapshot_*) that capture a user's CRM profile at the moment the ticket was created, preserving a historical record even if the profile has since changed.


Entities in the Data Model

Users table
Contains profile fields (name, email, phone), authentication level (authenticated, recognized, or anonymous), external user ID, and arbitrary custom properties set by the customer, of end user

Tickets table
Contains single support requests. Request can originate from an AI Supervisor interaction or a standalone Inbox thread.

Interactions table
Contains a segment of a ticket owned by a single actor — AI Agent, human agent, or queue. A new interaction is created each time ownership changes.

Events table
Contains individual messages, actions, or system events within an interaction. The most granular level of data in the unified model.

End User
The customer interacting with the AI Agent or human agent

Human Agent
A support team member handling a conversation in Inbox. Referenced as owner = 'human_agent' in the Interactions table.


Interaction Concepts

AI Agent interaction
An interaction segment handled by the AI Agent, sourced from AI Supervisor. Includes contact reasons, intents, sentiment, and knowledge sources used.

Inbox synthetic interaction
A human agent or queue interaction segment derived from Inbox chat metadata, synthesized into the unified interaction model.

Standalone inbox ticket
An Inbox thread that was never handled by the AI Agent — has no corresponding AI Supervisor interaction.

Contact reason
A classification of why a customer reached out, recognized by the AI Agent. Stored as recognized_contact_reasons and final_contact_reason on Interactions.

Final contact reason
The definitive contact reason assigned at the end of an AI Agent interaction, used for volume and automation rate analysis.


Event Types

AI Agent (GenAI React) Events

These events trace the AI Agent's reasoning loop — from receiving a user message through LLM calls, tool use, and response generation.

Event TypeDescription
UserMessageV2End-user sends a message to the AI Agent. Contains full input text, channel info (Email/Chat), react configuration, user details (language, region).
AIAgentResponseV2AI Agent produces a response. Contains generated reply text, or cannotHelp: true when the agent can't answer (triggers handover).
ReasoningResultV2Output of a single AI reasoning step — the agent decided what to do next (use a tool, respond, escalate).
ToolRunV2AI Agent initiated a tool execution (e.g., KnowledgeSearch, intent lookup).
ToolUsedV2Tool execution completed, result returned to the agent.
ToolKnowledgeSelectedSourcesV2Knowledge sources selected and ranked by the knowledge search tool. Shows which FAQ/KB articles were retrieved.
AvailableToolsV2Snapshot of tools available to the AI Agent at a given reasoning step. Changes as tools are added/removed during the turn.
ParallelTasksInfoV2Metadata about parallel task execution within the AI Agent reasoning loop.
IntentCandidatesV2Intent classification candidates identified by the AI. Includes confidence scores and goal extraction.
IntentResponseV2An intent was matched and a response was triggered from the FAQ/intent system.
ReactErrorV2Error in the React (AI reasoning) pipeline. Includes error type and details (e.g., timeout).
ReactGuardV2A post-tool guard/safety check was triggered during AI reasoning.

Zowie Engine (Workflow) Events

Events from the deterministic workflow engine that handles structured conversation flows, API integrations, and decision logic.

Event TypeDescription
SessionStartedNew Zowie Engine workflow session started for the interaction.
GoToWorkflowNavigation to a top-level workflow.
GoToSubWorkflowNavigation from a parent workflow into a sub-workflow.
ReturnToParentWorkflowReturned from a sub-workflow back to the parent.
GoToModuleNavigation to a reusable module within a workflow.
BlockEnteredA specific block (step) in a workflow was entered. Very high volume — tracks every step execution.
BlockErrorError occurred executing a workflow block.
ResponseWorkflow sent a text response to the user. Contains the response text and strategy.
LogDebug log message emitted by a workflow block.
KeyRetrievedRetrieved a stored key-value pair from session/conversation storage. Highest-volume event type.
KeyStoredStored a key-value pair to session/conversation storage.
ApiCallMadeExternal HTTP API call made from a workflow block. Contains full request/response details.
UserActionReceivedRaw user action received by the engine (text message, button click). Lower-level than UserMessageV2.
RuleMatchedA condition/rule matched in a decision table block.
DefaultActionFallbackNo rules matched in a decision table — default/fallback action was triggered.
ExtractorStartedA data extractor (custom JS function) started executing.
ExtractorSuccessData extractor completed successfully.
ExtractorFailureData extractor failed with an error.
LoopDetectedInfinite loop detected in workflow execution — safety mechanism that halts processing.
ObservationObservation/debug info emitted during AI processing within workflows (e.g., prompt instructions, context).

Inbox Events

These events record conversations handled through Zowie Inbox — both the messages exchanged and the state changes around them: queue entries, agent assignments, postpones and closures. They carry author: human_agent when raised by an agent, the system or a chatbot, and author: user when raised by the end user.

Event TypeDescription
ConversationStartedOpens a conversation with an end user and issues its ticket number. The first event in a conversation's history.
ChatStartedOpens a thread — one handling episode inside the conversation. Records the participants and who held the conversation before and after. A conversation with several handovers has several threads.
ChatFinishedCloses a thread. Emitted when the conversation is resolved, auto-closed or handed back out of Inbox.
MovedToFolderThe conversation moved between desk folders. Moving to PostponeInbox is a postpone (snooze); moving from it ends the postpone and returns the conversation to the agent.
ThreadPassedOwnership was given away. Carries the owner list before and after the change.
ThreadReceivedOwnership was taken up. Carries the owner list before and after the change.
ThreadRequestedOwnership was requested from the current owner. Declared but not emitted in current production traffic.
AgentFromDepartmentRequestedThe conversation entered a queue and Inbox began looking for an available agent in it. Carries the service-level thresholds and the SLA clock origin in force for this conversation. Re-emitted on every re-queue, so a forwarded conversation has one per queue it passes through.
AgentAssignedAn agent took, or was given, the conversation. Marks the end of the queue wait and the start of handling.
AgentDeassignedThe agent stopped holding the conversation. The cause field says why — resolved, forwarded to another agent or queue, taken over, timed out on inactivity, or returned from postpone — and names the destination where there is one.
AgentInteractionFinishedThe agent's involvement is over. Emitted immediately on de-assignment when wrap-up is off, or after wrap-up completes when it is on.
WrapUpStartedThe agent entered post-conversation wrap-up, with the configured wrap-up duration. Only emitted where wrap-up is enabled.
WrapUpFinishedWrap-up ended. Always accompanied by AgentInteractionFinished.
ReminderScheduledAn agent set a reminder on the conversation for a future time.
ReminderFiredA scheduled reminder came due.
AutoCloseScheduledAutomatic closing was scheduled for a future time.
AutoCloseFiredAutomatic closing ran and ended the conversation, recording the topic and queue it closed under.
TopicAddedA topic (disposition) was attached to the conversation.
TopicClearedAll topics were removed from the conversation.
NoteAddedAn internal note was added. Never visible to the end user.
CustomerInsightsAI-generated context shown in the agent's side panel — cart contents, purchase history, sentiment score, conversation summary and similar.
AuthorAddedA new participant appeared in the conversation.
AuthorMetadataUpdatedA participant's profile details changed — name, email, locale, avatar. High volume and rarely of analytical interest.
TextA plain text message. The single most common event type, sent by end users, agents and chatbots alike.
FileA file or attachment, referenced by file id.
ButtonThe end user pressed a button offered earlier in the conversation.
ReferralThe end user entered the conversation through a referral link or entry point.
LocationThe end user shared a geographic location.
EmailTemplateAn email message, with headers, subject, body and attachments. The message form used on email channels.
QuickButtonsTemplateA message offering a set of quick-reply buttons.
UrlButtonTemplateA message with a button linking to a URL.
CallButtonTemplateA message with a button dialling a phone number.
AnnouncementTemplateA system announcement shown in the conversation, either persistent or temporary.
ImageTemplateAn image, optionally with action buttons.
VideoTemplateA video, optionally with action buttons.
AudioTemplateAn audio clip, optionally with action buttons. Declared but not emitted in current production traffic.
CarouselTemplateA scrollable carousel of cards, each with a title, image and buttons.
PersistentButtonsTemplateA message whose buttons stay available rather than disappearing after use.
LocationTemplateA prompt asking the end user to share their location.
CommentTemplateA public comment on a social media post, with the post it belongs to.
CommentReplyTemplateA reply published to a public comment.
CommentHideTemplateA public comment was hidden.
CommentDeleteTemplateA public comment was deleted.
TweetTemplateA public post on X/Twitter, with mentions and attached media. Declared but not emitted in current production traffic.
TweetReplyTemplateA reply published to a post on X/Twitter. Declared but not emitted in current production traffic.

Inbox Configuration

Inbox Group
A grouping of human agents configured within Inbox, used for routing and organization.

Inbox Queue
A waiting state in Inbox where conversations are held before being assigned to an agent.

Inbox Topic
A classification label configured in Inbox, used to categorize conversations.

Inbox Thread
A conversation between an end user and a human agent within Inbox.

Inbox User
A human agent account configured within the Inbox instance.


Did this page help you?