The AI sent a notification that it had spotted an email from TripIt, the vacation-planning app Ulanoff uses, about a password change he had forgotten making. The agent wanted to make sure he'd seen the email verifying it was him.
Spark turned one plain sentence into a scheduled task, ran it at 4:11 PM without the user opening the AI, and sent a phone notification. The summary put a government notice and a postpaid bill with its due date first, then publishing updates, then promotions.
Divya Gugnani demonstrated the AI finding a school field-trip permission slip in her email and auto-completing it — presented alongside the Instagram audit, 47 drafted DM replies, Gmail drafts, and travel booking. The reel emphasizes the AI Secure VM and approval-before-send controls.
Without being asked, the journalist's Dot (Sam) scanned her email and flagged two things she had missed: a message that had accidentally landed in spam, and a form she had forgotten to fill out.
He runs his email agent on a 2018 computer he already owned. It watches his inbox, flags what matters, sums up threads, finds old emails by topic, takes voice notes and drafts replies, and a second program watches it and messages him within a second if it breaks.
This only partly worked. Worth knowing before you try it.
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.
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.
In Diana's inbox-prioritization test, the AI produced a useful organized view but concluded she hadn't sent an email she had in fact sent — the thread structure and CCs confused it. If she'd trusted the first answer, she'd have sent a duplicate email.
This one went wrong. See what happened before you try it.
He helped his brother with the website of Ichtus Vlaanderen, an NGO he used to work for. Using the AI through the WordPress.com MCP connector, he fixed design problems like a messy photo section and buttons that were too big.
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.
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.
His charity food pantry needed a barcode scanner and stock checker but could not afford a paid system. He built one with AI in two days, and it now runs on a laptop in the pantry.
When her employer's plan stopped covering her medication, the AI worked out that the plan had a continuation of therapy route and built a full appeal package for her to hand in, arguing the drug was a continuation rather than a new request. She filed it, and her doctor used the letter template it wrote.
This only partly worked. Worth knowing before you try it.
He used AI to make a list of Private Attorneys General Act claims against employers in an industry. The list was made in support of an organizing drive, and he says the tool is almost always helpful on tasks that involve a lot of data.
Tetsuro Miyatake had the AI call Volvo Cars as 'Hailey' on Matt Schlicht's behalf to check routine-maintenance availability for his XC90. The service department had openings all the following week starting Monday at 8 a.m.; the AI clarified it was checking availability only, not booking, since a phone number was still needed.
His agent sweeps his email and call transcripts looking for work he missed, then drafts the follow up messages and tickets for him. It catches commitments that slipped past him in busy weeks.
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.