An order through an aggregator stays with the aggregator, not with you
When a guest orders through a delivery app, they pay the platform, not you directly. The platform saves their phone number, address, and order history in its own database. You only see the order for the kitchen - sometimes a name, never a number. When the same guest wants to order a week later, the platform will also recommend the place next door.
- Payment goes to platform
- Guest phone number stays with platform
- Order history in platform database
- Re-contacting guest — via platform
- Payment goes to you
- Guest contact goes to your CRM
- Order history in your database
- Re-contact — your decision and your RODO responsibility
Your own ordering channel works differently. A form on your website or a link in your Google Business Profile saves the guest's contact directly to your CRM. You decide whether to write to them with a new communion menu or invite them to a tasting. Guest data stays with you and is subject to GDPR - this is your responsibility and your control over who sees it.
Pages from which inquiries don't come at all are described in the analysis of Warsaw business websites.
40 out of 181 Warsaw restaurants have no place of their own for inquiries
They have no place of their own where a guest could leave an inquiry.
For the owner, this means the same thing: without your own address for inquiries, these 40 venues have no way to collect contact details outside the platform.
Guest's journey to the table: phone → form → CRM → kitchen → report
An inquiry about a reservation or takeout order comes today through four channels at once: phone, form, Messenger, and Instagram. A well-structured process looks like this:
- 01phone or form
- →02CRM
- →03task for the floor manager
- →04confirmation to the guest
- →05report at the end of the day
Each inquiry lands in one place, regardless of the channel it came through.
This assumption is based on our practice in implementations for gastronomic venues, not on market research. If after a month inquiries from Messenger and Instagram still disappear without the floor manager's response, the sequence isn't working. Then you need to check the integration, not hire another person for the mailbox. The indicator to watch is the number of inquiries waiting longer than an hour without an assigned responsible person.
More about connecting phone, form, and messengers into one process can be found in the channel integration service.
Who handles it: floor manager, CRM, and supplier integrations
The inquiry itself is usually handled by the floor manager - they confirm the reservation and assign a table. The waiter receives a ready order from the system and doesn't need to ask who called and about what. CRM combines all submissions into one list, and integration with WhatsApp or Messenger automatically adds messages from messengers to it.
- Phone
- Form on page
- Messenger
- Google Business Card
- CRM — single ticket list
- Task for hall manager
- Guest confirmation
- End-of-day report
For passing submissions between the form, CRM, and the kitchen's mailbox, n8n works well - an automation tool that connects these systems without manual re-typing. The Google Business Profile listing is another source of submissions that needs to be connected to the same queue, otherwise inquiries from there get lost separately.
Integration can break after an API update on the delivery platform or messenger side. The symptom is always the same: submissions stop reaching the CRM, and the floor manager learns about the reservation only from the guest's phone. This is fixed by a system administrator who checks integration logs, not the waiter or reception.
More about connecting reservations, suppliers, and reviews into one process is in our article about reservations, suppliers, and reviews under control.
How much your own online ordering channel costs
A lead form that collects inquiries about reservations or catering takes the inquiry in. Inquiry automation — rules that direct submissions to the right person — carries it onward. CRM automation and integrations with Telegram or WhatsApp close the road to the person who answers. Each of these links without the next one ends the same way: the inquiry sits there. The scope is settled after a conversation about how your inquiry process works today.
The scope of the form that collects such submissions is described in the lead form service.
The table reservation system is the next stretch of the same road. You add it when the guest should see available times online themselves. The report that shows the floor manager how many inquiries are waiting without a response closes that chain. Decisions about staffing are then made based on data, not one person's memory. The order varies and depends on where the order stalls today — the scope is settled after a conversation about your needs.
We don't promise an increase in orders or a specific return on investment - no one can honestly guarantee that. What we do guarantee is that the guest's contact will go into a system that is yours, not someone else's.
When your own channel is a bad idea
A one-person café with two tables and a regular clientele doesn't need CRM or inquiry automation. A phone and a reservation notebook are enough as long as the owner handles all submissions themselves. Investing in a system makes sense only when inquiries come from several channels at once and someone starts forgetting about them.
The same applies to a venue that consciously operates only through aggregators and doesn't want to build its own brand. If orders from the delivery app fully cover kitchen capacity, adding another channel only distracts the team. Before you start building your own channel, check whether your kitchen has any spare capacity for additional traffic.
Five situations where we ourselves recommend against starting are collected in a separate article about failed implementations.
Questions we hear most often
Can orders through aggregators be connected to your own CRM?
Yes, if the platform provides export or email notification about the order, it can be pulled into CRM through integration. However, the guest's contact usually remains restricted by the platform's terms and cannot be downloaded directly. That's why we treat the aggregator as an additional sales channel, not a source of your own guest database.
Do I need my own website to collect reservation inquiries?
Not necessarily. A lead form can be embedded on a Google Business Profile listing or on a landing page, without building a full website. What matters is the place where the submission goes, not the website itself.
What happens to guest data when they use the form on the website?
The data goes to your CRM and is subject to GDPR just like any other contact database. You are responsible for who you share it with and how long you store it. This differs from ordering through an aggregator, where the platform administers the data.
Do I have to give up aggregators to have my own ordering channel?
No. Your own channel works alongside aggregators, not instead of them. The aggregator remains an additional source of traffic, and your own CRM remains the place where you collect the contact details of those guests who came to you directly.
Will the form replace the phone in the restaurant?
It won't replace it, because some guests will always choose a conversation, especially for larger reservations for a wedding or communion. The form takes over inquiries that today get lost outside the dining room's business hours. The phone and the form work together, each receiving the submission that fits the guest's situation.
Let's talk about what your restaurant can start collecting from the very first inquiry.