Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Chatbot Script Builder — Intents to MVP Conversation Flow

    1

    Unlike free bot-script prompts: an MVP vs phase-2 intent map, happy path, fallback, human handoff, data fields and a build + QA checklist.

    $4

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Chatbot Script Builder — Intents to MVP Conversation Flow

    Chatbot Script Builder — Intents to MVP Conversation Flow

    Example session with this skill installed

    business: Urban Oasis Gym
    channel: instagram
    primary_goal: Book trial classes and answer membership pricing FAQs
    audience: Local fitness enthusiasts
    integrations: Google Sheets (user-stated)
    tone: Energetic and helpful

    • Read your context and instructions
    • Compiled the chatbot script builder

    I have generated the chatbot intake and script outline for Urban Oasis Gym on Instagram. This document focuses on the trial booking flow and pricing FAQ intents.

    Chatbot intake & script outline: Urban Oasis Gym

    Channel: Instagram
    Primary goal: Book trial classes and answer membership pricing FAQs
    Audience: Local fitness enthusiasts
    Generated: 2026-10-19 · Discovery draft for human / client verification

    1. Discovery summary

    • Business context: Local boutique gym looking to automate top-of-funnel lead capture.
    • Problem the bot should reduce: Manual effort responding to repetitive pricing DMs and booking requests.
    • In scope / out of scope: In-scope: Trial booking, pricing FAQs, opening hours. Out of scope: Class rescheduling, billing disputes.
    • Assumptions: Google Sheets will act as the temporary database for trial bookings.

    2. Open discovery questions

    1. What specific data points are needed for a trial booking (Name, Email, Phone)?
    2. Are there specific time slots for trials, or is it any scheduled class?
    3. Should the bot notify a staff member immediately upon a booking?

    3. Intent map

    IntentPriorityTrigger examplesOutcome
    Book TrialMVP"trial", "free pass", "book"Triggers booking flow
    View PricingMVP"cost", "membership", "price"Displays tier breakdown
    Gym HoursMVP"open", "times", "schedule"Provides operating hours
    Human SupportMVP"help", "talk to person"Escalates to Inbox
    Class TypesPhase 2"yoga", "hiit", "pilates"Lists class descriptions

    4. Script outline (MVP)

    4.1 Entry / greeting

    "Hi there! Welcome to Urban Oasis Gym 🌿. Ready to smash your goals? I can help you book a free trial or check our membership rates."

    4.2 Happy path — Book Trial

    • Bot: "Awesome choice! What's your full name to get started?"
    • User: [Name]
    • Bot: "Got it, [Name]. And which email should we send your pass to?"
    • User: [Email]
    • Bot: "Perfect. Final step: Which day this week works best for you?"

    4.3 Fallback

    "I didn't quite catch that. You can say 'Pricing' or 'Trial' to get started, or 'Help' to talk to the team."

    4.4 Human handoff

    "Transferring you to one of our trainers now. They'll be with you in the Instagram Inbox shortly!"

    4.5 Closing / opt-out

    "See you at the gym! To stop receiving messages, just reply 'STOP'."

    5. Data to collect

    FieldRequired?Where stored (placeholder)Notes
    Full NameYesGoogle SheetsFor check-in desk
    EmailYesGoogle SheetsFor marketing follow-up
    Preferred DateYesGoogle SheetsTo manage capacity

    6. Integrations (user-stated only)

    • Google Sheets: Used for logging trial bookings and lead data.

    7. Handoff & escalation rules

    ConditionActionOwner placeholder
    User asks for 'Help'Notify via IG InboxFront Desk Team
    Specific pricing objectionTag as 'Lead' in Google SheetsSales Manager

    8. Build & QA checklist

    • Copy approved in energetic brand tone
    • Intents covered for MVP (Trial, Pricing, Hours)
    • Handoff tested to Instagram Professional Inbox
    • Opt-out / stop keywords functional
    • Google Sheets integration verified
    • Analytics events agreed (Lead conversion tracking)

    9. Suggested next step

    Review the trial booking flow with the Front Desk team to ensure all required fields are captured before building the Google Sheets connection.

    Next steps

    • Review the Data to Collect table to ensure no mandatory CRM fields are missing.
    • Confirm the list of pricing tiers to be included in the Pricing FAQ intent.
    • Finalise the notification trigger for the Front Desk team upon a new booking.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Unlike free "write me a chatbot script" prompts that return one long dialogue, this skill gives you the build spec: which intents ship in the MVP and which wait for phase 2, the fallback and human-handoff lines, every data field the flow collects, and a QA checklist. It never invents conversion rates and only lists integrations you name.

    Sample output (excerpt; input: Urban Oasis Gym, Instagram DMs, goal = book trial classes + answer pricing FAQs, Google Sheets):

    IntentPriorityTrigger examplesOutcome
    Book TrialMVP"trial", "free pass", "book"Starts booking flow
    View PricingMVP"cost", "membership", "price"Shows tier breakdown
    Gym HoursMVP"open", "times", "schedule"Gives opening hours
    Human SupportMVP"help", "talk to person"Escalates to IG Inbox
    Class TypesPhase 2"yoga", "hiit", "pilates"Lists class descriptions

    Happy path: Bot asks name, then email for the pass, then preferred day this week. Fallback: "I didn't quite catch that. Say 'Pricing' or 'Trial', or 'Help' to talk to the team." Data to collect: Full name (required, Google Sheets) · Email (required) · Preferred date (required, for capacity) Open questions: Which time slots are open for trials? Should staff be notified on every booking?

    You get 9 fixed sections every time: discovery summary, open questions, intent map, script outline (greeting, happy path, fallback, handoff, opt-out), data to collect, integrations, escalation rules, build + QA checklist, next step. Works for WhatsApp, Instagram, Messenger and Telegram bots.

    Works in Claude Code, Cursor and Codex · no invented stats or ROI · v1.0, updated Oct 2026 · questions answered via Agensi messages within 24h · More Cygnix Labs tools: https://apify.com/cygnix_labs

    Discovery calls for chatbot projects often result in messy notes and vague scopes. This skill forces structure onto the intake process, transforming business goals and channel constraints into a professional discovery document and script outline. It eliminates guesswork by mapping intents, handoff rules, and data requirements before you touch a low-code builder or write a line of code.

    What it does

    • Standardises discovery by generating a structured intake frame based on business context, channel, and primary goals.
    • Maps intents with a prioritised table of user triggers and expected outcomes for MVP and phase 2.
    • Outlines scripts for the happy path, fallback loops, and human handoff scenarios across WhatsApp, Telegram, or Messenger.
    • Identifies data requirements by listing necessary CRM fields and consent placeholders to collect during the flow.
    • Generates build checklists to ensure copy, QA, and technical integrations are verified before launch.

    How it works

    1. Input your client's business profile, target channel, and primary goal (e.g., lead gen or support deflection).
    2. Review the generated open discovery questions to close information gaps with the stakeholder.
    3. Use the intent map and script outline to align the client on the bot's conversational flow.
    4. Execute the build and QA checklist to track progress from development to deployment.

    Frameworks & tools

    Optimised for builders using WhatsApp Business API, Telegram Bot API, Instagram, or Messenger. Works alongside tools like Shopify, HubSpot, and low-code platforms like Voiceflow or ManyChat.

    Why this beats prompting it yourself

    Generic prompts often hallucinate unrealistic ROI metrics or conversion rates that you cannot guarantee to a client. This skill is strictly scoped to process and templates, ensuring you deliver a professional, honest technical specification without marketing fluff.

    Use cases

    • Scoping a WhatsApp lead capture bot for a real estate agency.
    • Creating a support deflection script for a Shopify merchant.
    • Aligning a client on handoff rules and human escalation for a Telegram community bot.
    • Building a phase 1 MVP checklist for an Instagram DM automation project.

    Known limitations

    Does not provide legal advice for GDPR/compliance. Does not support trading signal bots or financial return guarantees. Requires user-supplied integration details to be accurate.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Listed1 month ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions