Run any Skill in Manus with one click

sales-chatbot

Chatbot marketing and conversational automation — building chatbot flows, multichannel messaging (WhatsApp, Telegram, Facebook, Instagram, Viber, live chat), lead qualification bots, FAQ bots, and handoff to human agents. Use when website visitors leaving without engaging, WhatsApp or Telegram leads not getting qualified, bot flow feels broken or confusing, leads dropping off before reaching a human agent, or not sure how to automate conversations for sales. Do NOT use for live chat widget setup without bots (use /sales-live-chat), email sequences (use /sales-cadence), or SMS campaigns without conversational flow (use /sales-sms-marketing). For SendPulse-specific help, use /sales-sendpulse. For SWAI-specific help, use /sales-swai.

Run Skill in Manus

Overview

Install command

npx skills add https://github.com/sales-skills/sales --skill sales-chatbot

Copy and paste this command into Claude Code to install the skill

Source

sales-skills/sales

Stars37

Forks3

UpdatedApril 19, 2026 at 17:48

File Explorer

3 files

SKILL.md

readonly

More from this repository

same repository

sales-checkout

sales-skills/sales

Optimizes BUYER-side checkout pages, upsells, order bumps, payment collection, and cart abandonment recovery — increase average order value and reduce checkout friction. Use when checkout conversion rate is too low, cart abandonment is high, average order value isn't growing, not sure which checkout platform to pick, payment plans not converting, or buyers dropping off at the payment step. Do NOT use for full funnel strategy (use /sales-funnel), email follow-up after purchase (use /sales-email-marketing), affiliate tracking on sales (use /sales-affiliate-program), or supply-side / seller-side marketplace payouts to 1099 workers, sellers, drivers, or creators (use /sales-marketplace-payouts). For Groove-specific help, use /sales-groove.

2026-05-3137

sales-do

sales-skills/sales

Routes any sales, marketing, ad, or GTM objective to the right specialized skill and outputs the install command for that skill plus a ready-to-paste prompt packed with the user's context. Asks clarifying questions when the objective is ambiguous, then hands back a copy-paste-runnable next step. Covers prospecting, outbound cadences, deals, proposals, forecasting, deliverability, enrichment, intent, content, coaching, CRO, SEO, launch directories, newsletters, email/SMS/push marketing, chatbots, influencer marketing, social media, employee advocacy, media relations, reviews, data hygiene, B2B advertising, retargeting, affiliate, loyalty, digital products, memberships, webinars, checkout, and platform-specific help. Use when the user has a sales or marketing question and isn't sure which skill to use, or wants a multi-skill sequence with a batch install command. Do NOT use to solve problems directly — this skill only routes.

2026-05-3137

sales-marketplace-payouts

sales-skills/sales

Marketplace payouts strategy — selecting and operating the payment infrastructure that pays 1099 supply workers, sellers, drivers, hosts, and creators on a two-sided marketplace. Covers Stripe Connect (Standard / Express / Custom), PayPal Hyperwallet, Adyen for Platforms, Trolley, Tipalti, Routable, dots.dev, Branch, Nium, Wise Business, and Tremendous — when to pick each, the connected-account vs custodial trade-off, KYC and onboarding burden, daily-vs-weekly-vs-on-demand pay schedules, multi-currency, tax form generation (1099-K, 1099-NEC, W-9, W-8), and the 1099-misclassification risk that worker payment design carries. Use when deciding between Stripe Connect Standard vs Express vs Custom for a 1099 cleaning marketplace, comparing Hyperwallet vs Trolley for multi-country payouts, the supply side is churning because payouts arrive too slowly, can't decide whether to use a per-payout API (Trolley, Routable) or a full marketplace stack (Stripe Connect, Adyen for Platforms), need on-demand pay to compete on s

2026-05-3137

sales-two-sided-marketplace

sales-skills/sales

Two-sided marketplace GTM strategy — the cold-start chicken-and-egg problem, supply-vs-demand sequencing, flywheel mechanics, supply-side recruiting in tight local labor markets, and a single-corridor pilot framework before multi-city expansion for on-demand and recurring service marketplaces (cleaning, food delivery, courier, lawn care, mobile detailing, home services, pet care). Use when stuck on the chicken-and-egg problem and unsure whether to seed supply first or demand first, can't recruit 1099 gig workers fast enough to fulfill the demand you're closing, every demand-side sales call should double as a supply recruiting call but you don't know how to flip the 'I don't mind cleaning the bathrooms' objection into a recruit, evaluating Wonolo / Instawork / Bluecrew / Workstream / Craigslist / Indeed as supply-side channels, planning a single-corridor pilot before multi-corridor or multi-city expansion, or writing a one-page integrated GTM plan tying brand + demand + supply + local visibility together. Do N

2026-05-3137

sales-field-sales

sales-skills/sales

