Category: AI Receptionist

  • AI Receptionist: 把 AI Agent 放進 WhatsApp 群組:Skill-Wise 設定教學(Manus、ChatGPT、Zo Computer)

    Channel: 阿石OMP

    Introduction

    The video from 阿石OMP demonstrates how to place an AI agent inside a WhatsApp group using the Skill‑Wise platform. The presenter shows a live demo where an “OMP Demo” agent answers a question about yesterday’s event attendance (97 %) and explains the approval flow that lets a colleague tag the agent and require an owner emoji before the agent can access company data.

    What the Video Covers

    • Why a 1:1 WhatsApp chat with an AI is less useful than putting the agent in a group where teammates can @‑mention it.
    • A live demo of the OMP Demo agent responding to a query about event attendance and the optional human‑approval step.
    • The end‑to‑end setup process for connecting Manus, ChatGPT (paid), or Zo Computer to a dedicated WhatsApp number via Skill‑Wise.
    • Technical detail: a WhatsApp message creates a Manus task; when the task finishes, the reply is returned to WhatsApp.
    • Beta pricing information, the free‑for‑~100‑users offer, and the promotional pitch for CEF‑funded courses and related tools.

    Step‑by‑Step Walkthrough

    1. Create a Skill‑Wise account – sign up for free at skill‑wise.ai.
    2. Connect an AI model
      • Choose ChatGPT (requires a paid subscription), Manus, or Zo Computer.
      • If using Manus, paste the Manus API key obtained from the Developers portal.
      • Zo Computer is noted as the preferred option for fine‑grained permission control.
    3. Add a dedicated WhatsApp number
      • Do not use your personal WhatsApp account.
      • Register a new WhatsApp number (or a secondary SIM) and link it via the QR code shown in Skill‑Wise (WhatsApp Web flow).
    4. Configure approval settings
      • Set the default behaviour: the AI ignores requests until it receives explicit permission.
      • Define per‑colleague rules – either auto‑allow or require an owner emoji (e.g., 👍) before the agent may access CRM or other internal data.
    5. Invite the agent to a WhatsApp group
      • Add the dedicated WhatsApp number as a participant in the desired group.
      • Team members can now @‑mention the agent to ask questions.
    6. Observe the interaction flow
      • A user’s @‑mention triggers a WhatsApp message.
      • Skill‑Wise forwards the message to the selected AI (Manus/ChatGPT/Zo) as a task.
      • When the AI finishes processing, the result is sent back to WhatsApp as a reply.
      • If approval is required, the agent waits for the owner’s emoji response before proceeding with any data‑access actions.

    Tools, Numbers, and Key Details

    • Demo answer: the agent reported yesterday’s event attendance as 97 %.
    • Skill‑Wise beta: free for the first ~100 friends/users; potential future charges if server costs increase.
    • Supported AI connections: ChatGPT (paid), Manus (API key required), Zo Computer (preferred for granular permissions).
    • WhatsApp integration: uses the standard WhatsApp Web QR process to link a dedicated number (not a personal account).
    • Underlying tech: WhatsApp message → Manus task → task completion → reply returned to WhatsApp.
    • Additional mentions: Whisper ASR was used for transcription (no YouTube captions); the video ends with a pitch for CEF‑funded AI marketing/office courses and related tools such as Manus, VPN, and Alibaba office solutions.

    Caveats / Hype Check

    “將 AI 放進 WhatsApp Group 上是比較實用的”
    “我們建議你是使用一個新的 WhatsApp 號碼… 不要連接你自己的個人號碼”
    “預設 AI 是不會應付他們的,所以你一定要設定權限給它”

    The presenter notes that Skill‑Wise is still in beta, with a free‑for‑~100‑users offer that may transition to a paid model later. The transcript was generated via Whisper ASR, which can introduce noise (e.g., mis‑recognised terms). No independent security audit of the WhatsApp‑to‑AI bridging process is mentioned. The video concludes with promotional CTAs for courses and related tools, which should be evaluated separately from the core functionality.

    Concrete Next Actions

    • Evaluate Skill‑Wise (or a comparable WhatsApp‑group AI bridge) for an AI receptionist or HK‑based operations workflow, focusing on mandatory human approval before any CRM write or data‑access action.
    • If exploring alternatives, compare Skill‑Wise’s multi‑user group + approval model to tools like Speedy WhatsApp computer‑use or Grok Bot, noting differences in permission granularity and pricing.
    • Set up a test environment using a fresh WhatsApp number, connect a preferred AI (e.g., Zo Computer for fine‑grained control), and run a small internal pilot with a handful of colleagues to verify the approval flow and response latency (approximately 10 seconds in the demo).
    • Document any observed ASR‑related transcription issues and assess whether they impact the reliability of the agent’s answers in your specific use case.
  • AI Receptionist: Claude Opus 5.5 Just Replaced GHL $297 to $0 (No Subscription)

    Channel: ambITious | AI

    Introduction

    The video from ambITious | AI demonstrates how to replace GoHighLevel’s $297‑per‑month subscription with a self‑hosted agency CRM and website builder that can be assembled in roughly one hour using Claude Opus 5.5, Claude Code, and Firebase. The presenter frames the approach as a way to eliminate recurring software rent while retaining full ownership of client data and workflows.

    What the Video Covers

    The presentation walks through the end‑to‑end process of provisioning a CRM, branding it, connecting communication channels, and generating client‑ready websites. It also outlines a pricing model for selling the solution to local SMBs and highlights the risks associated with staying on a platform like GoHighLevel.

    Step‑by‑Step Walkthrough

    • Initial CRM deployment (≈15 minutes) – Using a single prompt, Claude Opus 5.5 reads the repository’s claude.md file and instructs Claude Code to scaffold the CRM inside VS Code. This step configures Firebase as the backend, imports brand assets (logos, colour palette), and sets up the core database schema.
    • Full operational setup (≈60 minutes total) – After the base CRM is live, the presenter adds API keys for AI services (Claude Opus 5.5 for chat), SMS providers, voice‑call platforms, and payment gateways. Each integration is triggered through additional Claude Code commands that update the Firebase functions and frontend components.
    • Website builder (≈20 minutes per site) – A separate Claude‑driven workflow generates a custom website for each client. The output includes a video hero loop, dark‑mode UI, auto‑generated SEO metadata, and favicons. The builder also provisions a contact form, an AI‑powered chat widget, a voice‑AI agent, and a knowledge base trained on the client’s business information.
    • Data routing – Submissions from contact forms, transcripts from chat widgets, and logs from voice calls are automatically written to the appropriate sub‑account within the CRM, ensuring a unified lead‑management view.

    Tools, Numbers, and Metrics Mentioned

    • Software: Claude Opus 5.5, Claude Code, VS Code, Firebase, Go High Level (GHL)
    • Cost comparison: GHL charges $297/month; the self‑hosted setup eliminates that fee, saving over $3,500 per year per agency.
    • Time estimates: 15 minutes for base CRM, 60 minutes for full deployment, 20 minutes per client website.
    • GHL platform risks: workflows stop after 14 days of non‑payment, sub‑accounts lock on day 1, and all data/funnels are permanently deleted after 90 days.
    • Revenue model: Charge SMBs $297/month for a managed website and lead delivery. Example outcomes: 3 clients → $10,692/year; 30 clients → $106,920/year.

    Caveats and Hype Check

    “That’s not software, that’s rent on your own business.”

    While the video markets the solution as a $0 subscription, it notes that variable costs remain for hosting (Firebase), LLM usage (Claude Opus 5.5), voice services, and SMS. The presenter also promotes a specific repository (“Lead Stack”) and a paid community (“AI Plus”), which may involve additional fees or access requirements. The claim that Claude Opus 5.5 replaces GHL should be understood in the context of the demonstrated workflow; it does not guarantee feature‑parity with every GHL module, especially advanced automation or marketplace integrations.

    Concrete Next Actions

    • For AI Receptionist: Adopt the auto‑provisioning model shown to bundle voice AI chat, web chat widgets, and CRM auto‑logging into turnkey client sites.
    • For Jev/Claude Automation: Standardise project setup around a claude.md file so Claude Code can automatically install dependencies, brand assets, and database schemas.
    • Evaluate the ongoing variable costs (Firebase read/write, Claude token usage, voice/SMS APIs) to ensure the $297/month client price covers expenses and delivers a target margin.
    • Test the end‑to‑end flow with a pilot client: deploy a sample website, submit a lead via the form, verify that the lead appears in the CRM sub‑account, and confirm that chat and voice interactions are logged.
    • Document the specific API keys and quota limits required for each integration to create a repeatable onboarding checklist for new clients.