← All case studies
Saverfly mark
Case study · Flight price alerts

How Saverfly uses Feedbank

Pay Saverfly with Feedbank →

Price alerts for the routes people actually fly, with a booking window.

The moment it loses people

An alert fires, the price has moved by the time they look, and the alert is deleted.

The pattern

Retention: feedback in exchange for access

Access in exchange for answers: the trial or the product keeps going as long as the answers do.

The trade

Gives: Premium alerts free for a month per accepted loop

Asks: Five questions after each alert

The door, live at /pay/saverfly
Saverfly's door on a phone: Pay Saverfly with Feedbank, what you get, what you give, and the button to start the first loop
The hub, as every brand's team sees it
The hub: accepted answers this month, answers that need a reply, credits issued, topic filters and the first answers

Planbrand's workspace, with answers in it. Saverfly's hub has the same screens, filed under Alerts, Booking, Routes and Leaving.

The weekly loop

Five questions on alerts, booking, routes. Every answer is scored for how specific it is; a complaint earns what a compliment earns.

  1. 1What had changed by the time you opened the alert?
  2. 2Which route do you watch that you have not told us about?
  3. 3What did you book instead, and where?
  4. 4What would make you act on an alert within an hour?
  5. 5Which alert did you delete, and why?

What Saverfly learns

  • How fast alerts go stale
  • Which routes are watched
  • Why alerts are deleted
At the moment of leaving

Anyone who stops gets three exit questions: what made you stop, what would have kept you, what did you expect. Scored like any answer, credited, and read first by the Insights model.

This page describes Saverfly's setup on Feedbank. Figures appear only where the brand has published them.