My Blog

Tag: Grok Bot

  • Grok Bot: GrokBot Just KEEPS Getting Better (4 New Use Cases)

    Watch on YouTube: https://www.youtube.com/watch?v=q7lekwOXXqk

    Channel: Kacper Rutkiewicz | AI Made Simple

    Introduction

    The video from Kacper Rutkiewicz | AI Made Simple showcases four recently added capabilities of Grok Bot. Each feature is demonstrated in a short, hands‑free session that ties together search, file creation, messaging, and voice interaction. The presenter frames the bot as part of a Cursor‑based workflow and shares concrete usage numbers from his own account.

    What the video covers

    Kacper walks through:

    • Native X (Twitter) search that does not consume developer credits.
    • Creation of real Google Docs, Sheets and Slides in the user’s Drive.
    • A dedicated bot‑owned inbox at @mail.grokbot.com.
    • A hands‑free voice mode that returns a full transcript after the session.

    He ties the four functions together in a 33‑second voice command that searches X, builds a deck, a doc and a sheet, then emails the links, and he shows the impact on his weekly quota.

    Native X search

    Grok Bot can query X directly from the chat interface without drawing on the user’s X developer or API credits. The feature is limited to 1,000 searches per day per account. In the demo the bot’s X Developer balance stayed at $3.61, confirming that no credits were spent. This allows repeated research queries—such as “top posts about X in the last 48 hours”—to be run throughout the day without affecting any paid X API usage elsewhere.

    Google Docs, Sheets and Slides

    When Google Workspace is connected, Grok Bot creates actual files in the user’s Drive rather than markdown placeholders. Users can point the bot at personal master templates so generated decks, docs and sheets follow brand styling. Slide generation typically takes 5–10 minutes. The same 33‑second voice command that produced a deck, a doc and a sheet moved the weekly quota from 32% to 35% (about a 3% increase), indicating that file‑creation consumes a modest portion of the limit.

    Bot email inbox (@mail.grokbot.com)

    Each bot instance receives a unique address of the form name@mail.grokbot.com, separate from the user’s personal Gmail. The address is claimed by typing “Claim our email and create our inbox”; allocation follows a first‑come, first‑served basis as the feature rolls out. The bot can send formatted HTML messages to any recipient and can also receive mail—useful for verification codes, receipts or newsletter sign‑ups—and reply to incoming messages. An important caveat is that new mail does not automatically wake the bot; a polling routine must be set up otherwise messages remain unnoticed until the user explicitly asks the bot to check.

    Voice mode

    Activating the waveform or call button enables hands‑free speaking; Grok Bot returns a full transcript after the conversation ends. In the headline demo a 33‑second verbal command—search X, build a deck, a doc and a sheet, then email the links—was executed successfully. Longer sessions, such as 15‑ to 20‑minute verbal brainstorming calls, barely register against the weekly quota on the Cursor plan, showing that voice interaction can support extended workflows without significantly impacting usage limits while still providing a searchable transcript.

    Tools and usage numbers

    • Cursor subscription: $60 / month (the plan used for quota measurements).
    • Weekly quota before demo: 32%; after demo: 35% (≈3% increase for the full multi‑step voice command).
    • X Developer credit unchanged: $3.61.
    • Native X search cap: 1,000 searches per day per user.
    • Slide generation time: 5–10 minutes.
    • Voice demo length: 33 seconds; longer brainstorms 15–20 minutes barely affect limits.
    • Integrated tools: Grok Bot, Cursor, X (Twitter), Google Workspace (Drive, Docs, Sheets, Slides, Gmail, Calendar), mail.grokbot.com.

    Caveats and hype check

    The presenter notes that the demonstrated usage figures are based on a single creator’s session and have not been independently verified. Claims about Grok Bot being a “premier personal AI agent” should therefore be treated as directional rather than definitive. The email inbox feature is still rolling out, so name availability varies and users may need to try several variations of @mail.grokbot.com. Additionally, new mail does not auto‑trigger the bot; a polling routine is required to avoid missed messages.

    > “Even 15‑to‑20‑minute verbal brainstorming calls barely impact usage limits.”

    Concrete next actions

    • Claim a preferred @mail.grokbot.com address by typing “Claim our email and create our inbox.”
    • Connect Google Drive via Connect Apps; optionally set a master template for Docs, Sheets and Slides.
    • Add a routine that polls the bot inbox (since new mail does not auto‑wake the bot).
    • Try a native X search prompt, for example: “top posts about AI agents from the last 48 hours.”
    • Run one multi‑step voice command (search X, create a doc, sheet and slide, email the links) and review the transcript plus the quota delta.
    • Optional: join the Skool community at skool.com/ai-automation-network-2970 for templates and guides.

  • Grok Bot: I Spent 50 Hours Testing Grok Bot: 8 Tricks You NEED

    Watch on YouTube: https://www.youtube.com/watch?v=CUxn_kTrc1o

    Channel: Nuno Tavares | Automated Marketer

    Introduction

    Nuno Tavares, creator of the “Automated Marketer” channel, shares the results of more than 50 hours of hands‑on testing with Grok Bot. The video outlines eight advanced techniques that aim to improve voice interaction, app integration, multi‑agent coordination, security, and skill retention for power users who want to automate complex workflows.

    What the Video Covers

    The presentation is structured around eight specific “tricks” that Tavares discovered while experimenting with Grok Bot. Each trick is demonstrated with a practical example, and a bonus maintenance routine is added to keep agent performance consistent over time. The video also notes the tools and platforms involved, provides quantitative details (e.g., number of apps accessible via Composio), and includes a brief hype check to remind viewers that the reported gains are based on personal experimentation.

    Step‑by‑Step Walkthrough of the Eight Tricks

    1. Assign distinct voice presets – Open a bot’s Settings inspector, choose a voice preset (e.g., Iris, Eve) and save it. This enables hands‑free interaction on mobile or desktop devices.
    2. Leverage Composio as a single‑click bridge – Sign up at composio.dev, install the Composio plugin inside Grok Bot, and connect the SaaS accounts you need. The free tier offers 100 000 actions per month and provides access to 1 580 external apps.
    3. Summon specialist bots with @mentions – During any chat, type the @ symbol followed by the bot’s name (e.g., @Presentation) to pull that agent into the conversation, preserving context.
    4. Create persistent group chats for agent swarms – Use the left‑sidebar + button to start a Group Chat, add the relevant bots, and issue a high‑level collaborative directive. The swarm stays active for ongoing projects.
    5. Secure logins with a 1Password Service Account Token – In 1Password, create a vault, generate a Service Account Token with read‑only scope, and paste the token into Grok Bot’s 1Password connector. This avoids storing plaintext credentials.
    6. Use the Chief of Staff as a “Bridge” for cross‑platform AI coordination – Assign the Chief of Staff a prompt that lets it control Claude and ChatGPT simultaneously, enabling A/B testing or parallel task execution.
    7. Teach agents to remember successful click paths – After an agent reaches a target screen, instruct it to “Remember what you clicked.” This stores the navigation sequence, reducing token usage on repeat runs.
    8. Record live‑screen demonstrations to create repeatable skills – Launch the bot’s virtual desktop, use the “Teach a task” feature to record a manual workflow, stop recording, and confirm the learned skill for future automation.

    Tools, Platforms, and Quantitative Details

    • Grok Bot (the core platform being tested)
    • Composio (composio.dev) – 1 580 apps accessible; free tier: 100 000 actions/month
    • 1Password – Individual Plan: $2.99 USD/month (annual) or $3.99 USD/month (monthly) with a 14‑day free trial; Families Plan: $4.49 USD/month (annual)
    • Claude (claude.ai) – ad dimensions noted: 1080 × 1080 (square) and 1200 × 628 (link)
    • ChatGPT (chatgpt.com)
    • Skool (skool.com) – mentioned as a community/resource
    • YouTube (youtube.com) – platform hosting the video
    • Google Chrome (virtual desktop browser) – used for the “Teach a task” recordings

    Notable Quotes from the Video

    “All of your bots can have a very specific voice, where you can actually communicate via voice on your phone or on your laptop or PC.”

    “Instead of you having to always connect your different AI tools into a bunch of different connectors… you can literally come in here, connect it once, and it will automatically use this with any of your AI tools.”

    “You can bring in other bots to your conversation… It will automatically bring in the bot to the conversation and pass that information through.”

    “Saved as `@claude-chatgpt-ad-design` so future runs deep‑link and skip the wander.”

    “Remember what you clicked so you can actually be a little bit more efficient in doing this and so you don’t use as much tokens.”

    “Watching the teach recording now — claiming the capture and reviewing it… Learn from demonstration.”

    “Create a routine that goes through and optimizes our skills and makes sure that our connections are the most up to date… so they don’t get stale and, more importantly, your skills are always improving.”

    Caveats and Hype Check

    The video’s productivity claims are based on the creator’s personal 50‑hour experiment. No independent verification, revenue figures, or guaranteed performance metrics are presented. Viewers should treat the described efficiency improvements as anecdotal outcomes rather than assured results.

    Concrete Next Actions

    • Open a bot’s Settings inspector and assign a unique voice preset (e.g., Iris, Eve) for voice interaction.
    • Sign up at composio.dev, install the Composio plugin in Grok Bot, and connect your key SaaS accounts.
    • In 1Password, create a vault, generate a Service Account Token with read‑only scope, and paste it into Grok Bot’s 1Password connector.
    • During any chat, type @ to summon a specialist bot (e.g., @Presentation) and continue the conversation with context.
    • Create a Group Chat via the left‑sidebar + button, add relevant bots, and issue a high‑level collaborative directive.
    • After an agent reaches a target screen, instruct it to “Remember what you clicked” to lock the navigation path for future runs.
    • Use the ‘Teach a task’ feature: launch the bot’s virtual desktop, record a manual workflow, stop recording, and confirm the learned skill.
    • Assign the Chief of Staff a maintenance prompt to periodically audit skills, tokens, and connections.
    • Mute the voice modal when not speaking to avoid accidental background triggers.
    • Explore the 1 580 apps list in Composio to identify additional integrations for your workflows.

    Related Topics

    Grok Bot, Marketing & Lead Gen, AI Tools

  • 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.

  • Grok Bot: Claude AI + Grok Bot = $61,000/month

    Channel: Ritesh Verma

    Introduction

    Ritesh Verma’s video explains how he combines Claude AI as the strategic “brain” with Grok Bot as an operational “computer‑using” employee to run an AI‑driven consulting business. He claims the setup generated roughly $61,000 in revenue over the last 30 days while he traveled to four countries.

    What the video covers

    The presentation walks through the architecture of the AI employee team, the specific roles Claude and Grok Bot play, how the team is built and trained, and the concrete workflows used for lead generation, advertising, and content creation. It also shares the tools involved, example numbers, and a set of action items for viewers who want to replicate the model.

    Step‑by‑step walkthrough

    • Claude as the brain – Claude designs the overall strategy, creates system prompts, and defines the organizational structure. In the video Claude writes a COO‑builder prompt for Verma’s consulting company, Agent Rise.
    • Grok Bot as the operator – Grok Bot runs a personal computer and executes tasks inside the business (WhatsApp messaging, Meta Ads management, content repurposing, etc.) rather than relying solely on API‑only chat.
    • Building the org chart – Using Claude’s COO prompt, Grok Bot proposes a structure with managers and individual contributors (ICs) across sales, client acquisition, content, and scaling. Verma mentions an example org chart of roughly 4 managers and 11 ICs (about 16 seats). He removes an AI “closer” role and adds a short‑form script writer.
    • Training Grok Bot employees – Skills are sourced from a Claude Skills zip file (script writing, repurposing, director, id8). Additionally, a Google Drive voice profile built from the highest‑converting YouTube scripts is used to align the bots’ tone with proven messaging.
    • Speedy SDR on WhatsApp – Grok Bot monitors a raw lead sheet. If a lead appears only in the raw data and has not yet been booked (i.e., not on the lead tracker), Grok Bot sends a WhatsApp message. Leads that already have a booked call are skipped to avoid duplicate outreach.
    • Ads manager workflow – A Meta Ads MCP/developer app with a system‑user token (ads_read, ads_management) lets Grok Bot audit campaigns daily. Under‑performing ads are paused or killed. Verma cites an example where the cost per acquisition (CPA) hovered around $30.
    • Scaling rule – Before adding any new hire, Verma asks whether the task could be performed by a Grok Bot employee. If yes, the role is filled by a bot; if not, a human is required. He notes that creative/design work still relies on humans for now, while growth is driven by more content, higher ad spend, and fresh creatives.

    Tools and numbers mentioned

    • Revenue claim: $61,000 in the last 30 days (as stated by Verma).
    • Travel: Business operated while Verma visited 4 countries.
    • Claude usage: Since February (approx. timeline).
    • Grok Bot usage: Roughly 45 days at the time of the video.
    • Claude model referenced: Claude Fable 5.1 medium (as spoken).
    • Org chart example: 4 managers, 11 ICs (~16 seats).
    • Ads performance: Example ~$30 CPA on Meta ads.
    • Free offers: 15 free roadmap strategy calls; claims clients can grow from $1k to $20k+/mo.
    • Tools list: Claude, Grok Bot, Google Drive/Sheets, WhatsApp, Meta Ads (developers.facebook.com apps), Agent Rise, Slyte, Skool WiFi Life.

    Notable prompts and quotes

    Claude becomes the brain that designs the system, and Grokbot becomes an operator that runs it entirely.

    If a raw lead appears on lead tracker and they have booked a call, do not WhatsApp them. If they’re only in raw lead data and not on lead tracker… those are the only people to message.

    Can this hire be a Grockbot employee? If so… If not, you need a human employee.

    Caveats / hype check

    The video presents a large revenue figure without showing a profit‑and‑loss statement or detailed financials on screen. The claim of a seven‑figure business relies on the stated $61k/month extrapolated over a year. The presentation includes a strong call‑to‑action for a free community, 15 strategy calls, and a done‑for‑you offering (Slyte). While the WhatsApp and Meta Ads automations appear to be real workflows demonstrated in the video, the results shown may be cherry‑picked. Viewers should treat the income claim as aspirational rather than guaranteed.

    Concrete next actions

    • Draft a COO‑style organizational prompt for Grok Bot that outlines workstreams such as content, lead handling, and operations before launching any bots.
    • Export reusable Claude Skills (script writing, repurposing, etc.) as Markdown files and use them to train matching Grok Bot employees in the same way Verma describes.
    • If testing a WhatsApp‑based SDR, replicate the “raw lead vs booked lead” gate in Google Sheets: only message leads that exist in the raw sheet but are absent from the lead tracker.
    • Set up a Meta Ads developer app with the required system‑user token (ads_read, ads_management) and create a daily audit routine that pauses campaigns exceeding a target CPA threshold.
    • Apply the scaling heuristic: for any new role or task, ask whether a Grok Bot employee could perform it; if the answer is no, plan to hire a human for that function.