Beyond ChatGPT: Using Manus for 24/7 AI Customer Support and Earning $1,200/Month Passive Income

Please note: All earnings mentioned are illustrative simulations.

Beyond ChatGPT: Using Manus for 24/7 AI Customer Support and Earning $1,200/Month Passive Income

Executive summary

• Offer: Build and maintain a 24/7 AI support bot for e-commerce stores using Manus on a $400/month retainer.
• Outcome goal: 60–80% ticket deflection, sub-5-second first response, 24/7 coverage, consistent tone, and compliant PII handling.
• Income target: 3 clients x $400/month = $1,200/month in largely passive income after initial setup.
• Time budget: ~6–10 hours for initial deployment per client, then ~30–60 minutes/week for maintenance and reporting.

Why Manus over “just ChatGPT”

• Persistent deployment: A real chatbot that lives on your client’s storefront and channels (not a one-off chat session). You can embed web chat, and typically connect email and messaging channels.
• Knowledge integration: Ingest sitemaps, FAQs, policy pages, product feeds, and sync changes automatically.
• Guardrails and escalation: Enforce strict boundaries, integrate order lookups via APIs, and auto-escalate to human agents when needed.
• Analytics: Track deflection rate, CSAT, containment, first response time, and fallbacks to prove ROI.
• Maintainability: Publish updates, version prompts, and keep a test suite so improvements don’t break flows.

Start here: Create your Manus account at https://manus.im/invitation/OJF7FVBNBC14H?utm_source=invitation&utm_medium=social&utm_campaign=copy_link

The $400/month productized offer (what clients actually buy)
Deliverables included

• 24/7 support bot with brand voice.
• Coverage for top 8–12 intents: 1) Where’s my order? 2) Shipping times and costs 3) Returns and exchanges 4) Product availability and stock status 5) Sizing/fit (for apparel) 6) Warranty and defects 7) Discount codes and gift cards 8) Account/login issues 9) Wholesale inquiries 10) Order changes/cancellations (rules-based) 11) Subscription management basics (if applicable) 12) Contact information and hours
• Handoff and escalation path: email or ticketing system for edge cases.
• Weekly reporting: deflection rate, unresolved intents, CSAT, and top queries.
• Continuous improvements: up to 2 small updates/week (e.g., add new FAQ, refine intent, tweak guardrails).

Scope and limits

• Target ticket deflection: 60–80% for typical SMB e-commerce (order-tracking questions alone often represent 35–55% of inbound volume).
• Answer coverage: All policy and shipping answers must be grounded in client-provided sources.
• Escalation threshold: Escalate after 2 failed attempts to answer or if sentiment drops below a defined threshold.
• Data privacy: No PII beyond order email and order number for lookups; hard cap on stored logs per the client’s retention policy.

Pricing and margin

• Monthly retainer: $400 per store (no long-term contract to reduce friction, 30-day cancel).
• Platform costs: Include Manus and any channel fees inside your $400. Keep a 60–80% margin after platform and your time. If platform usage grows, raise retainer or create a higher tier.
• Setup: Position $0 setup for speed, or $250 one-time if you want immediate cashflow. This guide assumes $0 setup to close faster.

Assumed ROI math you can show prospects

• Baseline: 200 tickets/month at $3–$6 per ticket fully loaded (wage + overhead) = $600–$1,200/month.
• With bot: 60% deflection → 120 tickets automated; cost to handle automated tickets ≈ near-zero marginal cost.
• New support cost: 80 human tickets x $3–$6 = $240–$480/month.
• Savings: $360–$720/month vs. baseline. Your $400 retainer sits within savings band; net-zero or net-positive for the client, plus 24/7 coverage and faster outcomes.
• Upside: Faster answers can lift conversion by 1–3% on visitor segments that engage support before purchase (varies by store).

Who to target (and who to skip)

