Sessions

Browse, filter, and manage your agent's conversations

Sessions is your primary tool for understanding how your agents behave in real conversations. Every interaction an agent has, whether text, voice, or a mix of both, across any channel, is recorded as a session in Observatory > Sessions. Each one holds the full conversation along with the data you need to understand what happened and why.

This makes sessions the foundation of agent analysis. When a test fails, the result links to the session that caused it. When a user reports strange behavior, you trace it here. When you want to understand why an agent responded a certain way, open the session and follow the workflow steps that produced that response.

Once you have found the session you are looking for, Inside a Session covers the transcript, metadata, and sidebar tabs, and Interaction Logs covers the workflow trace behind each reply.

Navigating Sessions

Open Observatory > Sessions > Chat Sessions to start exploring your agent's conversations. From here you can sort, filter, and tag sessions to find exactly what you need. Whether you are investigating a user complaint, reviewing test results, or tracking how a workflow change affects real conversations, this is your starting point.

Deep Dive

Expand any session to inspect the full conversation, workflow trace, and variable states

Sort & Browse

Sort by date and scan across agents and contacts to spot patterns at a glance

Tag & Organize

Review the tags each session collected during the workflow run and use them to filter and organize conversations

Export Transcripts

Download individual session records or export in bulk based on your current filters

Every session records the agent that handled it, when the conversation started, the contact who initiated it, which deployment served it, how long it lasted, and any tags assigned during the workflow. Click any session to expand it into the detail panel.

Agent

The agent that handled the conversation. Each row displays the agent's name and icon.

Created At

The timestamp when the session started. Click the column header to sort sessions by date in ascending or descending order.

Contact

The end-user who initiated the conversation

Deployment

The specific deployment that served the conversation (e.g., "Webchat Production" or "Automated Agent Testing Deployment"). Useful for distinguishing between channels or test environments.

Duration

The total time elapsed from the first message to the last interaction in the session.

Tags

Labels assigned during the workflow run via the Tag node. Use tags to categorize and filter sessions by topic, intent, or any custom criteria you define in your workflows.

Actions

Two actions per row:

• Click the download icon to export the session record

• Click the arrow icon to open the session detail panel

Sessions are available even before they expire. Use the refresh button to reload the session list and see ongoing conversations as they come in.

Filtering and Searching

Every Observatory page shares the same filter bar, which shapes the results you see. Work through them in order: scope the data, filter within it, then save the view or clear it to start over.

1

Set the Scope

Date Range and Agents define the data the page draws from. A wrong window or agent is the most common reason a page comes back empty.

Date Range

Set a start and end date to define the time window, then click Apply

Agents

Filter by agent or deployment, with your selected agents pinned first

2

Filter by Value

Within that scope, these filters narrow the results further. Each one lists only the values found in the current Date Range and Agents, so widen those if an option you expect is missing.

Filter	What it does
Tags	Include or exclude results by tag
Variables	Filter by a session variable's name, with an optional value to match against it
Contains	Keep sessions that include specific signals, such as user feedback or a CSAT response

3

Save or Reset Your View

Once the filters show what you want, keep that view or reset it.

• Save: Stores your current selection (Date Range, Agents, and every value filter) as your personal saved view. Observatory reopens with it applied, and an indicator flags whenever your live selection differs from what you saved.

• Clear: Resets the whole bar to its default view: the date range returns to its default and every other filter empties. Your saved view is left untouched, so Clear is a fresh start, not a delete.

Share a view: Filters live in the URL, so sharing or bookmarking the page reproduces the same view. Your selection also persists as you move across Observatory.

Searching by Attribute

With hundreds of sessions accumulating over time, finding the right conversation requires more than scrolling. Switch between search modes, each matching a different session attribute such as message content, tags, or Session Analysis signals. Like the shared filters, the available signal options adjust to the current date range and agents.

Combine filters to narrow results quickly. For example, filter by Contains: CSAT Response on a specific agent to find conversations with a user survey.

Exporting Sessions

Export session transcripts to share findings with your team or analyze conversations outside the Helvia Console. You can exclude messages from bulk exports when you want to focus on sessions rather than individual messages.

Supported formats:

• TXT

• CSV

• XLSX

Individual Export

Click the download icon in the Actions column of any session row, or use the download button inside the session detail panel.

Bulk Export

Select Download in the toolbar to export multiple sessions at once based on your current filters and date range.

Sessions generated by automated tests are excluded from bulk export.

Example: Individual Session Record

Timezone: Eastern European Standard Time

