Flow and scenario updates
New products, new pricing, a seasonal offer, kept in the bot’s flows as the business changes, not left stale until someone notices.
CARE · BOT MAINTENANCE
Bots need maintenance too, just not the plugin kind
Custom builds need less maintenance because there are no plugins to update. A bot is different: the business behind it keeps changing even when the code does not, and the flows need to keep up with it.
WHAT'S INCLUDED
Four things that drift if nobody watches them
Each one is a business change reaching the bot, not a code problem.
Catalogue and pricing kept in sync
What the bot shows a customer matches what is actually being sold, not a snapshot from whenever it was last updated.
Platform changes absorbed
WhatsApp and Telegram both change their APIs and policies over time. That is tracked so the bot keeps working without the business having to watch for it.
Handover routing reviewed
Who a conversation escalates to changes as the team changes. Routing is reviewed rather than left pointing at someone who left months ago.
OR EDIT IT YOURSELF
The console exists so you do not need this
Bot maintenance is for when you would rather we make the changes than your own team.
Every bot we build ships with a management console and a scenario editor your own administrator can use directly, no code required. Bot maintenance as a care plan is the alternative for teams who would rather hand the updates to us instead of doing them in-house.
See the bot management console
Scenario editor, conversation queue, and analytics, built in.
HOW IT'S PRICED
Quarterly, like all care plans
Scoped by how many flows and channels are involved, the same way the original build was.
Bot maintenance is billed quarterly, the same cadence as every other care plan. It is scoped individually rather than published as a flat figure, since a single-channel bot with a handful of flows is a different job from one running across WhatsApp and Telegram with a full catalogue.
How website care plans are priced
Around
STRAIGHT ANSWERS
Questions about bot maintenance
The ones that come up once a bot is close to launch.
Because the business behind it changes even when the code does not. New products, new pricing, a seasonal offer, a different handover contact, all of these need the bot’s flows updated to match, which is a content and scope task rather than an infrastructure one.
Yes. The scenario editor in the bot management console lets your own administrator make those changes directly, no code and no developer required. Bot maintenance as a care plan is for when you would rather we handle the updates directly, on an agreed schedule, instead of doing it in-house yourselves.
That is absorbed as part of maintenance. Both platforms change their APIs and policies over time, and keeping a bot working through those changes is exactly the kind of thing a plugin-free custom build still needs someone actively watching for and adjusting.
Quarterly, like all care plans. It is scoped by how many flows and channels are involved, the same way the original bot build was, rather than a single flat figure applied regardless of complexity or how much actually changes each quarter.
Building a bot? Maintenance is scoped once it ships.
There is no need to decide on ongoing maintenance before a bot is built. We revisit it at handover, once you know how many flows and channels it actually runs.
Bot maintenance sits alongside care plans and managed hosting as part of what keeps a system running after launch.