• Best fit:
  • Shopify/WooCommerce stores with 5,000–100,000 monthly sessions.
  • 30–300 inbound tickets/month (email, chat, social).
  • Clear policies pages and shipping/returns processes.
  • 20+ SKUs with recurring presales questions.
• Avoid (at first):
  • Highly regulated verticals requiring approvals for every response.
  • Stores with no clear policies, or those changing offers weekly without documentation.
  • Extremely low ticket volume (<20/month)—harder to justify ROI.

Prospecting that converts (scripts included)
Fast validation outreach email

• Subject: Cut your support volume by 60% this month (no new headcount)
• Email body: Hi {FirstName}, I build 24/7 Shopify/WooCommerce support bots that handle order tracking, shipping, returns, and presales. Target deflection is 60–80% with sub-5s first response time. For stores handling ~200 tickets/month, that’s $360–$720/month in savings. My retainer is $400/month, no setup fee, cancel any time. If I can’t show at least 40% deflection in 30 days, you don’t pay. Want a 10-minute Loom walking through how this would work on {Brand}? – {Your Name}

DM opener (LinkedIn)

• Saw your recent sale on {Product}. Quick win: a 24/7 bot that handles “Where’s my order?”, returns, and sizing. My clients deflect 60–80% tickets within 30 days. $400/mo. Want a 5-min rundown?

Loom pitch outline (5 minutes)

• 0:00–0:45: State the problem with actual numbers (tickets/month, current response time).
• 0:45–2:30: Show a demo bot answering shipping, returns, and order lookups live.
• 2:30–3:30: Walk through guaranteed guardrails and escalation to human.
• 3:30–4:30: Savings math on-screen; show $400 fits inside their current cost.
• 4:30–5:00: “Risk-free” trial structure and next steps.

Set up your Manus workspace (step-by-step)
1) Create your account

• Use this invitation link: https://manus.im/invitation/OJF7FVBNBC14H?utm_source=invitation&utm_medium=social&utm_campaign=copy_link
• Create a workspace per client: “{ClientName} Support.”

2) Collect source materials (client checklist)

• Sitemap URL (include /policies, /shipping, /returns, /faq).
• Returns policy, warranty policy, size guides.
• Shipping carriers and SLAs (domestic/international).
• Discount policy rules (what’s allowed/not).
• Product feed or catalog (CSV, API, or sitemap).
• Escalation email or ticketing inbox ([e-mail]).
• Order lookup API access (Shopify private app credentials or an order-status API endpoint; if not available, use carrier tracking API links and ask for order email/number).

3) Load the knowledge base

• In Manus, create a knowledge source and add:
  • Sitemap to crawl policy and FAQ pages. Enable auto-sync daily.
  • Upload PDF/Doc of policies if they’re not indexed.
  • Optional: connect product catalog if supported. If not, add top 50–200 product pages URL list to ingest.
• Tag content (e.g., Policy:Shipping, Policy:Returns, Product:Sizing) for better retrieval tuning.

4) Define actions for operational tasks

• Create actions (webhooks or integrations) for:
  • Order status lookup: Inputs: order_id and email. Output: status, carrier, ETA, tracking_url.
  • Return eligibility check: Inputs: order_id, item_sku, purchase_date. Output: eligible (true/false), window_end_date, instructions_url.
• If your client can’t provide APIs, implement “soft” actions:
  • Lookup by asking for order email + order number, then guide to carrier tracking using tracking URL conventions.
  • Issue a return by linking to the returns portal and pre-filling fields if possible.

5) Guardrails and privacy

• Enforce PII rules: only collect order email and order number; never store raw credit card data; never request full address unless required for a return label.
• Set refusal boundaries: no medical, legal, or pricing quotes beyond published policy; no discount promises beyond approved rules.
• Escalation policy: if the user provides conflicting info, uses strong negative sentiment, or repeats the same question twice without resolution, escalate.

6) Build intents and sample utterances

