From the first message to a conversation with your team.
Telegram bots for business enquiries, agreed response flows and conversations on behalf of your company. We help you choose the right format, build the logic and connect it to your website.
A client chooses a service, receives prepared answers and shares the details of their project. Your manager receives a structured enquiry and continues the conversation through the agreed channel.
Start → choose a service → questions → contact details → enquiry to your team
This is a menu with agreed logic and prepared answers. It does not use AI to make up responses.
02BOT FOR TEAM CONVERSATIONS
Talk to clients on behalf of your company.
A client messages your company’s official bot. The message reaches a private workspace, where enquiries are separated into conversations. Your manager replies, and the client receives a message from the company’s bot.
This is the format behind HOVER’s own implementation, shown below.
03WEBSITE CONNECTION
Connect your website to your working channel.
A / Open the bot
A website button opens a conversation with your bot in Telegram. The conversation takes place in Telegram, rather than inside the browser.
B / Receive form enquiries
A website form sends an enquiry to your manager in Telegram when that integration has been agreed and built. A form notification does not, by itself, create a two-way conversation.
A simple link and a backend form integration have different scopes. For an existing website, we review access to its code / CMS and compatibility with its current tools.
03 / HOVER’S OWN IMPLEMENTATION
One bot for the client. Separate conversations for the team.
We built HOVER’s own communication channel in Telegram. Clients contact the studio’s bot, while the team handles each enquiry in a separate conversation within a private workspace. A manager’s reply reaches the client on behalf of HOVER.
This is the studio’s own implementation, rather than an external client project.
Workflow illustration. Sample messages.
01 /
A client messages HOVER’s official bot on Telegram. They see a single, ordinary conversation with the studio.
The enquiry reaches the private HOVER | CLIENT INBOX working group, in a separate internal conversation for this client.
The manager uses Reply on the client’s message. The response reaches the client from HOVER.
What the client sees
One conversation with the studio’s bot
HOVERstudio bot
ILLUSTRATION
Client message
Hello. We need a landing page for a new product. Could we discuss the project?
HOVER
Hello! Of course. Please tell us about the product and what you want visitors to do on the page.
How the manager works
A separate internal conversation for the client
H
HOVER | CLIENT INBOXprivate working group
ILLUSTRATION
#A separate internal conversation for the client
Client message
Hello. We need a landing page for a new product. Could we discuss the project?
Reply → response to the client
ClientHello. We need a landing page…
Hello! Of course. Please tell us about the product and what you want visitors to do on the page.
Message direction
Client
HOVER bot
Working conversation
Manager’s Reply
Client
Clients do not join the working group. The team handles each enquiry in a separate conversation.
Reply reaches the client. Notes stay with the team.
The manager uses Reply on a client’s message in the relevant internal conversation. This sends the response to the client through HOVER’s bot. Ordinary messages posted without Reply remain internal notes.
Enquiries arrive in the private HOVER | CLIENT INBOX working group. Each client has a separate internal conversation; other clients do not join this group.
Want to contact the studio?
This opens our working bot. Your message will reach the studio, and a person will reply.
We first agree on the task, conversation flow and how enquiries will reach your team. This defines the scope of development, integration and launch; additional features are discussed separately.
What the work includes:
Discussing your task and choosing the format
Designing the agreed conversation flow
Menus, messages and navigation logic
Setting up enquiry delivery
Building the agreed functions
Connecting a website entry point
Checking workflows and error cases
Deployment
A short usage guide
Agreed separately:
Additional workflows and languages
Multiple teams / working groups and extra roles
Support for different file types
CRM connections or other external APIs
Changes to a third-party website
Specific data retention requirements
Extended administration
Ongoing support and new functions
05 / STARTING PRICES
Two formats.A defined scope.
01ONE-TIME DEVELOPMENT
Guided bot
FROM $450
An agreed basic implementation for explaining services and collecting enquiries.
One Telegram bot for one business
One language and one menu
One main enquiry flow with up to five consecutive steps
A short set of agreed answers / FAQs
Enquiries sent to one agreed working channel
One link or button from an accessible website
Checks and launch
A short usage guide
Two-way operator conversations through topics are not included. Complex extra branches and external integrations are estimated separately.
Where will the bot run, and what do you pay for after launch?
The bot needs somewhere to run its code: cloud hosting or a compatible server. With a cloud setup, you do not need to buy a physical server or keep your work computer switched on. A separate database may be needed for operational data and the links between conversations.
One possible setup uses Vercel for the bot’s server-side logic and a separate Neon / PostgreSQL database. This is an example configuration, not a mandatory set of services for every project. We select the tools around your requirements.
01
Your cloud accounts
The default approach: the project runs in accounts you own. You control access and pay the providers directly. HOVER sets up the agreed solution and provides a handover guide.
02
Your existing infrastructure
If you already have a server or cloud project, we first check compatibility, available resources and access. Having a website or a paid hosting plan does not automatically mean it can run the bot. Any additional resources are agreed separately.
03
Hosting arranged through HOVER
This requires a separate agreement. Before launch, we define who owns the accounts, who pays the providers, what support includes and how the project can be handed over. This arrangement is not automatically included in the starting development price.
Costs & billing
Development, hosting and database services, third-party services, and support are separate budget items. Some providers offer free allowances, but we do not guarantee zero running costs: usage and commercial-use terms matter. We agree any additional accounts, provider plans and billing arrangements before launch.
Support
Ongoing support and new functions are not an unlimited free part of the starting price. Their scope and terms are agreed within the project.
Access & handover
The project also defines the hosting region, access arrangements, and responsibility for backups and recovery. Access and materials are handed over through a secure process once the work has been agreed.
06 / PROCESS & MATERIALS
Start with the task. Then shape the flow and launch.
01
The task
We define what the bot should do and who should receive enquiries.
02
The flow
We agree menus, copy, data and the limits of automation.
03
Build and check
We implement the workflow and check typical situations and errors.
04
Launch and handover
We connect the required entry points, provide a guide and agree ongoing support.
Timing is confirmed after the scope is agreed and the necessary materials are available.
What we need from you
01
A short description of the task
02
The services and questions to cover
03
Your preferred channel for receiving enquiries
04
The person responsible for replies
05
Existing brand materials, if available
06
Details of the website and systems to connect
A description of the task is enough for the first enquiry. Please do not send passwords, tokens or private data through the public form.
07 / QUESTIONS & ANSWERS
Before we begin.
08 / LET’S TALK
What should your bot help you do?
Tell us how enquiries reach you today, who replies and what you want to organise. We will suggest a suitable workflow and agree the scope of work.