okeep.resto
Give a guest a reason to come back next week.
Your till knows what was ordered tonight. It does not know who is coming back on Thursday — and Thursday is where the month is won.
The same Tuesday, on both screens: her phone as the points land, and the board the order is cooked from. Names and figures are an example.
Two screens from one evening. On the guest's phone, her balance at Trattoria Nowa reads 340 earned points; a challenge the restaurant set — eight visits this season — stands at three of eight, so five are left; a free dessert is waiting in Your Rewards; and a notification tells her she earned 45 points on tonight's order. On the kitchen board, two orders are being prepared and one is ready: ticket 55040 is table service and marked urgent with one minute left, 55041 is a pickup with eight minutes to go, and 55038 is plated and waiting to be delivered.
CRM · Customers
The room was full. You still cannot name one person who was in it.
A till records the order and forgets the guest. Here every order belongs to someone, and the list writes itself.
The restaurant's own customer list: 428 guests, sorted into New, Hot, Warm, Cold and Lost. Four are shown — anna.k, a regular, last in on 6 August with fourteen orders and 340 points; guest-7f3c, who ordered from a table QR code without installing anything; marek88, cooling off since 12 July; and kasia.w, not seen since 30 May.
CRM · Challenges
You could just cut the price. Do it twice and you have taught them to wait for the discount.
So the reason to come back is a goal you set, and the reward is a dessert rather than money off every future meal.
The last step of the challenge builder, reviewing what is about to be created: the goal is the one already on the guest's phone — eight visits this season — the reward is a free dessert, given as a voucher, and it runs once, from the first of June to the end of August.
Guest app · Stories
Something changes tomorrow, and the only people who know are the ones already in the room.
A story goes to every guest who has ever ordered from you, and taps through to the dish or the reward it is about. Not to whoever an algorithm picks.
A story on the phone of a guest who has eaten here before: the first of three slides, headed "On the menu tomorrow", with a tappable area over the dish it is about.
CRM · Customer Chat
And no, you are not replacing the till.
Guests order from their phone, the order lands on the board, and questions about it are answered in the same thread. Free while we are in beta — no card, no fee per order.
The restaurant's thread with anna.k. Order 55040 sits inside it with its own progress — received, preparing, ready, done — currently preparing, beside a badge for the 45 points it earned her. Under it she asks whether the Caesar can come without anchovies, and the restaurant answers.
CRM · Dashboard
A month later, you should be able to say whether any of it worked.
Revenue, orders and the average against the month before, and beside them what the loyalty half did: points earned, points spent, vouchers bought and vouchers actually used.
It counts orders, guests and points, and nothing else. Food cost, wages and margin live in your books — this screen would only be guessing at them.
The restaurant's own dashboard over thirty days, in two rows. Money first: 38 420 zł of revenue and 412 orders, up twelve and nine per cent on the month before, an average order of 93 zł, thirty-four new customers and fifty-six returning ones — sixty-two per cent of everyone who ordered. Loyalty second: 1 208 app views from 312 people, which is more visits from slightly fewer of them; 19 210 points earned and 11 400 spent; 74 vouchers bought and 51 used.
Free. Really.
No catches. No limits. No transaction fees.
- Unlimited orders
- Unlimited team members
- All features (ordering, rewards, retention tools)
- Real-time analytics
- Customer chat
- Stories & promotions
- Mobile apps (iOS & Android)
- Web dashboard
- No transaction fees
- Free during beta
- No credit card
What happens after beta? Core features (ordering, loyalty, promos) stay free. We will add paid add-ons for multi-location networks down the road. Single-location restaurants? Free forever.
What a restaurant asks before signing up
Do my guests have to download an app?
No. They scan the QR code at the table and the menu opens in their browser. The app adds points, vouchers and notifications for the ones who want it — it is never the way in.
Does it replace my till?
No, and it does not talk to it either. Orders, guests, points and the chat live here; the till keeps ringing up what it always did. Nothing has to be migrated and nothing has to be switched off.
What do I need to start?
A computer or tablet with a browser, your menu with prices, and a phone to scan your own QR code and check it works. No terminal, no card reader, nothing to install.
How long does setup take?
The first order takes about ten minutes: create the venue, add a few items, print a service point's QR code and order from it yourself. Working through the whole getting-started list takes under half an hour.
Do points work across restaurants?
No, and that is deliberate. A guest's balance with you is yours alone — it cannot be spent somewhere else, and nobody builds a profile of your guests across venues.
What happens to points if an order is cancelled?
They come back off. Points are awarded when an order is closed and paid; a cancellation writes a compensating transaction and the balance corrects itself immediately.
Can I take an order for someone without a smartphone?
Yes. Your staff create it from the dashboard — the same order, on the same board, earning the same points. Phone orders and walk-ins do not fall outside the system.
What happens to our data?
It is encrypted in transit and at rest. Sign-in runs through Auth0, and card payments go through Stripe, so card numbers never reach our servers at all.
Tell us about a normal week in your restaurant
How guests order now, what you have already tried to bring them back, and what a full room on Saturday is worth to you on Tuesday. We answer with what okeep.resto would actually change — and what it would not.