• Shipping time/cost: “How long does shipping take?”, “Do you ship to Canada?”, “What’s the shipping fee?”
• Where’s my order: “Track my order”, “Where is my package?”, “Order #1234 status?”
• Returns/exchanges: “How do I return?”, “Is this eligible to return?”, “Exchange size M for L.”
• Sizing/fit: “Does this run large?”, “I’m 5'10” 160 lbs—what size?”
• Stock/availability: “When will black medium be back?”, “Is this in stock?”
• Discounts/gift cards: “Promo code not working”, “How to use gift card?”
• Warranty/defects: “My zipper broke”, “Coverage for defects?”
• Wholesale: “Do you offer wholesale pricing?”
• Account/login: “Can’t log in,” “Password reset.”
• Order changes/cancellations: “Can I cancel?” within X hours.
• Contact: “Can I speak to a human?”

7) Draft and install the system prompt (use the template below)

• Paste into Manus as the system or instruction prompt for the bot.
• Parameterize with brand details and links.

8) Test flows (before going live)

• Create scripted test conversations:
  • Positive path: “Where is my order?” → ask for email + order number → call order lookup → reply with status and ETA.
  • Negative path: invalid order number → ask to confirm → escalate after 2 failures.
  • Returns path: item purchased 40 days ago → reply with policy and whether it’s eligible.
  • Sizing path: map to size guide; avoid making body-shape claims.
  • Discount path: coupon expired → explain policy; avoid making unauthorized exceptions.
• Aim for <5 seconds first response, and <20 seconds to resolution on simple cases.

9) Deploy channels

• Web widget:
  • In Manus, obtain the embed/snippet for the web chat widget.
  • Shopify: paste the snippet in theme.liquid before the closing tag or use the theme customizer’s “Custom HTML” section.
  • WooCommerce/WordPress: add via a site-wide footer HTML block.
• Email:
  • Connect support@ inbox via forwarding or IMAP. Configure autoresponder to route common questions to the bot for instant answers and to hand off unresolved threads to human agents.
• Messaging (optional):
  • Connect Facebook Messenger/WhatsApp if supported. Establish opt-in and consent, and ensure message templates follow channel policy.

10) Go-live criteria

• Bot answers at least 80% of FAQs accurately in dry runs.
• Escalation works end-to-end (including ticket creation or email handoff).
• Order lookup tested on 3–5 sample orders.
• Logging is enabled for reviewing unknown questions (with PII minimization).
• Client has reviewed tone and compliance verbiage.

A battle-tested system prompt for Manus (copy, then replace placeholders)
Use the following as your starting prompt. Replace placeholders in braces.

System prompt title: {BRAND_NAME} Support Assistant (Manus)

Purpose

• You are the official, 24/7 customer support assistant for {BRAND_NAME}, an e-commerce store at {SITE_URL}. Your goals are: 1) Resolve common inquiries instantly using approved knowledge sources. 2) Automate operational tasks via allowed actions. 3) Protect customer data and adhere to policy. 4) Escalate to a human agent when you cannot confidently help.

Tone and style

• Be concise, helpful, and friendly.
• Use the brand’s voice: {BRAND_VOICE_GUIDELINES}, but never invent claims.

Knowledge boundaries

• Only answer using:
  • Ingested policy/FAQ pages,
  • Product pages and size guides,
  • Approved internal notes.
• If information is missing or uncertain, say: “I don’t have that information yet,” and offer to escalate.

PII and compliance

• Only request: order email and order number for order status; never ask for full address or card details.
• Mask any order numbers when echoing back (show last 2–3 digits).
• Do not store sensitive data in free-text logs.
• Comply with: {PRIVACY_POLICY_LINK} and {DATA_RETENTION_RULES}.

Allowed actions (call only if relevant)

• action_order_status_lookup(order_id: string, email: string) → {status: string, carrier: string, tracking_url: string, eta: string}
• action_return_eligibility(order_id: string, item_sku: string, purchase_date: string) → {eligible: boolean, window_end_date: string, instructions_url: string}
• If an action fails or returns uncertain data, explain the situation and offer escalation.

