Draft a Customer FAQ Chatbot Script

Create a comprehensive FAQ chatbot script for [product name], a [one-sentence product description]. This script will be loaded into our AI chatbot (Intercom Fin or similar) to handle the most common customer questions without human intervention.

Our product details:
- Pricing tiers: [list your tiers, e.g. "Free, Pro at $29/mo, Team at $79/mo"]
- Free trial: [yes/no, length]
- Key features: [list 3-5 core features]
- Integrations: [list major integrations]
- Support hours: [e.g. "9am–6pm ET, Mon–Fri"]

Write responses for these FAQ categories:

**Getting started (5 questions):**
Cover account creation, initial setup, importing data, inviting team members, and the first thing a new user should do. Each answer should be 2-3 sentences max with a link placeholder like [link:getting-started-guide].

**Billing & pricing (6 questions):**
Cover plan differences, how to upgrade/downgrade, billing cycle, refund policy, what happens when a trial expires, and how to cancel. Be transparent and non-defensive about cancellation — make it easy.

**Feature-specific (5 questions):**
Cover the top 5 features users ask about. For each, explain what it does in plain English, who it's for, and which plan includes it. Include a [link:feature-doc] placeholder.

**Troubleshooting (4 questions):**
Cover login issues, slow performance, data not syncing, and a generic "something isn't working" catch-all. Each answer should have a quick fix first, then an escalation path.

**Escalation & handoff (3 scripts):**
Write the chatbot's response when: (1) it can't answer a question, (2) the customer is frustrated or asks for a human, (3) the issue involves billing disputes or account security. Each handoff should feel warm, not robotic — acknowledge the issue and set a time expectation for human response.

Format rules:
- Write in second person ("you"), friendly but professional
- Keep answers under 60 words where possible
- Use bullet points for multi-step instructions
- Include [link:page-name] placeholders for documentation links
- Add a confidence tag to each answer: [high-confidence], [medium-confidence], or [needs-review]
- End each answer with a follow-up question: "Did that help?" or "Anything else I can help with?"