When a chatbot should become a workflow
People keep pasting the same thing into the same box. That is the signal that a conversation has become a process, and should stop being a conversation.
Here is a pattern worth recognising. Someone in your company opens a chat window every Tuesday, pastes the week’s orders, types roughly the same instruction, and copies the result into a spreadsheet. They have been doing it for two months.
That is no longer a conversation. It is an undocumented process running on a person’s memory, and it should be converted.
The four signals
- The same instruction, repeatedly. If someone has typed a variant of the same request more than ten times, the instruction is a specification and belongs in a system.
- The output goes somewhere fixed. Always the same spreadsheet, folder or system. That destination is the second half of a workflow.
- Only one person knows how. The phrasing that makes it work is in their head. When they are on holiday, the task does not happen.
- The result gets checked less and less. The most important signal, and the most dangerous. Familiarity erodes verification; a process with an explicit check does not.
What converting actually means
Not necessarily software. Converting can mean three different things, in increasing order of effort.
Write the instruction down. Save the prompt in a shared document with a note on what it is for. Costs nothing, removes the single-person dependency, and is where most SMEs should stop.
Make it a saved, shared template. Most business AI tools support this. Now the wording is consistent and improvements benefit everyone.
Make it run without being asked. A workflow tool picks up the input, calls the model, puts the result where it belongs, and tells a person it is ready. This is worth it when the volume justifies it — and only then.
The one thing that must survive the conversion
The check. A person pasting into a chat window at least reads the answer before using it. An automated version can run for weeks without anyone looking closely.
So when you convert, move the review from implicit to explicit: something a person actively confirms, and a record that they did. If you cannot name who checks the output of an automated step, you have not automated a process. You have hidden one.