Ordering a Telegram bot: agree on the handover
Before paying for a Telegram bot, agree on its actions, permissions and acceptance tests. Record who owns the accounts and who maintains the application. This will help you take over the result and continue work if the developer changes.
Define what happens after the reply
“The bot accepts inquiries” can mean forwarding a message, creating a CRM lead, saving a request during an outage or confirming receipt to the customer. Specify which outcomes you need.
Describe several normal conversations and a failed one, with an expected result for each. If the bot answers questions, define its source for prices and what it should do when information is missing.
Review account ownership and data access
Establish who owns the bot, server and connected service accounts. Grant the permissions each task requires. A bot that creates leads may have no reason to delete the entire database.
Store secret keys separately from source code and ordinary messages. Agree what data is stored, who can read the history and how it is deleted. If data goes to an external AI service, reflect that in the product design and customer documentation.
Separate running costs from future changes
Request separate costs for development, paid services and maintenance. For AI features, agree on a spending limit and notifications, alongside any per-message estimate.
Define who updates prices and answers, which revisions are included and what counts as a new feature. Agree on support hours and response terms explicitly.
Use a handover checklist
Check that you have what you need to continue operating the bot. A working chat alone does not provide account access or instructions. Agree on the handover before payment.
- Access to bot management and hosting on the agreed terms.
- The agreed source code and configuration, with secrets transferred securely.
- Instructions for updating prices and reference materials.
- A checked backup and recovery procedure.
- A support contact and terms for post-launch failures.
Run acceptance tests on your own examples
Go beyond the demonstration conversation. Submit a duplicate inquiry, send incomplete information, ask for a person and disable a test integration. The bot should explain its status, and the inquiry should remain available for investigation.
Ask for a recovery demonstration or a verified recovery guide. DevNomad’s starting price for an AI sales bot is 80,000 RUB; the exact scope is agreed before invoicing. Sample conversations and the desired outcome are enough for an initial discussion.