← All case studies
Hepzibar mark
Case study · Bar bookings and events

How Hepzibar uses Feedbank

Pay Hepzibar with Feedbank →

Table bookings, events and a cocktail menu that changes weekly, for one bar.

The moment it loses people

A guest books once through the site and books the next time by phone.

The pattern

Insight: structured answers to act on

The hub files every answer by topic and screen, and the model names the core reasons behind them.

The trade

Gives: A free cocktail per accepted loop, on the next visit

Asks: Five questions after a visit

The door, live at /pay/hepzibar
Hepzibar's door on a phone: Pay Hepzibar 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. Hepzibar's hub has the same screens, filed under Booking, The menu, Events and Leaving.

The weekly loop

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

  1. 1What made you book online this time, and what would make you call instead?
  2. 2Which cocktail did you order, and what did you almost order?
  3. 3What did you expect from the event listing that was not there?
  4. 4What did you look for on the menu page on your phone?
  5. 5What would bring you back on a weeknight?

What Hepzibar learns

  • Why guests go back to the phone
  • Which menu lines sell
  • What the event page is missing
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 Hepzibar's setup on Feedbank. Figures appear only where the brand has published them.