Telegram & WhatsApp Bots
Telegram bots, Telegram Mini Apps and WhatsApp messaging flows built around your bookings, community or team.
Your customers have Telegram or WhatsApp open all day. A bot there can confirm a booking, answer a question, collect a form or tell staff that something needs attention, without asking anyone to install an app or remember a password. The two platforms work very differently, though, and the choice affects both cost and design.
Telegram is open: a bot is free to create, can write to anyone who has started it and can open a Mini App, a small web app inside the chat with its own screens. We build Telegram bots in Python with aiogram, with handlers, middlewares and a database behind them, or with Google Sheets when the client wants to edit content in a spreadsheet. WhatsApp goes through Meta's Cloud API, needs a verified business account, and a message that opens a conversation must use a template Meta has approved. We usually wire WhatsApp through n8n, store every message in MySQL and check the signature on each incoming webhook.
Some of our work: a Telegram Mini App for a Ukrainian community, with onboarding, a dashboard, AI help and a discovery section, used by around 300 people. A series of community bots handled moderation, menus and logging with data in Google Sheets. For a salon we built a web inbox on top of the WhatsApp Cloud API and MySQL that shows conversations, reactions and attachment previews next to the customer's bookings; when the booking database was unreachable, the inbox kept working and simply showed no booking details. One lesson: the community bot went through five separate versions, which is why we now plan bots around one shared codebase from the start.
A Telegram bot with AI answers starts from 1,000 DKK ex. VAT. A WhatsApp flow takes more setup because of Meta's business verification and template approval. Running costs are hosting, AI usage if the bot answers with a model, and on WhatsApp the message fees Meta sets and bills to your business account.
A bot is the wrong tool when your customers are not on the platform. Many Danish customers expect SMS and e-mail, and an SMS reminder reaches everyone with a phone. It is also wrong for long forms or payment flows with many steps: an ordinary web page does that better, and a Mini App only helps when people are already inside Telegram.
Key Features
Telegram Mini Apps
Small web apps that open inside Telegram with your own screens: sign-up, dashboards, catalogues, forms. Users are recognised by their Telegram account, so there is no separate login to remember.
WhatsApp Cloud API
Booking confirmations, reminders and replies through Meta's official API, with message templates prepared for approval and every message stored in a database you control.
Shared inbox for staff
A web view where staff read and answer WhatsApp conversations, see reactions and attachments, and look up the customer's bookings right next to the chat.
Moderation for groups
Join requests, rules, menus and logs for groups and channels, so volunteers or staff do not have to watch the chat around the clock.
AI answers with limits
The bot answers from your own texts and hands over to a person when unsure. A daily cap on AI usage keeps the monthly cost predictable.
Verified webhooks
Incoming WhatsApp webhooks are checked by signature, tokens are kept in an encrypted credential store instead of in the code, and workflows are backed up daily.
Why Choose This Service
Customers use the messenger they already have, which lowers the barrier to booking or replying.
Conversations, bookings and alerts sit in one shared place instead of on personal phones.
A slow or missing data source switches off one feature instead of breaking the whole chat.
Menus, texts and answers can live in a spreadsheet or a simple admin view.
How We Deliver
Our proven process ensures quality at every step
Pick the channel
We look at where your customers actually write today and what the bot must do, then choose Telegram, WhatsApp or both, and decide what stays on the website.
Set up the accounts
For Telegram we register the bot; for WhatsApp we set up the business in Meta, the phone number and the templates for approval. The accounts belong to you.
Build the flows
Commands, menus, forms and AI answers are connected to your booking system, CRM or spreadsheet, and messages are stored in a database you control.
Test on your phones
Every flow is tested on your own and your staff's phones with test data, including what happens when a connected system is down, before customers see it.
Launch and look after it
After launch we follow errors and message logs, renew tokens and update AI models; on project support this is part of a regular check.
Frequently Asked Questions
Telegram or WhatsApp: which should we choose?
It depends on your customers. Telegram is cheaper and more flexible, with free bots and Mini Apps, and suits communities and internal teams. WhatsApp is the app many customers already use to write to businesses, but it requires Meta's approval, templates and per-message fees. A common split is WhatsApp for customers and Telegram for staff alerts.
Can the bot write to customers on its own?
On Telegram only to people who have started the bot. On WhatsApp the first message must be an approved template. Either way, we switch on messages to real customers only after you have approved the wording and the timing and we have tested the flow on your own number.
Can it connect to our booking system?
Yes, if the booking system has an API or a database we can read safely. We read bookings through a read-only account limited to the tables that are needed, and the bot keeps running if that source is temporarily unavailable.
What does it cost to run?
Hosting on our servers is covered by project support from 600 DKK a month. If the bot answers with AI, model usage is billed per use and can be capped per day. WhatsApp message fees are charged by Meta directly to your business account.
Can you take over an existing bot?
Usually. We read the existing code or workflow, move passwords and tokens out of the code into a secure store and keep the same bot account, so users do not notice the move. If the bot exists in several copies, we merge them into one first.
Ready to Cross the Bridge?
Let's build your lightning bridge to digital transformation. From first consultation to live deployment — we move fast.