Overview

🔍Simple search bar

At the top, you can search for tickets using their ticket number—no more dealing with impractical ticket IDs. This makes it faster and more intuitive for support teams to locate and assist with specific tickets.

T

At a glance, the ticket number and associated spectator email are clearly displayed, along with a status badge (e.g., DOWNLOADED) and the event name and start time indicating which event the ticket grants access to.

Below, a dedicated section presents the ticket ownership overview:

Holder (if Ticket Holder is defined. By clicking on it, you’ll be redirected to the Ticket Holder tab)
Current Owner
Previous Owner (hidden if the ticket was never transferred)
Initial Owner

The header background color provides an immediate visual cue by dynamically reflecting the ticket’s current status, helping support agents quickly assess its state at a gl

Green for DOWNLOADED
Lavender/Purple for NOT_DOWNLOADED
Golden Beige for PENDING_TRANSFER
Carrot Orange for DELETION_PENDING
Red for DELETED

📋Tabbed Navigation

Tired of endless V3 vertical scrolling? We’ve introduced tabbed navigation to bring clarity and focus—starting with what matters most.

From this navigation bar, you’ll be able to target different aspects of the ticket via four tabs:

Overview: Seating details, Purchase info, Ticket Attributes and new Status History (loaded by default)
Ticket Rules: Rules applied to this ticket
Metadata: Technical metadata
Ticket Holder: Collected data from the spectator

No matter which tab you navigate to, the ticket overview remains visible at all times, ensuring key information is always accessible without switching context.

Walkthrough the Tabs

‘Overview’ tab

The new Overview tab is designed to be operation-ready, presenting key ticket details at a glance:

Seating information
Purchase details
Ticket attributes, indicating when the ticket reached specific milestones such as Injection, Delivery, Assignment, Check, Control, or Deletion

And last but not least, the new V4 Ticket Status History, powered by the enhanced V4 model that tracks actions, actors, and devices with precision.

Ticket history

Ticket history > Overview

By default, a simplified overview of the ticket history is displayed, focusing on business Events which are bringing together ticket status & attributes (see Introduction to Tickets V4 | New ticket statuses and attributes).

The content of this table matches 1:1 the status history published to S-360 (and thus aligned with information visible from S-360 screens). Please refer to: S-360 <-> TIXNGO V4 Interface

Ticket history > Detailed

The detailed tab display the full Ticket status log, displaying every Action and corresponding ticket Status.

For explanation of each status, please refer to Introduction to Tickets V4 | Ticket Status.

Every history entry (overview or detailed) is displaying two timestamps:

The system date time when the corresponding event has been recorded by TIXNGO servers
When applicable, the mobile date time when the corresponding event happened on the mobile app.

‘Ticket rules’ tab

From the Ticket Rules tab, you can view the set of rules applied to the ticket.

Support Ticket > Ticket rules Tab

By default, only the rule names are displayed. If you’d like to see more details about a specific rule, simply expand the rule to reveal its configuration.

Support Ticket >Ticket rules Tab – Example of Expand/Collapse

For TIXNGO V4 roll-out, all rules types are expandable, except for Email rule, which is excluded as they do not directly impact the spectator, ticket rendering, or available actions on mobile.

'Metadata' tab

The Metadata tab provides in-depth information about the ticket, organized into clearly labeled sections to support advanced troubleshooting and back-office validation.

Ticket Details

Displays V3-like ticket metadata split into the 3 standard category: Main, Extra, Hidden

Purchase & Seating Details

Before all S-360 translations are propagated to TIXNGO, we will show in these sub-sections all the technical identifiers related to Purchase and Seating details

Purchase Details

Includes technical identifiers linked to the commercial configuration of the ticket:

Seat Category ID
Tariff ID
Contingent ID

'Ticket Holder' tab

The Ticket Holder tab displays all the data collected about the person assigned to the ticket. It reflects values gathered through Data Collection Rules, including both standard and custom fields.

Support Ticket > Ticket holder Tab

Fields are shown as Crowdin labels (for multilingual support) alongside their recorded values.
Supports various data types, such as:
- Text (e.g., First name, Last name, ID number)
- Date (e.g., Birth date)
- Boolean (e.g., test_bool_m, test_bool_o)
- Enum (e.g., Gender)

This tab is especially useful for verifying collected data, ensuring compliance, and supporting onsite or remote checks where ID or age verification may be required.

V4 Ticket Support screen