Moving from a chatbot flow builder to an AI agent: what each node becomes, what to keep, and what to drop
Menus disappear, button questions become qualifying fields, fixed answers become documents, prices move to the catalogue and "talk to an agent" becomes a handover rule — node by node, with help rebuilding it from a screenshot of the old flow.
Moving from a flow-builder chatbot to an AI agent is not redrawing the flowchart in a new tool — most of the flowchart disappears. Menu branches become the questions the agent must get answered, fixed answers become catalogue entries and documents, "talk to an agent" nodes become handover rules, and keyword triggers are no longer needed because the agent reads the message. Send us a screenshot of your old flow and some past conversations, and we will build the agent and its workflows from them with you.
On this page
Why the flowchart does not come across as a flowchart
A flow builder decides what to say by where the customer is in a drawing. An AI agent decides by what the customer said, what it still needs to know, and the rules it may not break. So a 40-node flow is usually five or six facts the business needs before a quote, a dozen answers, three reasons to hand over and a follow-up schedule. The rest of the nodes existed to route a customer through a menu they never wanted.
Node by node
| In the old flow | Becomes | Where it lives |
|---|---|---|
| A menu: "1 for pricing, 2 for booking" | Nothing — the agent reads the question | — |
| "What is your budget?" with buttons | A qualifying field the agent asks for and records | The qualification fields |
| A fixed answer: timings, address, policy | A document or a saved reply | Knowledge, saved replies |
| A price typed into a node | A product with a price | The catalogue — the only place prices live |
| "Talk to an agent" | A handover rule, by topic or request | Rules |
| Keyword triggers | Not needed; quick-reply buttons where taps are faster | Buttons |
| A tag set on a branch | A field, a score, or a lifecycle stage | Fields, scoring rules |
| "Assign to sales team" | A routing workflow | Workflows |
| A drip after no reply | A follow-up cadence or a campaign | Follow-ups, campaigns |
| An order or payment step | A payment request at the catalogue price | Payments |
What to keep from the old bot
- The questions that decided a quote. If your flow asked city, date and headcount before anything else, those are the agent's qualifying fields.
- The answers customers actually needed. Look at which branches people reached most; those answers become documents.
- Every place a person took over, and why. Those are the handover rules.
- The welcome message, if it worked — rewritten as a sentence, not a menu.
What to drop
- Menus. A customer who wrote "how much for 50 people on Saturday" should not be sent "Reply 1 for pricing".
- "Sorry, I didn't understand." The agent asks a question back or hands over.
- Branches nobody reached. The analytics in most flow builders show which; delete them rather than translate them.
We will build it from a screenshot and your chats
Rebuilding is easiest from the two things you already have: a screenshot or export of the old flow, which shows what you meant the bot to do, and some real conversations, which show what customers actually asked. Send both — customer numbers removed — and we will map the flow to goals, fields, rules and workflows and set up the agent with you. Get in touch.
If you would rather do it yourself: onboarding builds a first version from your website and documents, and the agent editor takes changes in plain sentences — "ask for the event date before quoting", "hand refunds to a person", "send hot leads to Anuj".
Can I import my chatbot flow into Linkubit?
Not as a file — an AI agent is not a flowchart. Send us a screenshot of the flow and we will rebuild what it did as the agent's questions, rules and workflows.
Will an AI agent say things my old bot never would?
Its rules are enforced in code: it quotes only from your catalogue, hands over on the topics you name, and a verifier checks every reply before it is sent. See the rules guide.
Can I keep buttons?
Yes. Quick-reply buttons still help where a tap is faster than typing — a date, a yes or no — and the agent sends them when they fit.
Read next
More on Switching to LinkubitLinkubit vs other toolsWhatsApp templatesCost calculatorPricing
Try it on your own number. Linkubit answers, qualifies and quotes on WhatsApp from your catalogue, and adds nothing to Meta’s per-message price. Start free — fourteen days of Pro, no card — or read the pricing.