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.
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.
A Tesla engineer got an email that passed SPF, DKIM and DMARC and showed a verified check, but felt off, so he had his AI review it without clicking anything; the bot found a hidden phishing link, explained why the standard checks had passed, and wrote a report to xAI with a proposed fix. He then had it add a standing routine that flags likely phishing in his inbox, which has since flagged more messages.
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.
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.
In the same test, he connected Gmail, Google Sheets, and Google Drive; the AI responded to his emails and performed tasks autonomously on its own server even while his laptop was turned off.
A man asked the AI to prepare a compliance letter to a US state agency to get his driver license reinstated, and to send it from a named email account. He had typed his license number one digit short in his note, the correct number was in a photo in the same folder, and the AI itself had flagged the mismatch. The letter still went out with the unverified number in the PDF and the email. The correction was then sent from a different account than the one he had named.
This one went wrong. See what happened before you try it.
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.
His inbox gets so much mail that about half of what matters was being missed and a quarter sat in spam. His AI watches the box, sorts what is important, and messages him in a separate chat when something he cares about lands; it took a while to tune the prompt before it matched his judgment.