Hhaila
Every task, on every app your team uses. No guessing, just the exact steps.
Every reservation that arrives through HaiLa starts as a pending request. Until you answer, the guest does not know whether they have a table, and the request expires on its own if you leave it unanswered.
A new request stays pending until you respond. As long as you have not responded, the guest does not know whether they have a table.
A quick decline leaves the guest time to look elsewhere. Declining costs you nothing, exactly like a request you let expire.
When the requested time does not work but another one does, a proposal keeps the guest. While the proposal is waiting for an answer, the request no longer expires and you stop getting reminders about it.
No app tells you when the guest answers your proposal. If you do not check, an accepted reservation goes unnoticed and a declined one quietly lands back in your queue.
Seating is the only signal that the guest actually turned up. It takes the reservation out of the arrivals list and shows the table as occupied on the floor plan.
Closing frees the table and sends the review invitation. If you do not do it, HaiLa closes the reservation itself later, invitation included.
A no-show is the only trace that the guest did not arrive. Without it, the reservation closes automatically as completed and the guest is invited to review a visit that never happened.
Something breaks in the kitchen, a table gets double booked, the guest calls. Cancelling tells the guest and takes the reservation off the invoice.
A phone reservation written into HaiLa holds the table in the same place as the online ones, so the two cannot overlap. Reservations your team enters are free.
A guest you already know does not need to spell everything out again. Picked from the list, the reservation stays attached to their record, so next time you see their visits, the team notes and their no-shows.
A walk-in occupies a real table. If you do not enter them, the floor plan shows that table as free and somebody seats another reservation on top of them.
A reservation without a table is a promise without a place. Assigning ties it to a real table, so the same table never goes to two parties.
Parties move: they ask for another area, the next table frees up, the window seat is draughty. Moving them in the app keeps the floor plan honest for the whole team.
A released table is immediately available to someone else. You do this when the party is no longer coming at that hour, or when you want to lay out the whole evening again from scratch.
At thirty reservations a night, assigning them one by one eats the service. Automatic assignment walks through all of them, seats what fits and leaves you only the cases that need a person.
The setting decides who picks the table: your team or the system. In automatic mode HaiLa can send the guest a proposal for another time without anyone pressing anything, so it is worth knowing which mode you are on.
Fingers miss. Undo fixes it on the spot, without hunting the reservation back down in a list.
A party grows from four to six, someone is running half an hour late. Editing keeps the reservation right for the whole team, but it does not tell the guest, so speak to them yourself.
During service only one day matters. The day view shows everything happening today, in time order, without the noise of the rest of the week.
The week shows where the pressure gathers, so you can see when to put extra people on and when you can still take a large party.
The timeline puts the hours side by side, so you can see at a glance which party is late, which table is running over its turn time and where two reservations land on the same table.
A phone call settles in thirty seconds what a notification never settles: the party running late, the table that freed up early, the special request nobody understands.
In the middle of service there is no time for lists. The plan shows the room as it is right now: which table is taken, which is free, and who is sitting where.
The plan does not change by accident during service. Changes are made in a separate mode, and until you save, nothing reaches the room.
Every table in HaiLa is a seat you can promise a guest. A table that exists in the room but not in HaiLa never receives an online reservation.
The map is only useful if it looks like the room. A table drawn where it is not confuses the team at exactly the moment they are glancing at a phone.
Seats decide which parties fit at the table, and the zone decides what it can be merged with. They are the two things HaiLa uses when it gives a table to a reservation, or does not.
Rooms change: a table goes, the terrace closes for winter. A deleted table leaves the seat count, so HaiLa stops promising guests a seat you do not have.
A plan you recognise your room in is read at a glance. Walls and dividers are the only thing that makes the map look like your place.
A party of eight does not fit at a table for four. Merging makes one table out of two, with the seats added together, so the party takes one place on the plan.
The big party has left and the room needs its ordinary tables. Unmerging puts them back exactly as they were, on the map included.
A venue with a terrace and a dining room has two maps, not one crowded one. Floors split the plan into pieces the team reads separately.
The floor name is what the team reads in a hurry. Big terrace says more than Floor 2.
The terrace closes in autumn, a room becomes storage. A deleted floor takes all of its tables out of the count at once.
Everything you do in edit mode sits aside until you tap Save. That is the moment the room and the reservations really change, so it is worth understanding.
Not everything about the room is done standing up, on a phone. For a bigger rearrangement, the dashboard has a plan editor too, on a large screen.
Before you call someone or prepare a table, it helps to know how often they have been, what they asked for last time, and whether they have no-shows.
The favourite table, the anniversary, the allergy. Notes land on the reservation row, so the team sees them without looking anything up.
A short rating after a difficult visit helps the team next time, and the score feeds a reputation other restaurants can see too.
Reviews are public and show on your venue page. What they say decides whether someone who does not know you books or moves on.
The reply shows under the review, for everyone. A calm reply to a bad review convinces more than ten good ones.
A review with no reply looks worse than a bad one with a reply. The filter tells you exactly where you have fallen behind.
The programme does nothing until you publish it. Published, it enrols guests on its own, from their first reservation.
The reward that worked in summer does not work in winter, and the target you set at the start turns out too high. Both can change, but you need to know who the change catches and who it does not.
It is the question everyone asks in the first week: where do I press to give them the stamp. The short answer is that you do not press anywhere.
Your menu shows on your venue page and in the app. The quickest way in is a PDF, because we read it and you only check it.
In the dashboard and in the Pro workspace, what you see after the read is a proposal, and your check is the only thing standing between a wrong price and your public page. In Lite nothing stands there: the menu is already published, so the check is no longer an approval but a repair.
Prices move, dishes come and go. You do not need a fresh PDF for a small change.
It is worth knowing exactly what the save button does, so you do not go looking for a second one that does not exist.
A concert, a tasting, a themed night. The event shows to guests in the app, with its seats, and is booked straight from there.
For the Friday jazz night or the Sunday brunch there is no point building a new event every week.
An event with no photo gets lost in the list. The first photo is the cover, which is the only one someone sees before opening it.
An event does not reach guests on its own. It goes through a review with us, and you are the one who starts it.
While it reads In review the event is still yours: no guest has seen it, so it can be changed freely.
The night before, you want to know how many people you have and who they are, so you can set the room.
Your hours decide what times a guest is offered. A day marked closed has no times at all, however hard they look.
If you would rather not find out at 19:55 that six people are coming at 20:00, this is the setting that closes the last minutes.
With no limit, someone can hold a table eight months out, on a date you know nothing about yet.
For a day taken over by a private party, a week of building work, or a night with a closed event, without touching the hours you show.
A new manager needs access, and someone who has left should no longer have it.
Every reservation that reaches you through HaiLa carries a fixed fee, different by the channel it came from. Without it you cannot read the invoice.
At the end of the month you want to know where the number comes from, not just what it is. The page breaks it down by venue and by channel.
With two or three venues on one account, the month total does not tell you which of them costs what, or why.
A number that does not look like your month is settled quickly if you know what to check first and who to write to.
With Poster connected, your team stops keeping two reservation lists and stops copying anything by hand from one screen to another.
The widget lets someone book without leaving your site, and a reservation that arrives that way costs half of one that comes through HaiLa.
The widget sits inside your page, so it is worth matching it as far as it can be matched: the language it speaks and the background, light or dark.
If you run your own site or your own app and want the reservations inside it, the API gives out free times and takes a reservation, with no widget involved.