== Changelog ==

Le versioni piu' recenti stanno nel readme.txt. Qui c'e' la storia completa. The most recent releases are in readme.txt. This file keeps the full history.

= 1.0 =
* First public release.
* Table reservations with availability, opening hours, rules on the number of guests, a weekly closing day and a quick-block calendar for one-off closures.
* Moving a booking: the guest changes day, time or number of guests from the link in their confirmation email (free tables re-checked live, with a per-venue limit), and staff can move any booking from the Waiter Dashboard with no limit.
* Per-venue time zone, filled in automatically from the WordPress setting or the site language, and from the city in the address for countries with more than one zone.
* No-show guarantee: the guest's card is authorised, never charged, and only captured if they fail to turn up. Staff release or charge it from the Waiter Dashboard.
* Prepayment tiers ("Menu Tariffe") for fixed-price menus, with their own refund policy, separate from the guarantee deadline: in one case nothing was ever charged, in the other the food is already bought.
* Prepayment tiers can carry a time band, days of the week and a minimum number of guests, and a tier covering the chosen time takes precedence over the no-show guarantee.
* A per-venue list of which booking emails reach the restaurant, all on by default.
* Settings page organised in three tabs: the venue and its hours, payments, and the messages you send. One Save button saves all of them.
* The reminder always goes out by email, and on top of that as one phone message: WhatsApp when configured, otherwise SMS.
* The reminder is written in the guest's own language, worked out from their phone number's country code as well as the language they booked in, so a tourist gets it in a language they read. Seven languages, each written to fit one SMS with the cancel link inside.
* Android SMS gateway setup reduced to scanning a QR code and copying two values, with each Android warning screen named in the instructions.
* The phone number becomes a required field only on venues that have SMS or WhatsApp switched on, with a line under it saying why it is asked.
* SMS reminders through your own provider, with ready-made integrations for Twilio, Skebby, Aruba SMS, Brevo and Vonage, plus an Android phone gateway. A test button sends one real message so a wrong key surfaces immediately.
* WhatsApp booking messages through your own WhatsApp Business Account: every reservation message goes out on WhatsApp too, not just the reminder, with a button that writes the eight templates onto the account and submits them to Meta for approval.
* Printable flyers with a QR code in A3, A4 and A5, each size laid out for its own reading distance.
* Gift cards, cooking classes and dating events.
* Seven languages, with the booking widget following the page language (Polylang and WPML supported).
* Guest assistant. A chat on your booking page that answers your guests with your real data, opening times, which slots are still free in the next 7 days, discounts and events. It uses your own Groq account: nothing is sent while the key field is empty. It does not book: it hands the guest to the booking form.
* The assistant can read up to five pages of your own site (menu, how to get there, parking) and answers with what is written there, saying where it read it. On prices and allergens it repeats only what you published; if it is not written, or if a guest asks whether a dish is safe for their own allergy, it sends them to your phone.
* When a guest names the day, the time and the number of guests, the button takes them to the booking form with all three already chosen, so they only fill in their name. If you are running time-slot discounts that day the list of times is shown instead, so the discounted slots stay visible.
* Optional lunch and dinner hours, on the Locations page next to Opening and Closing. Fill in both and the hours in between disappear from the times your guests can pick, so a restaurant that closes in the afternoon stops taking bookings at 16:00.
* Panel language, in mee-table -> Settings. On "Automatic" the panel follows your Site Language (Settings -> General); pick a language and it stays on that one, whatever WordPress and any translation plugin say.
* A question mark next to each section title opens the online guide at the exact paragraph that explains it.
* The link in emails and messages opens the booking widget on the restaurant's own site in edit mode: move or cancel with the venue's real rules. A hosted fallback page answers when the site is unreachable.
* Per-venue cap on people per single booking, separate from the venue capacity, enforced by the server on new bookings and on changes.
* Optional notice window: online changes close a chosen number of hours before the table, cancelling stays open.
* The Waiter Dashboard gives the space to what you actually read. Notes are twice as wide and no longer cut off in the middle, because from this version the booking form invites guests to write their allergies there. Phone and email are narrow: one tap calls, one tap opens the mail, and nobody reads an address out loud. Payment and Refund appear only when a booking in view was actually paid, so a venue that never turns prepayment on stops carrying two empty columns on every line, and the day the first payment lands they come back on their own.
* The booking form asks for allergies and intolerances in the notes, without making it compulsory: a required field would make everyone type "no" to get past it, and a declaration written to be rid of it is not information.
* Table rules, per venue: how long the table is held for a late guest, and how long it stays with the same guests. Both go into the confirmation email in the guest's own language, and optionally into the booking form as well. Leave a field at 0 and its line is never written: a venue that decided nothing promises nothing. The panel names the usual figures country by country, because they are not the same everywhere.
* The country code for the phone is picked from a list showing the flag and the country's own name, preselected from the guest's browser. United States and Canada share a dial code and are now two separate rows, so a Canadian no longer sees the United States selected.
* The "Message us on WhatsApp" button opens a chat with the restaurant's name already in the message: whoever reads it knows which venue it came from, which matters when two venues share one number.
* Switching WhatsApp or SMS off no longer deletes the credentials. Off means off, not erased: switch it back on and everything is still there.
* On the Locations page one venue card stays open at a time, so the page does not grow past reading.
* The test WhatsApp message goes out in the language of the number you type, the same table the real messages use. If that language is not approved on Meta yet, it arrives in Italian and the panel says so.
* The panel language also decides the language of the emails mee-table sends to you: one language, the one you picked, not two. Your guests keep reading in their own.
* The WhatsApp panel walks you from zero to a working setup: the numbered steps go from creating the Meta business account to the three values to copy. The message texts are already written: the button copies them onto your account and sends them to Meta, who reviews them. Approval usually takes a few hours.
* 23 August 2026: Dating Aperitivo tickets carry a QR code, and the number of drinks the ticket includes is set per event, from one to ten. From the Waiter Dashboard staff press "Scan the ticket" to open the camera and take one drink off the moment it reads the code, with a ticket-number field as a fallback if the camera cannot start. There is no such control on the guest's own page.
* 23 August 2026: The Waiter Dashboard gained a printable kitchen sheet, time, name, number of guests, phone and notes for the day, laid out for the printer and leaving out cancelled bookings and no-shows. A note that mentions an allergy or intolerance is now marked "ALLERGIES" and stands out from ordinary notes, so it is not missed at a glance.
