To build a chatbot flow without code, plan the welcome, questions and handoff before opening the editor. Each message needs a purpose: explain what the customer can do, ask for a useful detail or show the next action. A conversation becomes difficult when the bot keeps asking questions without helping the customer move forward.
Imagine Emma asking a shop in Lisbon about a linen shirt. She needs to choose a size, check collection or delivery, and see how to order. If she asks about exchanging an earlier purchase, she needs a different path. Sketch those conversations before choosing the blocks.
Build a chatbot flow without code: start on paper
Choose a familiar request that your team already handles well. Write the customer's likely opening message at the top of a sheet. Under it, draw the answer, the next question and the point where the conversation can finish. Label each branch with the answer that leads there.
- The purpose: help a shopper choose a shirt and reach the order step.
- The necessary details: size and whether they want collection or delivery.
- The normal ending: the relevant product and a clear way to order it.
- The human route: an existing order, a complaint or a request you cannot confirm.
Check each question against the purpose. If knowing the answer would not change the next reply, remove the question. Leave unrelated requests for a later flow.
In Kwamle Media, connect your business's own account through the channel's official login or API. Use a channel that supports the flow and follow its current messaging rules for conversations customers start. Open Bot Builder, choose New Bot and start from a template or a blank canvas. Arrange the steps to match your paper plan.
Welcome the customer and ask one question at a time
Use Send Message for a welcome that explains the help available. Keep it close to what someone at your counter would say, while making clear that the opening reply is automated.
Hello. This is the shop's automated assistant. Would you like help choosing a shirt or with an existing order? You can also ask for a person.
Then use Ask Question to collect and save a detail, and Condition to choose the next branch from the answer. Ask about size before asking about collection or delivery. A shopper should be able to answer the message in front of them without remembering a list of earlier questions.
On the paper plan, make the branches concrete:
- If the customer chooses collection, explain the collection arrangements you actually offer.
- If they choose delivery, ask which area they need before giving the relevant delivery information.
- If the answer does not fit either choice, clarify the request or let a person help.
Keep the wording distinct. "Collect from the shop" and "Delivery" are easier to understand than "Option A" and "Option B". Do not treat an unclear answer as agreement. If the customer changes their mind, check the corrected detail before continuing. Use a Tag User step only when a label such as "collection" will help your team recognise the request later.
Put rules and saved answers before AI
Write the answers your team can stand behind before adding generated replies. Opening hours, collection arrangements and your delivery policy need consistent wording. Keep those answers current when the business changes them.
The reply order is rules first, then saved answers, then AI. Use AI Reply for open questions, guided by the tone, language and instructions you set in AI Studio. Prepare the content in this order:
- Rules: decide which familiar requests should get a fixed response and which need a person.
- Saved answers: write the checked information the customer needs, including the next action.
- AI instructions: explain the business's tone, what information it may use and when to ask the team for help.
For example, a question about collecting a shirt should get your established collection information. A question about the fabric may suit an AI reply if you have supplied those details. A request for a special delivery arrangement needs someone who can confirm it. Do not let a fluent answer stand in for a fact you have not checked.
Show the product and make the handoff clear
Show the item once you have enough information to make it relevant. Include the product name and the size or colour being discussed, so the customer can check it. Offer a clear next action, such as continuing to checkout or asking for help with the choice. A product card should answer the customer's question before asking them to buy.
Link your Kwamle Media store to the bot and use Send Message to show a product card with photos and product options. Offer a checkout or payment link in the conversation; payments use the gateway your business connects. When a person is needed, a team member can take over in the unified inbox, read the history and continue in the same chat. The bot stays quiet while that person replies.
Decide who on your team handles complaints, changes to an existing order and requests outside your normal offer. Explain that a person will review the request, and describe your team's actual availability without promising an immediate reply. Ask the colleague taking over to read the earlier messages and acknowledge the unresolved question. The customer should not need to start the conversation again.
Test the flow as a customer
Try the conversation from the customer's side on a phone. Ask a colleague who did not write it to do the same. Watch where they hesitate, what they misunderstand and whether they know what happens next.
- Follow the normal purchase path through to the product and checkout link.
- Try both collection and delivery, and check the answer shown for each.
- Give an unexpected answer, then correct a detail you supplied earlier.
- Ask for a person before finishing the questions, and try a complaint midway through.
- Check that the colleague taking over can read the history and that the bot stops replying.
Fix the first confusing step and try that path again. Read the messages aloud as well: wording that feels awkward in a conversation usually needs shortening. Repeat the relevant checks when you change a product, policy or branch.
Keep the useful path short
Return to the paper plan after testing. Remove greetings that repeat, questions whose answers you never use and product details that distract from the next action. Keep enough context for the customer to understand where they are and how to reach a person.
Use the no-code chatbot flow builder guide to turn the plan into steps. For the words inside those steps, read automated replies that sound human. Start with the conversation you can explain clearly, then expand it only when real customer questions show what is missing.
