Upgrades · Build on an existing bot
Keep your existing bot useful as needs change.
Is something broken, or has the current flow become too limited? Start with the code, runtime and access permissions. The work might be a focused change or a larger upgrade, depending on what the existing project allows.
What changes can be assessed?
Examples include investigating a recurring fault, changing buttons or permissions, adjusting business rules, adding a notification flow or discussing a spreadsheet, website or system connection. Each depends on the current implementation. Integration assessment starts with interface documentation, fields and authorization.
Current projects focus on Telegram. Other platforms, older frameworks and externally maintained code need an initial review. If source code is unavailable, the possible approach must be reconsidered; screenshots alone are not enough to promise a direct modification.
Give the change a clear boundary.
- Current behavior
- Record the trigger, observed behavior and expected result. Separate bug fixes, rule changes and new features.
- Code and data
- Identify affected modules, permissions and data handling. Where migration is needed, agree backup, migration checks and recovery arrangements before making the change.
- Delivery and release
- Agree the scope of changed source, configuration or notes. Specify who deploys and accepts the change, including existing flows that need to be checked during testing.
Useful information for an assessment
- The bot’s purpose, platform and current usage.
- Steps that trigger the issue, errors or screenshots with sensitive details removed.
- Whether source and runtime access are available, and whether the original maintainer is involved.
- The existing features to preserve and your most urgent change.
Who maintains it afterward?
You can continue running it yourself or return it to your existing maintainer. Source delivery, deployment, fault handling and future feature changes are agreed individually for the project.
Discuss ongoing maintenance separately if needed. For a project that has not started, see custom development.
Questions before commissioning
- Can you take over if the original developer has stopped maintaining it?
- We first review the source, runtime and permissions. Without source code, available interfaces and data determine the options; screenshots alone cannot establish that a direct change or takeover is possible.
- How are existing user data and workflows preserved?
- List the data and flows to retain, then agree backups, migration checks and recovery arrangements. Acceptance checks cover both the changes and the existing essential flows.
Describe what happens and what should change.
Start with the most important adjustment and the code or runtime information you can provide.