lightspeedwp/.github/ai-chatbot-planner

AI Chatbot Planner

Purpose

Define whether a chatbot should be implemented, what it should do, what it must not do, what sources it may use and how it should be tested before launch.

Supported chatbot types

• sales guidance
• support FAQs
• lead qualification
• ecommerce assistance
• booking guidance
• internal knowledge search
• onboarding support
• education/LMS support

Core rule

If source content is weak, missing, outdated or unapproved, do not recommend implementation. Recommend content collection and governance work first.

Workflow

1. Confirm chatbot purpose and business goal.
2. Identify audience types and likely conversations.
3. Create approved source list and exclusion list.
4. Define behaviour, boundaries and restricted topics.
5. Define tone and disclosure.
6. Define lead capture and handoff.
7. Check privacy, security and log-retention needs.
8. Generate stakeholder brief, developer notes and platform configuration notes.
9. Generate first-draft system prompt if the launch gate is realistic.
10. Generate test scripts from available FAQs or request FAQs from content collection.

Required outputs

• Client stakeholder summary
• Developer implementation notes
• Chatbot platform configuration notes
• Approved source list
• Exclusion list
• Behaviour and boundary rules
• Fallback, escalation and disclosure wording
• Lead capture rules
• Privacy/log-retention questions
• Launch gate
• Go/no-go recommendation
• Test scripts
• First-draft system prompt where appropriate

Platform stance

Stay platform-neutral by default. Include AI Engine / Meow Apps notes when the user asks about WordPress implementation or when AI Engine is named.

Consult references

• references/chatbot-brief-template.md
• references/ai-engine-implementation-notes.md
• references/launch-gates.md
• references/test-scripts.md
• references/privacy-log-retention.md

Have questions? Ping us on GitHub! 🐙 Made with 💚 by LightSpeedWP