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.
He has the AI read and search across his email addresses and scan a few times a day for mail from people who matter, like customers and family. He has basically stopped checking email forty times a day. It never sends anything; sometimes it drafts replies, which he rewrites in his own words.
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.
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.
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.
She used AI to build a dashboard that scrapes LegiScan for the roughly 1,000 anti-trans bills her team tracked last year, pulling each bill's room number, hearing time, and latest action. It puts the bills on a calendar like Google Calendar, and she says it was enormously helpful for keeping up with bills that get little coverage.
Tech journalist Lance Ulanoff connected his personal Gmail to his AI 'Charlie' and asked it to check for anything pressing he had missed. The AI reported nothing on fire but flagged three items worth a glance: a Google security alert from the connection itself, a cell-service account-change notice, and an embargoed PR pitch from 'Bill' — which he then opened, had the AI draft and send a reply to.
The developer set a scheduled job in plain words: every weekday at 8:30, send events from all calendars plus emails needing a reply, in five lines or fewer. The first run arrived at 8:44 with an apology for the delay, covered all 16 calendars, removed duplicate events and listed private events by time only.
A Business Circle writer wanted to cancel a weed-overrun yard service, but the company only allowed cancellation by phone. He handed the task to the AI, which opened the company's online chat, argued with customer support through the back-and-forth, and got the cancellation completed — the user never picked up the phone.
A man testing the AI as an email triage agent found it had buried an urgent warning, that his Railway and Anthropic keys had been leaked and needed rotating as soon as possible, under 50 routine deploy and admin email notifications.
This one went wrong. See what happened before you try it.