Internal customer notes, allergen filter, and this wiki
A polish batch on the CRM, the public menu, and an announcement that concerns you directly: wiki.restapro.es is now live.
A polish batch on the CRM, the public menu, and an announcement that concerns you directly: wiki.restapro.es is now live.
At a restaurant owner's request ("walk-ins are coming in, I don't want any more online reservations for lunch, but I don't want to dig into settings"), we are shipping the live service pause.
This week was more about paying down debt than shipping new things, but the result is that the app feels more solid. Here is a summary so you know where things got better even if your eye did not catch it.
Two launches aimed at different profiles: the pure private-events business, and the restaurant owner landing on the public site for the first time.
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.
Two small improvements that cut noise on both sides: the guest does not call to change a time, and the restaurant does not learn about a new reservation late because they were checking another inbox.
This is the screen we have been thinking about for months: a single real-time view to run service without jumping between menus. It is called Live service and it lives at /app/local.
Two small but requested fixes from cafés and breakfast spots: morning hours are no longer a second-class citizen, and reservation slots no longer get cut off too early.
Two visible changes for your guests in this batch: the public menu has been fully redesigned, and you can now request a group event from your page without picking up the phone.
Invisible but important improvements: the AI assistant is faster, and platform errors no longer disappear into a log nobody checks.