Request via Telegram
The user chooses a service, answers questions and leaves a contact for a manager.
Bots and AIfor business
Telegram bot development
for business.
We'll build and launch a Telegram bot for your task: collecting requests, guiding the user through an agreed scenario and passing inquiries to a manager. We'll consider other messengers after checking what connection options are available.
Discuss a Telegram botfrom $200
Let's start with one clear task
These are examples of possible tasks, not completed client projects. For the first launch, we choose one main scenario.
Answers from your materials
The bot explains terms through set branches or, using AI, from confirmed information.
Event notification
A separately agreed scenario reports an event from a connected system; we check access and channel rules in advance.
How wework
How a scenario might work
An example for discussion. We define the sources, actions and human involvement for your task before development.
Start of the dialogue
The user starts the bot and chooses the service they need.
Clarification
Answers questions along the agreed branch.
Contact
Provides the required details; the bot validates the planned fields.
Handoff
The manager receives the inquiry by the chosen method.
Next step
The bot reports that the request was passed on. Calendar booking or payment requires a separate integration.
02 / 04
Scripted bot or AI: we choose based on the task
A scripted bot guides users through set steps and buttons. It suits cases where you need to choose a service, collect contacts and pass on a request. AI isn't required for that.
The AI consultant answers free-form questions based on the materials provided. The client confirms current services, prices, products and terms. We set and test the rules: don't make up facts, say when information is missing and offer a connection with a person. The model can make mistakes; we don't promise error-free operation or full replacement of a manager.
We'll build and launch the agreed scenario
03 / 04
The base scope includes one main task, the dialogue structure and messages, creating and connecting the bot, agreed materials for AI, request collection and one way of passing it to a manager. It also includes two rounds of compiled revisions within the approved scope, testing, launch, access and short instructions.
CRM, calendar, catalog, order statuses and other actions are separate integrations. We'll check for a suitable ready-made solution, permissions and cost before promising a feature. Collecting a request doesn't mean a confirmed booking, an accepted order or a completed payment.
We agree on the checks before development
We define test cases and expected behavior in advance. At handover we check them on the finished solution; these are criteria for the future work, not results already achieved.
- The agreed dialogue branches and delivery of the request to a manager.
- An answer based on the materials and a message to the user about the outcome.
- A question outside the knowledge base and conflicting information, with no unconfirmed promises.
- Invalid contacts and repeated submission.
- Unavailability of a connected service and the planned error handling.
- Handoff to a person by the chosen method and refusal of actions outside the agreed permissions.
An estimate for your task
from $200
Tell us what problem you need to solve and what result you want. After we discuss it, we'll agree on the scope of work, a fixed price and a deadline. A detailed technical specification isn't required for your first inquiry.
If we need to study the process in detail, review sample materials or check connections, we'll agree in advance on a paid assessment and its deliverable: a solution outline, the boundaries of the work and an estimate. The assessment is paid in full before it starts. You can receive it as a standalone deliverable; if you order the implementation, the payment is credited toward the total price.
Terms of
work.
Implementation and running costs are separate
We subtract the already paid assessment from the total agreed price. The remaining amount is split: 25% before implementation and 75% after the result is checked. The assessment is not paid for twice. We estimate additional scenarios and scope changes before work begins.
Platform subscriptions, the AI model, API, hosting, storage and paid connections are billed separately. Before the start, we'll show the expected costs for the agreed number of requests or operations and state our assumptions. Costs may change as the load grows; we'll set up limits and notifications wherever the service allows it.
Launch, handover and fixes
We'll hand over the working agreed scenario, client access and short instructions. Where possible, accounts are registered in your name. Acceptance is recorded by your dated confirmation in the agreed channel. For 30 days from confirmed acceptance, we fix errors in our implementation free of charge, within the agreed scope.
New tasks, material updates, adapting to changes in third-party services and ongoing support are estimated separately. If the planned failure handling was implemented incorrectly by us, that is our error. Website support plans do not automatically apply to bots and automation.
If the project is handed over without further maintenance, you revoke our permissions and change the passwords and keys known to us, following a list. We record what was handed over, ask for confirmation and remove our own access where we can. For agreed ongoing support, we keep only the necessary permissions.
Before launch.
Questions and answers.
Do I need to provide a ready-made bot?
No. We'll build and launch a bot for the agreed task. We'll discuss creating accounts and the necessary access before we begin.
Does a Telegram bot need AI?
Not always. A scripted bot is enough for steps, buttons and collecting contacts. Answers to free-form questions about the materials can use AI.
Is a request already a calendar booking?
No. Booking, payment and changing an order require separate integrations, permissions and verification of the result.
Can a CRM be connected?
We'll check for a ready-made integration and the actions needed. We'll agree on the scope, price and behavior on failures before work begins.
Which messengers are available?
The main starting channel is Telegram. We'll consider other channels after checking the platform's requirements, the account and the capabilities of the chosen solution.
Who changes the scenario after launch?
We'll hand over access and instructions. New branches, materials and support are discussed separately; we fix our errors within 30 days of confirmed acceptance.
Other tasks
Describe your task in your own words
Describe the process, website or channel, the systems you use and the result you need. We'll discuss sample documents and access later in an agreed channel. Don't send passwords, keys or confidential materials through a public form.
Discuss a Telegram bot