Marketing and CRM: bringing guests back automatically
Acquiring a new guest costs many times more than bringing back an existing one — and the return path is usually not automated at all. In Delever, marketing runs on operational data.
CRM and segments
The pain: your customers belong to the platform. You don't know who ordered, what they like or how to bring them back — which means you pay commission on every one of their next orders.
The guest profile holds order history, average check, favourite dishes, branch and channel. From this, behavioural segments are built: new, regular, lapsed, VIP — as ready-made lists, not a spreadsheet export.
The segment then becomes the audience for a campaign: push, SMS and Telegram messages go to a segment, not the entire base. That is the difference between a campaign and spam — and the difference in unsubscribes, which end up costing more than the campaign itself. The section lives under “Marketing → Customer tracking”.
Promos, banners, pop-ups and stories
The pain: every banner and every promotion is a task for a developer, released by the end of the week, while the occasion often lasts three days.
Promotions, pop-ups, banners and stories are created in the panel and appear in every channel at once — in the app, on the website, in the bot. The editor is multilingual: any language can be added when needed, on one screen, without duplicate cards.
The active period is set by a schedule: a promotion switches on and off by itself. Launching a promotion requires no development tasks. Section: “Content → Promotions / Pop-up / Banners / Stories”.
Triggers and automation
The pain: an abandoned cart is forgotten, the guest never got an order status, and nobody remembered their birthday.
Triggers are set up once and then run on their own. Order statuses — accepted, being prepared, courier on the way, delivered — go out by SMS and push automatically. An abandoned cart is followed up with a message, and a lapsed guest gets a reason to come back. Birthdays and loyalty-accumulation mechanics fire on events, not on the marketer's memory.
A separate scenario is the late order: if an order goes over the standard time, the guest gets a message before they start calling themselves. Section: “Marketing → Triggers”.
Reviews and quality
The pain: feedback is collected by hand and gets lost, while negativity goes to social media where everyone can see it.
Every review is tied to an order: you can see the branch, the courier and the order number — sorting it out takes minutes, not a back-and-forth between managers. Reviews are handled on a kanban board: new, in progress, resolved, closed without resolution — nothing is left hanging.
Filters by rating and branch show exactly where quality is dropping, rather than “things have generally got worse”. This is also material for operations: if complaints are concentrated on one branch in the evening hours, the problem is not the kitchen in general but a specific shift. Section: “Marketing → Review management”.
Loyalty, promo codes and referrals
The loyalty programme lives inside your own channels: points, tiers and bonuses are earned for orders in the app, the bot, on the website and in the dining room — not in a separate card system that has to be reconciled by hand.
Promo codes and discounts are configured in the panel: per item, per category, per channel, per period. A referral programme gives guests a reason to bring a friend, and gives you a growth channel that doesn't cost a pay-per-click budget.
Cashback and deposit wallets reach the POS correctly: service fees, surcharges and bonuses don't break the end-of-shift reconciliation — this is part of the 40+ synchronisation options configured between Delever and your POS.
Notifications and Telegram
The pain: the manager finds out about a problem when the guest is already calling to complain.
Every new order, with its items, total and channel, arrives in the branch's Telegram group. Failure alerts go there too: POS unreachable, payment failed, order stuck. Guests' personal data is hidden in notifications.
Setup is by role and branch: who receives which events. The owner gets a morning digest, the branch manager gets failures at their location, the marketer gets campaign results. Nobody has to open the admin panel for this.
Frequently asked questions
Where does the customer base come from if we used to work through aggregators?
The base starts growing from the first day your own channels are live: the app, website, bot, QR menu and call centre. Aggregator orders are visible in the system too, but the platform doesn't give you the guest's contact details — which is exactly why you need your own channels. After a few months of operation a chain usually already has a segment of regular guests it can work with directly.
Which channels are messages sent through?
Push in your app, SMS and Telegram. Push is the cheapest channel: it costs nothing per message, so it usually becomes the main one for promotions and statuses, while SMS is kept for those who don't have the app installed.
Do we need a dedicated marketer for this to work?
Triggers are set up once and then run on their own — statuses, abandoned carts, birthdays. Promotions and banners can be launched by anyone from the panel, without development tasks. A dedicated marketer is needed not to launch things but to come up with reasons to reach out.
Can campaigns be run separately for each branch?
Yes. Segments and campaigns are filtered by branch and channel, and permissions are set so that a branch manager works with their own location. A promotion can be switched on in one city and off in another.
How does this relate to the loyalty programme in the POS?
Delever loyalty works at the platform level and is shared across all channels. With two-way exchange with the POS, discounts, bonuses, cashback and deposit wallets reach the POS correctly, so the shift reconciliation always matches.