Chatbot Conversation Flow Designer

Automation-ready v2.0

Chatbot Conversation Flow Designer

automationautomation readychatbotconversation-designcustomer supportUX
ChatGPTClaudeGemini⚠ Human review required📁 Needs project context🔌 MCP-ready⚡ Automation-ready
Health 100/100 18 📋 135 copies

Trigger Phrase

Run automation: Chatbot Conversation Flow

Prompt

141 words
# Automation Ready: Chatbot Conversation Flow Designer

You are a conversation designer.

Inputs:
- Business/service: [business/service]
- Main use case: [main use case]

Design a flow: 1) welcome message 2) decision branches with the user inputs that trigger them 3) a fallback response 4) a human-handoff path.

Constraints:
- Cover the unhappy path and an explicit handoff; no invented integrations.
- Structured as a branching flow.

Output: a chatbot conversation flow.

## Output Contract
Clear markdown with headings, concise sections, checklists where useful, and a final action-ready output.

## Guardrails
Do not execute high-risk actions without a human approval checkpoint. Output must be structured and predictable. Log or flag unexpected inputs rather than guessing. Do not invent statistics, prices, laws, medical claims, or financial advice. Do not leave placeholders unfilled in output. Flag when inputs are too vague to produce a quality result — ask for clarification.

Before & After

❌ Without this prompt

Unstructured request with unclear constraints and inconsistent output.

✅ With this prompt

Reusable, testable prompt/skill with clear trigger, inputs, output format, guardrails, and pass criteria.

Install Instructions

Install the skill component first. Map the trigger phrase to your automation tool (Make, n8n, Zapier). Connect inputs and outputs as described. Set a human approval checkpoint before high-risk outputs. Test end-to-end before going live.

Test It

Test command:
Trigger manually with a test input. Confirm structured output matches the expected schema before connecting automation.
Expected output:
Welcome: "Hi! What do you need - [A] order help [B] returns?"
A -> ask order # -> status. Fallback: "Let me get a human." -> handoff.
Pass criteria:
  • Output is structured and machine-readable. Trigger phrase reliably produces the expected output format. Human approval point is clearly flagged before high-risk actions.

⚠️ Guardrails

  • Do not execute high-risk actions without a human approval checkpoint. Output must be structured and predictable. Log or flag unexpected inputs rather than guessing. Do not invent statistics, prices, laws, medical claims, or financial advice. Do not leave placeholders unfilled in output. Flag when inputs are too vague to produce a quality result — ask for clarification.

📁 Context File Tip

Business Context file

⚠️ Common Failure Modes

  • May become generic, over-confident, miss constraints, over-automate, or produce output that needs fact checking.

🔧 Fix Prompt

Tighten the goal, add examples, add constraints, specify the output format, and ask the model to list assumptions before final output.

🎛 Available Modes

Quick Detailed Critic Final

🔌 Compatibility & Requirements

✅ Works offline
📁 Needs project context
👤 Needs human approval
Approval point: Before publishing, sending, spending money, changing systems, or making commitments.
Required tools: Automation builder

⚡ Automation

n8n | Make | Zapier

📋 Upgrade Notes

Upgraded for Prompt Hub Pro v9.9.5 scoring, skill metadata, importer compatibility, and reusable agent/workflow presentation.

💡 Suggest an improvement

Install Wizard

Choose your platform to get step-by-step install instructions: