Mission Control | TPG Sales Platform

Sales and reviews: supplied reports · Operational metrics: simulated scenario · No live feeds

Needs attention

Investigate affected orders and prepare a briefing.

SIMULATED OPERATIONS

Order / client	Payment method	Current state	Time in state	Amount

Demo rule: pending over 10 minutes, or captured payment without a ticket. Ten minutes is an illustrative threshold, not an agreed SLA.

Sales momentum

Tickets sold · 21 September – 5 October

Tickets sold Limited coverage**Sales records missing: 29 Sep 14:19 – 30 Sep 04:07.
5 Oct includes sales only up to 17:32. All times are Swiss time.

Key insight

AI DEMO

Sales are growing.
The audience is coming back more often.

Week 2 visits rose 34%, while unique visitors stayed almost flat. The pattern suggests deeper use within a stable tracked audience.

Launch ramp-up and incomplete tracking affect this comparison.

Based on sales and usage

How customers buy

18,071 completed orders · all available exports

Ticket shop80% · 14,500 orders

From a trip search20% · 3,571 orders

Opportunity to explore
Make ticket purchase from a connection easier to discover. A search without a purchase is not necessarily a failed purchase.

Where to focus next

Suggested actions from the post-launch analysis

3 priorities

01

Close the sales export gap

29–30 Sep is incomplete. Around 630 orders are estimated missing.

02

Understand the checkout journey

Align iOS and Android events before interpreting drop-off.

03

Build on SwissPass adoption

44% of orders are still guest purchases.

Customer voice deserves its own signal

October written reviews · snapshot collected 6 Oct, 09:44 Zurich

1.38 / 5 ★

29 reviews · 28 Android, 1 iOS

Access to departures, navigation and readability remain prominent complaints. Ticket-purchase friction also appears.

Sales growth and review sentiment can coexist. This small, self-selected sample does not measure satisfaction across all users.

REVIEW SNAPSHOTS

Written-review sample, not the overall store rating. No new store fetch.

Snapshot Platform

Rating trend

1–5 star scale

Every star counts

Rating distribution in the selected sample

Daily rating breakdown

Date	Reviews	1 ★	2 ★	3 ★	4 ★	5 ★	Average / 5	1–2 ★ share

What reviewers are reporting

Explore related metrics

Review themes can guide investigation; they do not establish causes.

01

“Buying a ticket is difficult”

Inspect checkout activity and payment visibility.

02

“Too many steps to see departures”

Compare the reported task with app usage.

03

Sales can grow while feedback stays negative

View commercial performance alongside customer feedback.

Two ways to purchase

Backoffice · whole report period

80%ticket shop

Ticket shop14,500

Trip search3,571

Share of completed orders, not purchase success.

The shop carries most sales. Journey-planner conversion is a separate measure with an earlier data cut-off.

Trip search → purchase

Matched window · launch to 25 Sep

EARLY SNAPSHOT

0.12%

724 trip purchases / 605,220 new-app trip searches

~1 in 830searches lead to a trip purchase

CHF 5.23trip revenue per 1,000 searches

Existing travelcards and information-only searches affect this ratio. It is not an app-wide conversion rate.

Inside the ticket shop

Visits containing each event · consented users · 21 Sep – 5 Oct

Indicative measurement

Indicative event counts. Platform event names differ, so these figures do not establish checkout abandonment.

Payment methods

Purchase quality

Partial visibility

Refunded tickets32 · ~0.2%

Refund within 10 minutes17 · 0.09% of orders

Median time to refund4 minutes

Purchase success rateNot available

Payment failure rateNot available

Failed and waiting orders are missing from the supplied export. Low refunds do not prove a healthy payment flow.

Migration to the new app

Share of all HAFAS trip searches · 22–25 Sep

Remaining searches include the legacy app and third-party API clients.

Platform mix

Tracked visitsiOS 81% / Android 19%

Orders with a known clientiOS 71% / Android 29%

Android has a larger share of orders than tracked visits. Consent differences and 800 orders without a client prevent a direct conversion comparison.

A reason to return

48%

of SwissPass buyers purchased at least twice

4,643SwissPass buyers

2,245repeat buyers

8,002guest orders

Guest repeat purchases cannot be identified in the supplied report. This is a two-week repeat-purchase measure, not long-term retention.

Product demand

Historical data

Build your briefing

Select the content for your briefing.

Report type

Report title

Audience

Your commentary (optional)

Demo report · review before sharing.

Recurring report

Choose a cadence for the demo.

Build your report

Choose an audience and sections, then generate a draft.

Data coverage

Historical report data and simulated operations

Demo coverage

Source	Available through	Includes	Note
Purchase operations Simulated	Illustrative 24-hour cohort	Purchase outcomes and fictional DEMO orders	Requires complete order/payment histories and matching timestamps. No live feed.
Backoffice	5 Oct, 17:32	Orders, tickets and revenue	Missing hours on 29–30 Sep
Matomo	5 Oct, partial day	Visits, screens and shop events	Consented users only
HAFAS / Grafana	25 Sep, 17:00	Trip searches and new-app share	Earlier reporting window
App reviews	6 Oct collection	Ratings and complaint themes	Written-review sample; limited iOS coverage

Metric details

Select a metric for its calculation and source

Metric	Definition	Source