Chatbot Flow Templates: Build Once, Reuse Everywhere

A chatbot flow template is a finished conversation (greeting, questions, conditions and hand-off) that you copy and adapt instead of building from a blank canvas. The best templates aren't just good scripts. They're built to be reused: the parts that change from one business or website to the next are easy to spot, the flow is saved as a file you can back up, and there's a short checklist for making a copy work somewhere new.

This guide gives you four starter flows, shows how to make any flow portable, and explains how to back up, import and reuse flows across websites, which matters most to agencies and businesses running more than one site.

When a template beats starting from scratch

Templates save the most time in four situations:

Your first flow. A working structure shows you what a good flow looks like before you've seen any transcripts.
A second website. If your new site serves similar visitors, most of the logic carries over. Only the wording and a few rules change.
Client work. An agency that has built a lead-capture flow once shouldn't rebuild it for every client.
Big edits. A saved copy of the version that worked lets you experiment without fear.

A template is a starting point, not a finished bot. Every flow still needs your questions, your wording and a test run with real answers. If you're designing from zero, start with how to plan a chatbot decision tree, then come back here to make the result reusable.

Four chatbot flow templates to start from

Each template below is written as steps, so you can rebuild it in any no-code builder. Words in code are the variables that store answers. Keep each flow short: three to five questions is plenty, as covered in our chatbot flow best practices.

1. Welcome and triage

Best for: any business site where visitors arrive with different needs.

Message: "Hi! What brings you here today?"
Question (buttons), saved to topic: Pricing / I need help / Just looking / Talk to a person.
Condition: IF topic is "Pricing", go to a short pricing answer and offer a person. IF topic is "I need help", ask what it's about, then go to the hand-off check. IF "Talk to a person", go to the hand-off check below. ELSE ("Just looking"), share one useful link and end.
Condition: IF agents_online is true, hand off with "Connecting you now." ELSE, explain you're offline and ask for an email.
End: "Thanks! We'll be in touch."

Change per site: the button labels and the pricing answer.

2. Lead capture with a budget check

Best for: service businesses and agencies that quote for work.

Question (buttons), saved to service: your three main services, plus "Something else".
Question (number), saved to budget: "Roughly what's your budget in US dollars?"
Condition: IF budget is greater than your threshold, go to the sales path. ELSE, go to the self-serve path.
Sales path: ask for an email "so we can send a proposal", then hand off.
Self-serve path: share a helpful next step (a guide or a price list), then offer to keep in touch by email.

Change per site: the service names, the threshold and the currency. For a deeper version with question banks by industry, see the lead qualification chatbot guide.

3. After-hours capture

Best for: small teams that aren't online all day.

Condition: IF office_open is true, go to your normal welcome. ELSE, continue.
Message: "We're closed right now. We reply from 9am on weekdays."
Question (text), saved to request: "What can we help with?"
Question (email), saved to email: "Where should we send our reply?"
End: "Got it, {{email}}. We'll get back to you first thing."

Change per site: the opening hours in the message. The office_open check stays the same, as long as each site has its own office hours set. More offline patterns are in our guide to after-hours live chat.

4. Page-aware help

Best for: sites where the pricing or contact page deserves a different opening.

Condition: IF page_url contains "/pricing", go to a pricing greeting ("Questions about plans? I can help you choose."). IF page_url contains "/contact", go straight to the hand-off check. ELSE, go to your welcome and triage steps. Put this condition first in the flow, so it runs before the greeting.

Change per site: the URL paths. This is the rule most often broken when a flow moves to a new website, because every site names its pages differently.

Make a flow portable before you reuse it

A flow that works on one site can fail quietly on another. These habits make the copy easy to adapt.

Name variables for what they hold

Use short, lowercase names such as budget, team_size and email, not question_4. Whoever adapts the flow later can then read every condition without opening each step. If you collect contact details, save them to the standard names (name, email, phone) so they reach the contact's profile. Our post on chatbot variables covers naming in more depth.

Mark what must change

Put the site-specific parts in obvious places: the business name in the greeting, prices, opening hours, URL paths and budget thresholds. Some teams keep a "master" version with bracketed placeholders, like "[Business name]" or "[hours]", so nothing slips through unchanged. Placeholders are easy to spot when you test; they only reach visitors if you skip the test.

Keep button labels and rules in sync

