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 municipal election had a huge list of candidates and felt overwhelming. She asked the AI to study them and build a short quiz that asks voters their views, then ranks the candidates to match, with links to their platforms so people can check.
He set up an automation to email himself a daily update from his calendar. Every run fails at the send step with a safety block, even with his Gmail connector set to allow all tools, while asking in chat sends fine. He rebuilt it several ways and every version stops at the same point.
This one went wrong. See what happened before you try it.
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.
Before a speaking engagement, Ulanoff couldn't recall where he was talking or where to park. He asked the AI to find the original note from his contact, misspelling the contact's name.
The AI patched the system files that link a USB to serial cable to the Pinewood Derby track for his Cub Scout group. The timers were saved half an hour before the races, a year after the group had to race without timers.
Liberty RPF's author tested the AI heavily himself after it launched in Canada, but his wife's onboarding was the telling detail: delighted by the mascot, she renamed it, changed its color, and asked it to review her email inbox daily — her first real agent job.
Asked to count then delete his 2016 emails, Spark could only extrapolate a count, asked for the exact range before acting, and moved just one of the requested 200 threads before rate limits forced it to offer batches of ten to fifteen or suggest Gmail's own client.
This one went wrong. See what happened before you try it.
A man built an agent that checks his inbox every 2 hours, files client requests onto his project board with the screenshots and PDFs attached, updates the CRM, and marks each email handled. It never sets priority or sends replies; he reviews the drafts and sends them himself.
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.