Top intents and rules
1) Where is my order?

• Ask for order email + order number.
• Call action_order_status_lookup.
• Provide status, ETA, and tracking link. Do not promise delivery dates; quote the ETA.

2) Shipping times and costs

• Use policy pages {SHIPPING_POLICY_URL}.
• For countries/states not listed, say we don’t currently ship there.

3) Returns and exchanges

• Use {RETURNS_POLICY_URL} and {RETURNS_PORTAL_URL}.
• If beyond return window, explain policy, and offer store credit only if policy permits.

4) Sizing/fit

• Refer to size guides {SIZE_GUIDE_URL}. Do not speculate about body shape or health.

5) Discounts and gift cards

• Only mention publicly available offers. Do not create custom discounts.
• If a code fails, suggest checking expiration and minimum cart value per {DISCOUNT_POLICY_URL}.

6) Warranty/defects

• Follow {WARRANTY_POLICY_URL}. Provide RMA steps; escalate with photos if needed.

7) Order changes/cancellations

• Allowed only within {CANCEL_WINDOW_HOURS} hours if the order is not fulfilled. Otherwise guide to returns policy.

8) Escalation

• Escalate immediately if:
  • Two failed attempts to resolve the same issue.
  • Strong negative sentiment.
  • Requests outside allowed scope.
• Escalation path: create a ticket at {ESCALATION_EMAIL_OR_TICKET_SYSTEM} with conversation transcript; tell the customer “I’m connecting you to a human agent.”

Prohibited content

• No legal, medical, or financial advice.
• No price promises beyond published policy.
• No derogatory or offensive language.

Response format

• One to three short paragraphs or bullet points.
• Always include relevant link(s) and next step.

End of system prompt.

KPIs to track from day one

• Containment/deflection rate: target 60–80% within the first 30 days.
• First response time: <5 seconds.
• Resolution time for automated cases: <60 seconds for standard shipping/return queries.
• Escalation rate: ≤20% after initial tuning, down to ≤10% after 30 days.
• CSAT/thumbs-up rate: ≥80% on resolved interactions.
• Order status lookups automated: aim for 50–100/month for small stores.

Weekly maintenance SOP (30–60 minutes)

• Review analytics: Identify top 10 queries and any with low CSAT.
• Check “unknowns” and add 3–5 new Q&A entries (canonical answers).
• Update policies (e.g., holiday shipping dates).
• Extend intents or add synonyms; ensure retrieval points to correct policy anchors.
• Run a 10-case regression test set: shipping, returns, order lookup, discount, sizing, and two edge cases.
• Email the client a 3-number summary: deflection %, escalations %, and CSAT, plus one recommended improvement.

Client onboarding checklist (what you need before build)

• Confirm brand voice guidelines (3–5 bullets).
• Confirm “no-go” answers (e.g., do not quote custom discounts).
• Provide escalation inbox and SLA expectations (e.g., human response within 24 business hours).
• Verify order lookup connectivity (Shopify app/API or manual process).
• Decide on return window and exceptions (holiday grace period, final sale items).
• Confirm data retention window for chat transcripts (e.g., 30 or 90 days).

Live deployment playbook (Shopify example)

• Add Manus chat widget via the embed code provided under Channels > Web Widget in your Manus workspace.
• Set chat to appear on all pages, with proactive greeter on high-exit pages (cart, shipping policy).
• Configure greeting copy:
  • Cart page: “Questions about shipping or returns? I can help instantly.”
  • Product page: “Not sure about size or stock? Ask me.”
• Add an “Order status” quick-reply that triggers the order lookup flow.
• Create a page “Help Center” and embed the bot there as well; link it in the header/footer.

Email channel configuration

• Set an autoresponder:
  • “Thanks for reaching out—most questions about orders, shipping times, and returns can be answered instantly here: {Help Center link with bot}. If you still need help, reply to this email and a human will respond within 24 business hours.”
• Route emails containing order numbers to the bot first. If not resolved within 1 exchange, escalate.