Hyperlocal field-sales strategy — door-to-door / territory / route-based outbound to cash-heavy local SMB owners (restaurants, gas stations, convenience stores, salons, gyms, contractors, HVAC, lawn care) who ignore email cadences and aren't on database providers like Apollo or ZoomInfo. Covers corridor and territory target-list building from local sources (Google Maps Places API, Yelp Fusion, Foursquare, Outscraper, Phantombuster local-business scrapers — NOT Apollo), route planning and density optimization, in-person pitch frameworks for 60-second clerk encounters, objection handling for cash-heavy owners, non-email follow-up via SMS/handwritten note/phone, and platform selection across SalesRabbit, Spotio, Map My Customers, Badger Maps, Outfield, Repsly, Skynamo, and Geopointe. Use when planning a single-corridor pilot before multi-city expansion, can't find local SMBs on Apollo or ZoomInfo, an email cadence isn't getting replies from restaurant or gas-station owners, deciding which field-sales platform to

2026-05-3137

sales-prospect-list

sales-skills/sales

Builds targeted B2B prospect lists for outbound campaigns from database providers (Apollo, ZoomInfo, Clay, Cognism). Use when you don't know who to target, your outbound list is too broad and response rates are low, you can't find the right decision-makers at target accounts, your ICP is vague, or your prospect list is full of bad-fit contacts. Do NOT use for enriching existing contacts with emails/phones (use /sales-enrich), interpreting buying signals (use /sales-intent), general Apollo platform help (use /sales-apollo), or hyperlocal / door-to-door / territory / route-based outbound to local SMBs that aren't on databases — restaurants, gas stations, salons, contractors, HVAC — (use /sales-field-sales).

2026-05-3137

Source

sales-skills

sales-skills/sales

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations13-1161L4

name	sales-chatbot
description	Chatbot marketing and conversational automation — building chatbot flows, multichannel messaging (WhatsApp, Telegram, Facebook, Instagram, Viber, live chat), lead qualification bots, FAQ bots, and handoff to human agents. Use when website visitors leaving without engaging, WhatsApp or Telegram leads not getting qualified, bot flow feels broken or confusing, leads dropping off before reaching a human agent, or not sure how to automate conversations for sales. Do NOT use for live chat widget setup without bots (use /sales-live-chat), email sequences (use /sales-cadence), or SMS campaigns without conversational flow (use /sales-sms-marketing). For SendPulse-specific help, use /sales-sendpulse. For SWAI-specific help, use /sales-swai.
argument-hint	[describe your chatbot or conversational automation question]
license	MIT
version	1.0.0
tags	["sales","chatbot","live-chat","conversational"]

Chatbot Marketing & Conversational Automation

Help the user build chatbot flows for sales, support, and marketing — across WhatsApp, Telegram, Facebook Messenger, Instagram, Viber, website live chat, and other messaging platforms.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

What channel are you building for?

a) WhatsApp Business
b) Telegram
c) Facebook Messenger
d) Instagram DMs
e) Website live chat widget
f) Viber
g) Multiple channels / omnichannel
h) Not sure yet — help me choose

What's the bot's primary job?

a) Lead qualification — ask questions, score, route to sales
b) FAQ / support — answer common questions automatically
c) Product catalog / e-commerce — browse, recommend, purchase
d) Appointment booking — schedule meetings or demos
e) Welcome / onboarding — greet new subscribers, set expectations
f) Re-engagement — win back inactive contacts
g) Order tracking / transactional — status updates, notifications
h) Full conversational sales funnel

What's your technical comfort level?

a) No-code visual builder only
b) Comfortable with webhooks and basic integrations
c) Developer — want API-level control

Step 2 — Strategy and approach

Read references/platform-guide.md for channel comparison, flow design principles, lead qualification frameworks, FAQ bot structure, platform-specific guidance (SendPulse, SWAI, ManyChat, Tidio, Intercom, Drift, HubSpot), bot-building steps, metrics benchmarks, and common mistakes.

You no longer need the platform guide details — focus on the user's specific situation.

Step 3 — Actionable guidance

Based on the user's channel and bot type, provide:

Platform recommendation — which chatbot platform fits their channel, budget, and technical level
Flow design — map the conversation for their specific use case (qualification, FAQ, e-commerce, booking)
Integration setup — connect bot to CRM, calendar, or e-commerce platform
Testing plan — how to test the bot before going live
Optimization — which metrics to track and how to iterate on drop-off points

Gotchas

Best-effort from research — review these, especially items about platform-specific rules that may change.

WhatsApp 24-hour window is strict — if you send a non-template message outside the window, it silently fails or gets your account flagged. Always check last_activity timestamp before sending.
Facebook/Instagram 24-hour rule — similar to WhatsApp, Messenger has a 24-hour standard messaging window. Outside it, you need message tags (limited to specific use cases like confirmed event updates or account updates).
Template approval takes time — WhatsApp message templates require Meta review (hours to days). Don't wait until launch day to submit templates.
Bot-to-human handoff state — most platforms pause the bot during human chat but don't always resume correctly. Test the full cycle: bot → human → bot resumes.
Multi-channel subscriber identity — a user on WhatsApp and Telegram is often two separate contacts in the platform. Merging/deduplication requires matching by phone or email.
Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.

Before recommending a specific platform skill

