Staff take orders on mobile devices, the kitchen sees its tickets and checkout brings payments and receipts together. You choose the workstations and guest features your venue needs.
A call, a visit, a request for a window table: your CRM keeps contacts, history and next tasks together. The next conversation starts with what you already know.
Reservations, calls and other modules supply contacts or events. The dashboard shows what reaches your CRM. Open contacts, incoming numbers and tasks from here.
View from the module · Via Palermo
02
Assignment
Turn a number into a contact.
Elena calls about a family evening. Add her name and link the number. Phone and email help you find contacts again; a name search alone does not establish a unique identity.
View from the module · Via Palermo
View from the module · Via Palermo
03
History
Look back before you call.
Elena’s timeline shows completed reservations and the next callback task. Linked calls remain traceable. See what happened without searching through several screens.
View from the module · Via Palermo
04
Segments
Find the relevant guests.
Filter by frequent visits, a long absence or missed visits. Segments follow recorded events. They do not replace a conversation; reservation reliability rules are configured separately.
View from the module · Via Palermo
05
Tasks
Make a reminder a task.
Create a callback, follow-up or reminder. Contact, reason and due date stay together. Mark tasks done; closing a visit as a no-show can create a callback automatically.
View from the module · Via Palermo
06
Preferences
Remember the little preferences.
Elena likes a window table. Store the preference in a note and maintain contact details and permitted communication channels. Recorded allergy information is a note, not a guarantee about a dish.
View from the module · Via Palermo
LidoOS Copilot
No AI in this module
No AI in this module
The CRM uses fixed rules to link contacts and events. It does not generate conversation notes or recommendations with AI.
You maintain contacts, notes and tasks yourself.
The system only knows what has been recorded or passed on by a connected module.
CRM ↔ POS
NovaPOS
Connected, with clear limits.
POS voucher redemptions can reach the shared event log through the bridge. This does not automatically link every till receipt to a CRM guest.
The till maintains its own guest profiles; a general sync with these CRM contacts is not established.
Tickets and vouchers have their own booking and customer flows. An event in the log does not necessarily appear in Elena’s contact timeline.
Reservations, calls and other modules supply contacts or events. The dashboard shows what reaches your CRM. Open contacts, incoming numbers and tasks from here.
Turn a number into a contact.
Elena calls about a family evening. Add her name and link the number. Phone and email help you find contacts again; a name search alone does not establish a unique identity.
Look back before you call.
Elena’s timeline shows completed reservations and the next callback task. Linked calls remain traceable. See what happened without searching through several screens.
Find the relevant guests.
Filter by frequent visits, a long absence or missed visits. Segments follow recorded events. They do not replace a conversation; reservation reliability rules are configured separately.
Make a reminder a task.
Create a callback, follow-up or reminder. Contact, reason and due date stay together. Mark tasks done; closing a visit as a no-show can create a callback automatically.
Remember the little preferences.
Elena likes a window table. Store the preference in a note and maintain contact details and permitted communication channels. Recorded allergy information is a note, not a guarantee about a dish.
What you need to get started
For restaurants that want to recognise guests on the next call or visit: history, preferences, reliability and open tasks in one place.
CRM is part of every package. It only knows what is recorded in LidoOS or handed over by a connected module. Caller recognition needs the telephony connection, segments need maintained reservations.
The limits
A history cannot read minds.
Ask about preferences you do not know. People with the same name are not automatically the same guest. A saved contact does not mean you have permission to send marketing.
Packages
CRM is included in every package.
CRM is part of Starter, Professional and Enterprise. Current terms are in the shop.
In every package
Starter
CRM included
Professional
CRM included
Enterprise
CRM included
How would you like to look after your guests?
Describe your workflow and the contacts you want to find again.
Not automatically. A CRM contact is a guest record, not a consent. Marketing needs the newsletter opt-in on the contact; CRM shows it but does not decide it.
Where do CRM contacts come from?
From reservations, incoming calls via telephony, prediction game entries, vouchers and tickets. Each module writes an event to the ledger; a contact exists once a person is assigned.
What does the segment “risky” mean?
It groups guests with repeated no-shows. Reservations then apply the reliability check, such as a confirmation in advance. You set the rules in the reservation settings.
Does the team see the same contacts in the till?
No. LidoOS POS keeps its own guest profiles. There is no general sync with CRM contacts; tickets and vouchers have their own flows.
All names, numbers and visit histories shown are fictional demo content from Via Palermo.
Build the right setup for your business.
Your plan, enabled modules and limits define the scope. The shop shows current terms. We plan connections to POS, devices and external services with you.