WhatsApp/Messenger (optional)

• Use opt-in templates for order updates and FAQs.
• Keep responses concise; link to help center for long-form content.
• Confirm channel policy compliance for promotional messages.

Proof and reporting that closes renewals

• 30-day report template:
  • Tickets handled: 220
  • Contained by bot: 144 (65.5%)
  • Escalated: 76 (34.5%)
  • First response time: 2.1 seconds median
  • Bot CSAT: 84%
  • Order lookups automated: 92
  • Estimated cost saved: 144 x $3.50 = $504
  • Retainer: $400
  • Net monthly savings: ~$104 (plus 24/7 coverage and faster pre-sale responses)
• Include 3 customer quotes/examples (anonymized).
• Recommend one improvement with projected impact (e.g., add international shipping flow; expected +5% containment).

How to keep this passive at $1,200/month

• Onboard 3 clients to hit $1,200/month.
• Batch work:
  • Monday: 30 minutes reviewing all client dashboards and preparing mini-reports.
  • Wednesday: 30 minutes adding content updates for all clients (copy/paste variations).
  • Friday: 30 minutes regression test and sanity checks.
• Automate reminders for policy updates (holidays, new product drops).
• Template everything:
  • System prompt template (above).
  • Weekly report template.
  • Test suite template.
• Use the same core intents and actions across clients; change only brand voice, policies, and links.

Quality bar and SLAs you can promise (and meet)

• First 14 days:
  • ≥50% containment.
  • No hallucinated policies; always link to source.
• Day 30:
  • ≥60% containment, ≤10% failed answers, ≥80% CSAT on bot-resolved threads.
• SLA to client:
  • Bot uptime: 99% (platform dependent).
  • Manual policy update turnaround: <48 hours.
  • Escalation forwarding: immediate, with transcript.

Common pitfalls (and how to avoid them)

• Pitfall: Bot invents answers for missing policies.
  • Fix: Add strict refusal + link to policies; highlight “I don’t have that info” path.
• Pitfall: Order lookups fail.
  • Fix: Validate API credentials; catch errors; provide human escalation instantly on failure.
• Pitfall: Tone mismatch.
  • Fix: Provide brand tone bullets and examples in the system prompt; review 10 conversations weekly.
• Pitfall: High escalation rate after promotions.
  • Fix: Pre-load promo FAQs and validity windows; add a “Promo issues” intent before the campaign.

Legal and data protection checklist

• Data processing agreement: If the client requests, provide a standard DPA that covers chat logs and retention.
• PII minimization: Only request email + order number; mask identifiers when echoing back.
• Retention: Agree on deletion window (e.g., 30 or 90 days); document this in your contract.
• Customer consent: Ensure channel-specific opt-ins (e.g., WhatsApp).
• Accessibility: Ensure web widget has keyboard navigation and ARIA labels.

Contract template essentials (for your $400/mo offer)

• Scope: Intents covered, channels supported, weekly updates included, and what’s out-of-scope.
• KPIs: Containment target, FRT target, CSAT target.
• Fees: $400/month, cancel anytime with 30 days’ notice.
• Platform costs: included in retainer unless overage triggers a tier upgrade (define a threshold, e.g., >1,000 automated conversations/month).
• Data handling: retention and deletion commitments.
• Liability: Limitations; no guarantees on conversion lift.

Realistic rollout timeline (per client)

• Day 0–1: Intake and data collection.
• Day 1–2: Knowledge ingestion and action wiring (order lookup, returns).
• Day 2–3: Intent buildout, system prompt, and tests.
• Day 3–4: Staging and client review.
• Day 5: Go live on web widget.
• Day 6–7: Connect email channel, finish escalation rules.
• Day 8–30: Weekly improvements and KPI reporting.

Example flows (keep for your test scripts)

