---
name: chatbot-conversation-flow-designer
description: "A chatbot conversation flow with branches, fallbacks and human handoff, laid out as a decision tree ready to build on your platform. Use when a team needs a chatbot conversation flow with branches, fallbacks and human handoff for a given use case and platform. Do not use for building the chatbot in code or writing a long FAQ knowledge base. Related topics: customer support, automation, chatbot."
---

# Chatbot Conversation Flow Designer

A chatbot conversation flow with branches, fallbacks and human handoff, laid out as a decision tree ready to build on your platform.

## When to use

Use this skill when a team needs a chatbot conversation flow with branches, fallbacks and human handoff for a given use case and platform. Do not use it for building the chatbot in code or writing a long FAQ knowledge base.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Write a greeting for each entry trigger that states what the bot can do.
3. Map each main branch as bot message, user options and next node, keeping each path to about four steps.
4. Add a fallback for unrecognised input and a limit on retries.
5. Define the escalation message and the context passed to the human if handoff is on.
6. List the data captured along each branch and check every path ends in a resolution or handoff.

## Inputs

- **Primary use case** (choose one: Customer support FAQs, Lead qualification, Appointment booking, Product recommendation, Order status, Complaint handling, Onboarding, Sales)
- **Industry** (free text, e.g. "E-commerce or SaaS or Healthcare")
- **Platform** (choose one: Website widget, Facebook Messenger, WhatsApp, Slack, Custom integration)
- **Entry triggers** (choose any: Website page visit, Time on page, Exit intent, Manual click, Post-purchase, After sign-up)
- **Main branches** (longer free text)
- **Escalate to a human** (choose one: Yes, No)
- **Escalation trigger** (choose one: Customer request, Bot cannot answer, High-value lead detected, Complaint detected, After 3 failed attempts)
- **Tone** (choose one: Professional, Friendly, Playful, Minimalist)
- **Bot name** (free text, e.g. "Aria or Max or no name")

## Output

An indented decision-tree outline with bot lines in the chosen tone, followed by a list of captured data fields.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Chatbot Conversation Flow Designer

Design a chatbot conversation flow.

- Primary use case: {{Primary use case}}
- Industry: {{Industry}}
- Platform: {{Platform}}
- Entry triggers: {{Entry triggers}}
- Main branches: {{Main branches}}
- Escalate to a human: {{Escalate to a human}}
- Escalation trigger: {{Escalation trigger}}
- Tone: {{Tone}}
- Bot name: {{Bot name}}

Design the flow as a decision tree. Write the greeting for each trigger, then each branch as a sequence of bot message, user options and next node, capped at about four steps from entry to resolution. Use quick-reply buttons where the platform supports them. Add a fallback for unrecognised input that offers the menu, and the handoff message and data passed to the human if escalation is on. Write all bot lines in the chosen tone. Return the tree as an indented outline, then a list of the data the bot should capture.

## Pitfalls

- Branches that dead-end with no resolution or handoff.
- Free-text prompts everywhere, when buttons would keep users on the happy path.
- A handoff that loses the conversation context, so the customer repeats themselves.
