← All case studies
Discued mark
Case study · Course discussion

How Discued uses Feedbank

Pay Discued with Feedbank →

Discussion threads that live inside online courses, next to the lesson.

The moment it loses people

A course creator installs it, posts twice, and students never reply.

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: The creator plan free for a month per accepted loop

Asks: Five questions from creators and from students

The door, live at /pay/discued
Discued's door on a phone: Pay Discued 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. Discued's hub has the same screens, filed under First posts, Replies, Notifications and Leaving.

The weekly loop

Five questions on first posts, replies, notifications. Every answer is scored for how specific it is; a complaint earns what a compliment earns.

  1. 1What was the first thing you posted, and what reply were you hoping for?
  2. 2Where in the lesson did you want to say something and could not?
  3. 3Which notification made you come back, and which one you ignored?
  4. 4What would make you reply to another student?
  5. 5What did the thread need that it did not have?

What Discued learns

  • Why first threads go unanswered
  • Which notifications bring people back
  • What a lesson needs to start a conversation
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 Discued's setup on Feedbank. Figures appear only where the brand has published them.