A Telegram bot that takes the routine off your support desk
Account look-ups, order and payment status, setup instructions, renewal reminders — answered in Telegram at any hour, without anyone on your team typing the same reply again.
We built one for our own subscription business first and then turned it into a service. It is not a chat widget bolted onto a website: the bot talks to the system you already run, so what it tells your customers is your real data, not a scripted guess.
What it actually does
- Account linking. A customer connects their account once, and from then on the bot knows who is asking and answers only about them.
- Answers from your own data. Balance, order status, next payment date, what their plan includes, when it expires.
- Instructions on demand. The same setup guides and documents your team currently sends by hand, delivered in seconds.
- Notifications triggered by events. Payment received, subscription about to expire, request answered — pushed to the customer instead of waiting to be asked.
- Three languages if you need them. English, Russian and Lithuanian are already built in; another language is a translation job, not development.
- A clean handover to a person. When the question is not something the bot should answer, it collects the detail and passes it to your team rather than improvising.
Where it saves staff time
Most support time goes on a short list of questions that repeat all day. Those questions are the ones a bot answers well, and they are also the ones that keep a trained person from the work only a person can do.
- Repeat questions handled without a person. Status, balance, instructions, what is included — the answers that are identical every time.
- Cover outside office hours without a shift. Evenings and weekends get the same answers as Tuesday morning.
- Fewer conversations that go cold. A customer who gets an answer in seconds does not open a second request about the same thing.
- Less copying between systems. What the bot records lands in your system directly, so nobody re-types it afterwards.
It will not halve your support team, and we will not claim it does. What it removes is the twentieth identical reply of the day — and that is usually a large share of the desk.
Three situations, three very different jobs
- Your system has a documented API. Odoo, a CRM, a billing platform. The bot reads and writes directly, and the price is fixed.
- Your system has no API. Spreadsheets, an old admin panel, a desktop program. The integration has to be built around what exists — scheduled exports, a small intermediate database, sometimes automation at screen level. That work is quoted, not priced from a list.
- You have no central system yet. The bot is still useful on its own: menus, instructions, contact routing, notifications you send when you need them.
We tell you which of the three you are in on the first call, before you pay for anything.
What it costs
- Bot without integration — £850. Menus and texts in up to three languages, deployment on a server, testing, handover and fourteen days of support.
- Bot with no-code integration — £1,200. Everything above, plus a connection to your system through scheduled exports or a no-code layer where a direct interface is not available.
- Bot with API integration — £1,400. Everything above, with the bot reading and writing in your system directly: accounts, orders, payments, event notifications.
- System without an API — from £950, quoted. There is no honest fixed price here: the figure depends on what your system allows, and we give it after looking.
- Care — £95 per month. Monitoring, updates, changes to texts and buttons, a monthly report on what the bot was actually asked.
- Care Extended — £195 per month. Everything in Care plus hosting on our Managed VPS, so there is no separate server line to pay.
- Work beyond Care — £85 per hour. New scenarios and new integrations are charged by the hour; text and button changes are not.
Bot setup and integration Monthly Care
Prices exclude the cost of any AI model you choose to add — see below.
Where it runs, and who pays for what
- On our Managed VPS. Care Extended at £195 per month includes the hosting, so nothing is added on top.
- On a server you already have with us. Then the bot goes onto the machine you already pay for and there is no second hosting bill.
- On your own server. Equally fine — we deploy there and keep the access arrangements documented.
- If you want the bot to answer with an AI model, it runs on your own OpenAI or Anthropic key. You hold the key, you see exactly what it spends, and we do not resell usage to you at a margin.
What we do not sell
- We do not support your business software itself. We look after the bot, the server it runs on and the connection between them. The programs your company runs stay with their own suppliers.
- We do not promise a bot that answers everything. A bot that guesses is worse than no bot — the honest design is a short list it answers well and a fast handover for the rest.
- We do not move your customers' data anywhere new. The bot reads the system you already run; it does not build a second copy of your database somewhere else.
How the build goes
Step 1
A short call
What the bot must answer, and what it must never touch.
Step 2
Integration check
We look at your system and confirm which of the three situations you are in, with a price.
Step 3
Build and test
Bot, texts, integration, tested on your own data with a small group of users first.
Step 4
Handover
Published, your team shown how to change texts, fourteen days of support included.
Tell us what your team answers all day
Book a free thirty-minute consultation. We will look at the questions that actually repeat in your support, and say plainly whether a bot is worth it for you.