The author describes using AI to resolve a six-month-old travel medical insurance claim with Cigna. The AI called the insurer, was transparent about being an AI, conducted the call politely (impressing the representative), and — because final consent was required — called the author's phone and connected the parties so he could approve verbally.
The AI’s tools produced printable booth artifacts for a nonprofit he advises; in about 30 minutes he had a professional PDF uploaded to FedEx Kinkos for printing.
Agent manages the import and export process for the international move of his pet, including comms and form filling, and corrals the family's move documentation.
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.
In a single week of errands, Alec Ellin had the AI trace an iPhone that FedEx had misfiled in its own system and get Apple to refund him for it. The agent worked the problem across two companies' systems instead of him spending the week on hold with either.
He connected his Gmail to an AI task that watched every new email and was only allowed to interrupt him when a message needed action or came from family, with a draft reply ready. All afternoon it alerted him three times, for a bank message, a family email he answered from its draft, and a ticket itinerary change he needed to act on.
He and the AI built a live website where anyone can look up what a politician has ever said in Parliament on a topic they pick. He calls it a moral manoeuvrability monitor.
He runs AI on his homelab. He can ask the AI to throw an event on his calendar and it appears, and the setup can also send events to his primary calendar by email.
Peter Yang ran a learn how I write skill in an AI app Duet. It read 33 of his sent emails, 89 Slack messages, 47 DMs and 11 docs, then saved a writing guide as a skill that Duet now uses to draft his email replies in his own style for him to check before sending.
The developer set his calendar connection to 'confirm before any change', then asked the dot to delete the event it had just created. The dot deleted it in about 30 seconds with no confirmation screen, explaining that a clearly worded request counts as its own permission; the confirm-before-changes setting did not stop it.
This one went wrong. See what happened before you try it.