A delivery bot and CRM in ten days
How a kitchen in Batumi moved lunch orders out of chat and into a Telegram bot and a dashboard, and what we built on each of the ten days.
On this page
A Telegram bot for orders and a web dashboard for the kitchen. The bot went live on the first day, the order board on the second, weekly orders on the third. By day ten the system covered the whole routine, from publishing the menu to delivering the sets.
The routine we automated
The kitchen delivers set lunches in Batumi: soup, a main and a salad, one price for every day, Sunday off. Every day runs the same way. Publish the menu, collect orders before a cutoff, cook the right number of sets and get them to the right addresses.
Orders used to arrive in chat, so each one had to be retyped before anyone could cook or deliver it. That retyping was the first thing to go.
What the client sees
Clients order in a Telegram bot. The week’s menu arrives as one post with a button for each day and one for the whole week, and photos of the available days come as an album. A client then:
- picks a day or the whole week;
- chooses the number of sets and cutlery;
- leaves an address.
Orders for a date close the day before, at a time the owner sets. Every day at 12:00 Batumi time the menu for the day after tomorrow goes to everyone who had a delivered order in the last seven days.
What the owner sees
The owner works in a web dashboard. Requests land on a board with five columns, from new to delivered.
An order moves through the statuses in a set order and cannot skip a step, and a double tap in the bot never creates a second order. Rejecting, cancelling or a failed delivery asks for a reason.
The menu lives in a monthly calendar. A day can be dragged to another date, and if that date is taken the two menus swap, photos included. Staff get their own role in the bot with today’s orders to pack and deliver.
Ten days, day by day
| When | What shipped |
|---|---|
| 3 Oct | We write the bot’s spec, and the bot goes live the same day, with backups from the start. |
| 4 Oct | The order board, clients, statistics and broadcasts. |
| 5 Oct | Orders for the whole week. |
| First weekly order | A rule change: accepting one day accepts the whole week, and the client gets a single confirmation. |
| Day 10 | The system covers the whole routine: clients order lunch in a few taps, and the owner sees what to cook today and where it goes. |
Try it yourself
The live demo shows the dashboard on fictional data. The order board and the menu calendar work right in the browser.
Questions
How long did it take?
Ten days for the whole system. The bot itself went live on the first day, and the order board on the second.
Can the owner change the menu without a developer?
Yes. The menu lives in a monthly calendar in the dashboard; a day can be dragged to another date, and on a taken date the two menus swap, photos included.
Do couriers need a separate app?
No. Staff get their own role in the same bot, with today’s orders to pack and deliver.
Can I try it?
Yes. The live demo shows the dashboard on fictional data, and the order board and the menu calendar work in the browser.
ZabSoft is a software company in Batumi. The person who scopes your project is the person who builds it.