-- Session details:
Agent: <agent_id>
Session id: <session_id>
Date Created: <date>
Last Interaction: <date>
Duration: <duration>
Message Count: 3
Tags: []
Sentiment: 
Summary: 
Urgency: 
Resolution: 
Features: 
Metadata: [subscriberName=<name>, subscriberEmail=<email>, deploymentId=<deployment_id>, deploymentName=<deployment_name>, platformOrigin=<platform_origin>]
-- Messages
Sender | Time | Message | Tags | CSAT
<user_info> (user) | 10:35 | Jump to node: agent_start | [] | 
(bot) | 10:35 | Happy Wednesday morning! Ready to crush today’s priorities and keep things light? Let’s make this a smooth, focused start. | [] | 
<user_info> (user) | 10:35 |  Let's get started. How can I be more productive with my calendar? | [] | 
(bot) | 10:35 | Use your calendar as a **plan, not a diary**:

- **Time-block** your top 1–3 priorities daily
- Add **buffers** (10–15 min) between meetings
- Batch similar work (emails/admin) into set slots
- Schedule **deep work** like a meeting (no notifications)
- Do a **5-min daily plan** + **15-min weekly review**

What calendar do you use (Google/Outlook/etc.) and what’s your biggest issue—overbooked, distractions, or forgetting tasks? | [] | 

Missed Questions

A missed question is a user message that your workflow explicitly flagged as something the agent could not answer. Go to Observatory > Sessions > Missed Questions to see them. This is not automatic detection. You decide where in the workflow a question counts as "missed" by placing a Missed Question Node on the path where the agent has no answer.

This makes missed questions a targeted feedback loop. Instead of guessing what users are asking that your agent can't handle, you get a concrete list sorted by frequency. Review it regularly to prioritize new content, update existing workflows, or expand your Knowledge Base.

To see missed question trends over time and how they compare to answered questions, check the Missed Questions tab in Analytics.

Reporting Missed Questions

Before anything appears in Observatory, you define which user messages count as missed. Place the Missed Question Node in the workflow path where the agent cannot provide an answer. Any user message that reaches this node gets recorded as a missed question, linked to the session and the specific message that triggered it.

Advanced: Reporting via the API

You can also report missed questions programmatically or with an HTTP Request Node by sending a POST request with the following payload:

{
  "missedQuestion": {
    "question": "{{userTextMessage}}"
  },
  "sessionId": "{{sessionId}}",
  "messageId": "{{messageId}}"
}

Each report is tied to a specific session and message, so it appears in the same context as node-reported questions.

System variables let you build workflow logic around missed questions. Use {{missedQuestionsCount}} to track the total number of misses in the current session, and {{consecutiveMissedQuestionsCount}} to detect when the agent fails multiple times in a row. For example, you could escalate to LiveChat after three consecutive misses. See Variables for the full list.

Browsing Missed Questions

The Missed Questions table collects every reported question in one place. Identical questions are grouped into a single row with an occurrence count, so repeated questions surface at the top rather than cluttering the list. Grouping is based on exact wording, so two messages phrased differently appear as separate rows even if the intent is the same.

Sort by Occurrences to prioritize the highest-impact knowledge gaps first.

Missed Questions uses the same shared filter bar as Chat Sessions: scope by date and agents, then refine with the value filters. To pinpoint a specific question, search the list by keyword. Export the full list as a CSV file using the Download button and use the adjacent options menu to choose between comma or semicolon separation.

Investigating a Missed Question

Knowing what was missed is only the starting point. You need the surrounding conversation to understand why it was missed and decide how to fix it.

Select any row to open the Missed Question Details panel. A stats bar shows the number of occurrences within your date range, the total occurrences since the agent was created, and how many distinct chat sessions contained this question.

From here you can browse and select any session where the question appeared and see the conversation transcript with the missed question highlighted. This gives you the context to understand whether the gap is a missing intent, unexpected phrasing, or a workflow routing issue. Select Go to Session to open the full session for a deeper look.

Surveys

Where Missed Questions surfaces what your agent could not answer, Surveys collects the structured input you deliberately asked for. A survey record groups everything a user answered during a single run of a survey workflow.

Go to Observatory > Sessions > Surveys to see every submission across your agents, one respondent per row. Expand a row to read the questions and the answers that respondent gave. The same shared filters scope this list, so narrow the submissions before exporting them as a CSV with the Download button.

Collecting Responses

Responses reach this page only from survey-producing workflows. Build a workflow in Designer > AI Workflows > Flows, set its type to Survey, and add nodes that ask the user for input. Any user-input node is captured such as Question, Option, Multi-Options, Dynamic Options, User Input, File Upload, and Input Collection (Beta).

Enable Surveys first: The Surveys powerup is off by default, so nothing is recorded until you activate it. Contact support to turn it on.

Best Practices

• Check your filters first: The shared filter bar scopes every Observatory view, so verify these are set correctly if you miss some sessions.

• Review missed questions by frequency: Sort by occurrences to surface the most common knowledge gaps first. Fixing one high-frequency miss improves more conversations than fixing ten rare ones.

• Tag sessions for follow-up: Use tags to mark sessions that need review, retraining, or escalation so your team can filter for them later

• Cross-reference with test results: Automated test results link directly to their generated sessions. Use this to investigate why specific test scenarios failed.

You can now browse, filter, and export sessions, and track unanswered user questions through Missed Questions.