Write the scope first
- Who it is for: support, alerts, internal tools, or a Mini App
- Commands, buttons, and conversation flow
- Whether it talks to your existing backend
- Who creates the token, where it is hosted, and whether you get source
Rate limits, duplicate callbacks, and a leaked-token revoke are engineering items. They belong in acceptance, not in “send it again”.
Typical shapes
Support Q&A, order or stock alerts, menu-driven internal tools, and Mini Apps that need a login. Each has a different conversation depth and hosting note — “build a bot” is not a quote.
Long-tail lines
Telegram机器人定制开发TG客服机器人开发Telegram Mini App定制订单通知机器人Bot API WebhookTelegram机器人源码交付
FAQ
How is it priced?
By features and calendar time. Say the use case and whether you need a Mini App.
Do we get source?
If the acceptance note says so. Tokens are not left in the chat.
