Skip to main content

Goodbye TheFork + five UX sprints on live service

RestaPro Team
Product & Platform

Big wave this week: we have removed the TheFork integration and run five back-to-back sprints polishing the Live service screen point by point.

Why we removed TheFork​

We learned this the hard way: when RestaPro was the source of the reservation, data was consistent and emails arrived on time. When a reservation came from TheFork, there were two sources of truth: sync drifted, reminders duplicated, and restaurant owners got complaints from guests receiving two confirmations for the same dinner.

The decision was: either fix it properly (weeks of work) or remove it. We chose to remove it and simplify. If you need TheFork, we still ask customers to keep it running in parallel and reflect those reservations as walk-ins in RestaPro.

If you still had a restaurant connected to TheFork, past reservations stay in history and new ones stop syncing. We flagged it via email and a backoffice toast.

Five UX sprints on live service​

After launching Live service, we ran weekly sprints to polish what you only feel when you actually use it:

  • Sprint 1. Quick wins: tooltips, keyboard shortcuts, responsive layout on tablet.
  • Sprint 2. General UX: copy review, clearer separators, visual weights.
  • Sprint 3. Operational efficiency: fewer clicks to reassign, quick access to "mark arrived", critical-table highlighting.
  • Sprint 4. Guest context: VIP badge and no-show counter visible at a glance.
  • Sprint 5. TV view (mode for the dining-room display) and sound on new incoming reservation.

If you have not opened this screen in a while, try it now. It is a different thing.

More in the reservations guide.

ESENCA