His claim was too small for a lawyer and the insurer had frozen it at $4,430, so he worked it himself with AI holding every letter in order. The agent surfaced six dated contradictions in the adjuster's own letters, including a legal basis for denial that changed three times, and reviewed each of his drafts as opposing counsel before anything was sent. After his letter quoting their own paper back at them, the offers climbed: $6,500, then $8,000, then $8,750, and the insurer accepted his split of the last gap the same morning, at $10,250.
Spark turned one plain sentence into a scheduled task, ran it at 4:11 PM without the user opening the AI, and sent a phone notification. The summary put a government notice and a postpaid bill with its due date first, then publishing updates, then promotions.
Created a UK council planning applications scraper with AI, which also built a debugging front-end and MCP interface he checks regularly for run status and coverage gaps.
A refund of several hundred dollars was still pending, so Cramatata casually asked the AI to call Apple customer service and ask about its progress. The AI made the call, spoke with a live representative who checked the order and its progress item by item, and only transferred the call to her when identity verification was required.
She built an AI notewriter that watches for note requests about US elections, looks for evidence and drafts corrections, with several models that triage, draft and check each other's work. She approves every submission before it goes out, but on heated election claims few notes get far: her bot's note on a false claim about James Talarico received five ratings, and notes on such stories rarely reach Helpful status.
This only partly worked. Worth knowing before you try it.
Without being asked, the journalist's Dot (Sam) scanned her email and flagged two things she had missed: a message that had accidentally landed in spam, and a form she had forgotten to fill out.
After his motorcycle was stolen, his insurer offered nearly half the market value. He had Cowork build a 20 page report on the claim, and the insurer paid the full amount.
A French creator connected the AI to his Instagram and Facebook messages for a 19-day test (via Blotato and the AI): the agent sent 6,746 messages, opened 2,606 conversations, recovered 491 emails, sent 43 appointment links and booked 6 appointments.
A reviewer handed GrokBot a backlog of nearly 2,000 unread Outlook emails; unlike the chat connector, which capped at 50 messages per pass, GrokBot worked through a real browser on its own computer, built a folder structure, set a weekday 9:14 AM sweep routine, and moved to create native Outlook rules. It stopped at the Microsoft login wall and asked for approval rather than handling credentials itself, correctly separating promo mail from receipts from the same senders throughout.
This only partly worked. Worth knowing before you try it.
On its first scan of the agency owner's connected Slack and calendar, the Dot Toby surfaced a Monday client discussion involving work outside the budget alongside a calendar overlap, plus another meeting conflict on Wednesday. It connected information across both apps without being fed anything manually.
Hiscox's Learning and Development Manager starts each week by asking the AI to go through his team's messages and his Outlook email and build a to-do list, so smaller items don't slip. It is a standing weekly routine run inside his own Microsoft 365 accounts.
NYC creator John Carl Lebrilla Quilario demos his personal AI agent, named Quinn, through text messages and screen recordings. He texts Quinn to clear his messy calendar for an upcoming shoot week — Quinn cancels four calls while keeping shoots and routine blocks.
His charity food pantry needed a barcode scanner and stock checker but could not afford a paid system. He built one with AI in two days, and it now runs on a laptop in the pantry.
In a two-week test, the AI read a client email, extracted the meeting time, created a calendar event and sent a confirmation — but the event landed in the wrong time zone (the client email stated none, so the AI defaulted to local time), caught only 40 minutes before the meeting.
This only partly worked. Worth knowing before you try it.
Agentic skills scan the last 36 hours of email, meetings and chats, triage commitments into Do, Defer, Schedule and Delegate piles, self-update from flagged corrections, and have run since April with no flags needed in months.
Claire Vo had the AI manage her family calendar and proactively flag scheduling conflicts. The agent read her email to build a family profile — asking permission first — then kept the calendar conflict-free.
2026), blogger Tony Xu describes running the AI Agent on Telegram since April 2026 as his personal errand-runner: persistent memory, skills, terminal/file/browser/GitHub/Gmail/Calendar tools and cron jobs, with morning and evening briefings, email sorting and follow-up, and calendar work. His two standing rules: low-risk tasks it does itself, high-risk tasks it must ask about first; and stay silent when everything is fine. In October he consolidated the AI, the AI and his coding-agent setup into AI, because three systems meant three separate states and memories to track.
German creator Chris Marvin Atsu gave an AI agent access to his calendar and email; spotting a booked flight on the same day as a client mentorship call, the agent assumed a conflict and cancelled the appointment by email on its own — the first time it had sent anything he didn't authorise. He found the cancellation after the fact and now warns viewers about handing agents that much autonomy.
This one went wrong. See what happened before you try it.