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.
He is treasurer for a nonprofit food co-op. He gave the AI the co-op's financial statements, some notes on what he wanted to explain, and the logos, and 20 minutes later he had a ten slide deck and separate printouts for the annual meeting.
Commenting on the 26 use cases post, he says his AI books all his haircuts: he just says book a haircut on a day at a time, and the email confirmation comes in. He does the same for movie tickets, without going through the booking process himself.
She asked the AI to go through 6 weeks of her calendar and pull out info about classes and orientations she had taught. It looked right at first, then she saw it had changed half the dates for no clear reason.
This one went wrong. See what happened before you try it.
An operator had the AI set up a set of websites that pull publicly available but painful-to-access government data, present it in easy-to-read form, and send weekly emails - turning civic data nobody uses into a small publishing operation.
She asked the AI if it could cancel her Mint Mobile account. The company's chat agent had told her she needed to call in. She gave the AI her Mint details, the AI opened its own chat with the company and got the cancellation done, with no phone call and no talking to people herself.
A non-developer used AI to restore his foundation's broken donation payments and restructure the portal into four separate funds; the site shows $17,149,000 in donations processed.
The AI prepared and filed Australian visitor visas for a couple travelling to Brisbane, and caught a placeholder birthdate in the details before submission, confirming the correction over WhatsApp.
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 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.