Price follows the workflow, not the number of buttons
Two bots with similar menus can do very different work. One collects an enquiry and sends it to a manager. Another checks availability, reserves a slot, takes payment and synchronises a CRM. Menu size alone cannot describe that difference.
Cartel Digital’s Telegram bot development starts from $300 per project for an agreed compact workflow. This is a development fee, not a monthly subscription. Hosting, paid services and ongoing support are discussed separately; the final scope is agreed before work begins.
Three scopes to distinguish
Collecting an enquiry
The user selects a service, answers a few questions and leaves contact details. A manager receives a readable message with the required fields. An estimate needs the questions, recipient, confirmation message and duplicate-handling rules. A compact workflow without complex integrations may fit the starting budget.
Requesting or booking an appointment
A request and a confirmed reservation are different outcomes. Without shared availability, a manager still needs to check the selected time. If the bot reserves appointments itself, it must handle simultaneous requests, cancellation and rescheduling.
Connecting a CRM or catalogue
The bot retrieves information from another system and sends results back. API capabilities, access permissions, data matching and failure handling affect the estimate. A service offering “integrations” does not establish that it supports your particular action.
Information to prepare
- The user’s main action and the expected result.
- Questions, answer options and required fields.
- Examples of the customer confirmation and manager notification.
- External systems and their available API documentation.
- Rules for repeated requests, cancellation and human assistance.
Describe the process in everyday language. Walking through it manually often reveals where a person must make a decision. Our enquiry bot guide can help map the first workflow.
Work that is easy to overlook
The scope includes invalid input, going back, repeated clicks and unavailable external services. Agree data storage, staff permissions and contact retention. A standard Telegram bot cannot initiate a private conversation with an arbitrary user; the person must first interact with it.
Establish who changes messages after launch, where the application runs and who maintains integrations. The owner should control the bot account and token. The token must not appear in public documents or website code.
Test the handover
Use a new account, enter invalid information and repeat a request. Confirm that the manager receives the correct information once. Test cancellation and a clear response when an integration fails. For confirmed bookings, test two users trying to reserve the same slot.
Agreed outcomes, account ownership and guidance matter more than the button count. Describe your workflow on our Telegram bot development page to establish a useful first release.