• Order status
  • User: “Where is my order #12439?”
  • Bot: “I can help. Please share the email used for the order. I’ll keep your info private.”
  • User shares.
  • Bot calls action_order_status_lookup → returns “In transit, ETA June 29, tracking US123…”
  • Bot: “Your order is in transit via USPS. ETA June 29. Track it here: {tracking_url}. Anything else I can help with?”
• Returns
  • User: “I want to return a hoodie purchased 35 days ago.”
  • Bot: “Returns are accepted within 30 days for unworn items. At 35 days, store credit may apply if your item is unused. Here are next steps: {RETURNS_PORTAL_URL}.”
• Sizing
  • User: “What size should I get if I’m 5'10” 160 lbs?”
  • Bot: “Please use our size guide here: {SIZE_GUIDE_URL}. This product generally fits true to size. If between sizes, consider the larger size per our guide.”

How to package higher tiers (when you’re ready)

• $600/month: add WhatsApp/Messenger channel, product recommendation flows, and 1 A/B experiment monthly.
• $1,000/month: add proactive cart saver flows, integration with email/CRM, and bi-weekly optimization plus 24-hour SLA for updates.

Your next steps (action plan for this week)

• Day 1:
  • Set up your Manus account at https://manus.im/invitation/OJF7FVBNBC14H?utm_source=invitation&utm_medium=social&utm_campaign=copy_link
  • Build a demo bot for a sample store using public policies (no PII).
  • Record a 3-minute Loom showing “Where’s my order?”, returns, and size guide flows.
• Day 2:
  • Send 30 cold emails + 10 LinkedIn DMs.
  • Add a calendly link for 15-minute discovery calls.
• Day 3–4:
  • Close 1 pilot at $400/month with a 30-day “no pay if <40% deflection” guarantee.
• Day 5–7:
  • Deliver the build using the steps above; report KPIs at Day 7.

Frequently asked questions (for clients)

• Will this replace my support team?
  • No. It reduces repetitive tickets so your team can focus on complex cases. We escalate anything nuanced or sensitive.
• What if the bot gives a wrong answer?
  • We restrict it to your official policies and sources, and add refusals for anything not documented. We also review logs weekly and adjust.
• Can it track orders?
  • Yes, if you provide an order lookup endpoint or we connect to your e-commerce backend. Otherwise, we guide customers to carrier tracking with clear instructions.
• Is customer data safe?
  • We only collect order email and order number, never store card details, and comply with your data retention policy.

Closing the loop

• Keep the promise simple: instant answers for repetitive questions, strict boundaries for safety, and measurable savings that offset your fee.
• Build once, iterate lightly, and replicate across clients with your template.

Get started with Manus today

• Create your Manus workspace now: https://manus.im/invitation/OJF7FVBNBC14H?utm_source=invitation&utm_medium=social&utm_campaign=copy_link
• Use the system prompt in this guide.
• Land 3 clients at $400/month to reach $1,200/month in recurring, mostly passive income.

Appendix: Discovery call checklist (10 minutes max)

• Ticket volume last 3 months (avg/month).
• Top 5 inquiry types (estimate % per type).
• Current first response time and CSAT.
• Policy source of truth URLs.
• Escalation inbox and human SLA.
• Access to order lookup or returns portal.
• Go-live page(s) for the chat widget.
• Approval on refusal boundaries (what not to say).

Appendix: Day-30 optimization ideas

• Add proactive prompts on cart and PDP (“Ask about shipping times”).
• Expand international shipping matrix with clear timeframes.
• Clarify return exceptions (final sale, hygiene items).
• Add synonyms and locale variants (shipping vs. delivery).
• Load seasonal content (holiday cutoffs, pre-order ETAs).

Final note

• The math works because most e-commerce support volume clusters around repeatable questions. With Manus handling 60–80% of those with grounded answers and no hallucinations, your $400/month retainer becomes an easy “yes” for stores—and three of those retainers gets you to the $1,200/month target.

Ready to build? Start with this invitation link: https://manus.im/invitation/OJF7FVBNBC14H?utm_source=invitation&utm_medium=social&utm_campaign=copy_link