Chatbot Marketer

---
name: chatbot-marketer
description: Use conversational marketing — chatbot strategy, conversation design, lead qualification bots, and messaging ROI.
category: business-marketing
---

## Overview

Chatbots and conversational marketing meet buyers in real-time conversations: answering questions, qualifying leads, booking meetings, and guiding purchases — 24/7. This skill covers chatbot strategy, conversation design, lead qualification flows, and measuring conversational ROI.

The principle: be helpful first, capture second. Bots that interrogate before helping get closed.


Chatbots and conversational AI compress the funnel: instead of forms and landing pages, prospects get answers and take action inside a conversation. The best implementations feel like talking to a knowledgeable rep, not navigating a phone tree. Design for resolution and conversion, not for showcasing AI capabilities.
## When to use

- Adding chat to a website for lead generation
- Designing chatbot conversation flows
- Qualifying leads conversationally
- Reducing support load with bots
- Building Messenger/WhatsApp marketing
- Measuring chatbot performance

- Qualifying website visitors outside business hours
- Deflecting repetitive support questions
- Guiding users through complex product selection
- Capturing leads from high-traffic blog content
- Running conversational quizzes for product matching
- Providing instant answers in paid landing pages
## Core concepts

**Use-case clarity.** Define the bot's jobs: lead qualification, meeting booking, FAQ deflection, product guidance, or order support. One bot doing five jobs does none well. Start with the highest-volume, highest-value use case.

**Conversation design.** Write like a helpful human, not a form: one question at a time, short messages (under 40 words), quick-reply buttons for common answers, graceful handling of unexpected input, and always a path to a human. Test flows with real users — designers can't predict confusion.

**Qualification flows.** Conversational BANT: need ("what are you trying to solve?"), fit (company size, role), timeline, and contact handoff. Progressive: earn information by giving value first. Route hot leads to humans immediately — don't make them finish the flow.

**Playbooks by page.** Different pages, different intents: pricing page (offer help comparing plans), blog (offer related resources), high-intent pages (proactive outreach after 30–60 seconds). Match the playbook to visitor intent.

**Human handoff.** The moment of truth: pass full conversation context, set expectations ("connecting you with Maya, our specialist — typical wait 2 minutes"), and never make users repeat themselves. Failed handoffs destroy trust faster than no bot at all.

**Messaging channels.** Website chat, Messenger, WhatsApp, Instagram DMs — meet customers where they are. Each channel has norms (WhatsApp = personal, keep it concise) and rules (opt-in requirements, template restrictions for business messaging).


**Conversation design principles.** One question at a time; offer quick-reply buttons instead of open text where possible; always provide an escape to a human; confirm understanding before acting ("Just to confirm, you want..."); handle the unhappy path (confusion, profanity, edge cases) as carefully as the happy path. Test with real users — designers cannot predict how people actually type.

**Handoff design.** The bot-to-human transition is where most implementations fail: pass full conversation context (never make the user repeat themselves), set expectations ("Connecting you with Maya from support, ~2 min wait"), and route by intent and language. A graceful handoff beats a clever bot.

**Lead qualification flows.** BANT or CHAMP adapted for chat: 4–6 questions max, quick replies over free text, progressive disclosure (ask the next question only when the previous is answered).
Chat-qualified leads convert 2–3x better than form leads because the conversation builds micro-commitment.
Always offer "talk to a human" — forcing bot completion loses hot leads.
**Proactive triggers.** Time-on-page, scroll depth, exit intent, and return-visitor detection trigger contextual invitations ("Questions about pricing? I can help.").
Trigger too early and you annoy; too late and they are gone. Test trigger timing per page type — pricing pages warrant faster triggers than blog posts.
## Practical workflow

1. **Pick the use case.** Analyze: where do visitors drop? What questions repeat? Start with one high-impact flow (e.g., pricing-page qualification).
2. **Design conversations.** Map the happy path + top 3 detours per flow. Write in natural language. Add quick replies, fallback responses, and human-escalation triggers (frustration signals, complex questions, high-value visitors).
3. **Build playbooks.** Per key page: trigger conditions, opening message, qualification questions, routing rules, and follow-up for missed chats. Keep opening messages helpful, not pushy.
4. **Integrate.** Connect to CRM (log conversations, create/update records), calendar (meeting booking), marketing automation (nurture for not-ready leads), and alerting (hot lead → instant Slack/email to owner).
5. **Launch and monitor.** Soft-launch on high-traffic pages. Watch: engagement rate, completion rate, qualification rate, handoff success, CSAT. Read actual transcripts weekly — they reveal confusion and opportunities.
6. **Optimize.** A/B test opening messages and CTAs. Expand to new use cases once the first works. Prune flows with low completion. Update answers as products change.

**Transcript review checklist:** where do users drop? What unexpected inputs recur? Do handoffs include context? Is the tone right for frustrated users? Are quick replies covering 80% of responses?


**Use-case prioritization:** list candidate conversations → score by volume (how often does this happen?) × value (conversion or deflection impact) × feasibility (can the bot resolve it reliably?) → build top 3 first. Start with high-volume, low-complexity wins (hours, pricing, order status) before attempting complex sales conversations.

**Analytics that matter:** containment rate (% resolved without human) → CSAT for bot conversations → conversion rate vs. control → fallback rate (how often the bot fails) → top failed intents (your build backlog). Review failed conversations weekly — they are the roadmap.

**Build checklist:** define the single goal per bot (qualify, book, support — not all three) → script the happy path → script the 5 most common detours → add human handoff → test with 10 real users → soft launch on one page → review transcripts weekly → expand.
Transcript review is the ongoing work — user language evolves and flows decay without it.
## Common pitfalls

- **Interrogation before value.** Asking for email in the first message. Give help first, earn the contact.
- **No human escape.** Trapping users in bot loops. Always offer a human, especially after two failed attempts.
- **Over-automation.** Bots handling situations needing empathy (complaints, complex issues). Know the bot's limits.
- **Generic playbooks.** Same popup on every page. Match to page intent.
- **Ignoring transcripts.** Never reading what users actually say. Weekly transcript review is the optimization engine.
- **Slow human response.** Bot promises help; humans take hours. Staff the handoff or don't offer it.
- **Compliance blindness.** Messaging regulations (opt-ins, quiet hours, template approvals on WhatsApp) vary by channel and region. Know the rules.
- **Pretending to be human.** Deceptive bots destroy trust when discovered. Identify as automated upfront; users do not mind bots, they mind being tricked.
- **No human fallback.** Trapping frustrated users in bot loops. Always offer a human exit, prominently.
- **Launching without training data.** Bots trained on imagined conversations fail on real ones. Seed with actual chat transcripts and support tickets.
- **Too many questions.** 15-field interrogations in chat form. Every question costs completion — ask only what changes the outcome.
- **Dead-end conversations.** Flows that end without a next step. Every conversation ends with value delivered or a clear handoff.