This skill covers a strategy domain across many platforms. Before pointing the user to any specific platform skill (any /sales-{platform} listed in ## Related skills, e.g., /sales-mailshake, /sales-klaviyo, /sales-apollo), read that platform skill's actual SKILL.md first. The 1-line description in ## Related skills is enough to identify a candidate — it's not enough to commit to it or to write a prompt that invokes it well.

How to read it:

If ~/.claude/skills/{skill-name}/SKILL.md exists locally, Read it.
For sales-* skills, WebFetch directly from this repo: https://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md — e.g., for sales-mailshake: https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md.
For non-sales-* skills (third-party), look up {org}/{repo} in ~/.claude/skills/sales-do/references/skill-sources.md if installed and fetch the same skills/{skill-name}/SKILL.md path under that repo.

After reading, ground your recommendation in something concrete from the SKILL.md (its scope, a sub-flow, its argument-hint shape, or a "Do NOT use for..." negative trigger). Align any generated invocation with the platform skill's argument-hint. If the platform skill turns out not to fit the user's situation, swap to another or handle the question here directly rather than recommending a poor fit.

Step 5 — Related skills

/sales-zendesk — Zendesk platform help (AI agents, chatbot automation, ticketing)
/sales-helpdesk-selection — Help desk platform comparison (Zendesk vs Freshdesk vs Intercom vs Help Scout)
/sales-hubspot — HubSpot platform help (chatbot builder, Conversations inbox, live chat)
/sales-qualified — Qualified platform help (Piper AI SDR conversations, Salesforce-native chatbot)
/sales-sendpulse — SendPulse platform help (chatbots across 7 channels, visual flow builder, Automation 360)
/sales-swai — SWAI platform help (AI chat widget, autonomous lead qualification, Cal.com scheduling)
/sales-birdeye — Birdeye platform help (webchat chatbot for multi-location businesses, appointment scheduling)
/sales-live-chat — Live chat widget setup and optimization (non-bot focused)
/sales-sms-marketing — SMS campaigns and automation (non-conversational)
/sales-cadence — Multi-channel outbound sequences (email, call, social — structured outreach vs. conversational)
/sales-email-marketing — Opt-in email marketing (broadcasts, automations, newsletters)
/sales-integration — Connect chatbot platforms to CRM, helpdesk, and other tools
/sales-audience-growth — Grow your subscriber base (pop-ups, lead magnets, opt-in forms — feed contacts into bot flows)
/sales-lindy — Lindy platform help (AI agent builder with custom chatbot creation and knowledge base RAG)
/sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do

Examples

Example 1: WhatsApp lead qualification bot

User says: "I want to build a WhatsApp bot that qualifies leads for my SaaS product and books demos" Skill does: Recommends WhatsApp Business API setup, designs a 4-step qualification flow (greeting → role question → team size → pain point), explains 24-hour window and template requirements, configures meeting booking via calendar link, sets up hot lead handoff to sales rep Result: Working WhatsApp bot that qualifies inbound leads and books demos for qualified prospects

Example 2: Multi-channel FAQ bot

User says: "We get the same 20 questions on our website, Facebook, and Instagram. Can I automate this?" Skill does: Recommends a platform with multi-channel support (SendPulse, ManyChat, or Tidio), structures FAQ into 5 categories with sub-menus, configures fallback to human agent after 2 failed attempts, sets up the same flow across website widget + Facebook + Instagram Result: FAQ bot deployed on 3 channels, reducing support ticket volume by handling common questions automatically

Example 3: E-commerce abandoned cart recovery via Messenger

User says: "I want to send abandoned cart reminders through Facebook Messenger instead of email" Skill does: Explains Messenger 24-hour window and checkbox plugin for opt-in, designs flow: 1hr reminder with product image → 24hr discount offer → fallback to email if no response, configures Shopify/WooCommerce webhook to trigger the flow, adds human handoff for purchase objections Result: Messenger-based cart recovery flow that engages customers in a conversational format with higher open rates than email

Troubleshooting

Bot sends messages but users don't see them

Symptom: Messages show as "sent" in the platform but users report not receiving them Cause: Usually a 24-hour window violation (WhatsApp/Messenger) or the user has blocked/muted the bot Solution: Check if the message was sent outside the messaging window — use template messages instead. Verify the user hasn't blocked the bot. For WhatsApp, check your Business Manager quality rating — low quality can throttle delivery.

Bot flow gets stuck in a loop

Symptom: Users report the bot keeps repeating the same message or cycling through the same steps Cause: A condition in the flow always evaluates to the same branch, or a fallback routes back to the same step Solution: Check condition logic — ensure variables are being set correctly. Add a loop counter (increment a variable each pass) and break out after 2-3 iterations with a human handoff.

Human handoff doesn't work during business hours

Symptom: Bot transfers to human agent but nobody picks up, or the handoff action doesn't trigger Cause: Business hours misconfigured, no agents online, or the handoff action isn't connected to the live chat queue Solution: Verify business hours timezone settings. Ensure at least one agent is set to "available" in the live chat panel. Test the handoff action in preview mode to confirm it routes to the correct team/inbox.