Button labels are what a condition compares. If one site's button says "Pricing" and another says "Plans and prices", a rule written for the first won't match the second. When you rename a button, update every rule that checks it, then test that branch again.

Prefer built-in variables to hard-coded facts

A message that says "We're online until 6pm" is wrong on a site with different hours. A condition on office_open or agents_online adapts by itself, as long as each site has its own office hours and team.

Back up a flow before every big change

Most no-code builders let you export a flow as a file. Make it a habit:

Export before you edit. Save the file with the site and date in the name, for example acme-triage-2026-11-09.json, so you can tell versions apart.
Keep the files in one shared folder, next to a one-line note on what changed and why.
Make the change, then test every branch with different answers.
If the new version performs worse, import the backup and switch back.

A backup costs a minute. Rebuilding a flow from memory after a bad edit costs an afternoon, and you rarely get it exactly right.

Move a flow to another website

Moving a flow is mostly the same as restoring a backup, plus a few checks. The flow file carries the conversation itself: the steps, questions, answer types, variables, rules and messages. Settings that belong to the website, such as office hours, the team, the widget and any AI knowledge, live in the destination and must be set up there.

After-import checklist

Run through this before you switch the copy on:

Check	Why it matters
Business name, prices and hours in every message	The most visible mistake a reused flow can make
`page_url` rules	Page paths differ between sites
Budget thresholds and currency	One client's "big project" is another's small job
Button labels and the rules that check them	A renamed button breaks its branch silently
Office hours and team on the new site	`office_open` and `agents_online` only work if they're set up
AI answer steps	The new site needs its own knowledge base and a plan that includes AI
Every branch tested end to end	The only way to catch a step that leads nowhere

A note for agencies

If you build chat for clients, treat your best flows like any other reusable asset. Keep one master file per flow type (triage, lead capture, after-hours), adapt a copy for each client, and keep the client's version in their folder. When you improve the master, say by shortening a question that people kept skipping, you can roll the improvement out to each client the next time you review their flow. Reading a client's real transcripts still comes first: no template knows their customers better than their conversations do.

How to do this in RetroChat

RetroChat's flow builder includes three templates to start from: Welcome & triage, Lead capture and Contact form. You can also start blank or import a file. The Import and export flows guide includes a complete sample flow for a fictional bike shop that you can import and adapt, with a quick-reply menu, a budget condition, an AI answer step and an "is anyone online?" check before the hand-off.

Export: open Chatbot, open the flow's menu and choose Export. You get a JSON file named like welcome-triage.retrochat-flow.json.
Import: open Chatbot, click Import, choose the file and name the flow. RetroChat checks the file first, leaves out anything it can't use and lists any problems so you can fix them in the builder.
Importing never replaces a flow. It always creates a new one. Only one flow is active at a time, so you can test the copy with Test and press Activate when it's ready. Activating it switches the others off.
Built-in variables such as agents_online, office_open, returning_visitor, page_url and country work in conditions without asking the visitor anything. See Variables and conditions.
Plans: Starter includes one chatbot flow with up to 15 steps. Team and above include unlimited flows and steps, so you can keep a backup copy next to the live one. Business and Autopilot support multiple websites. AI answer steps need the Business or Autopilot plan, or AI replies left in your trial; without them, the step hands the visitor to your team instead.

Start with one template

Pick the template closest to what your visitors need, adapt the wording, test every branch and export a backup the day it goes live. You can try the built-in templates and the sample flow in a free 14-day RetroChat trial, no credit card required. Running chat for several sites or clients? Book a demo to see how it would work for you.

Frequently asked questions

What is a chatbot flow template?

It's a ready-made conversation, with its greeting, questions, conditions and hand-off already connected, that you copy and adapt instead of starting from a blank builder. A good template marks clearly which parts you need to change, such as the business name, prices and opening hours.

Can I reuse the same chatbot flow on several websites?

Yes, if your tool can export and import flows. Export the flow as a file, import it where you need it, then update the site-specific parts: messages, page-based rules, thresholds and office hours. Test every branch before you switch it on.

How do I back up a chatbot flow?

Export it as a file before every significant edit and keep the files in one folder with dated names. If a change performs worse, import the backup and switch back. In RetroChat, importing creates a new flow and never overwrites the one you're running.

What doesn't carry over when I import a flow?

The flow file holds the conversation itself. Settings that belong to the website, such as office hours, the team, the widget's look and any AI knowledge base, have to be set up on the new site. Check them before you activate the imported flow.