Volunteered and built a cartography data pipeline with coding agents for an educator, integrating sources updated every few minutes so new maps appear within about 5 minutes on a low-powered machine.
A US citizen with permanent residency in Japan set the AI to monitor developments on the sudden proposed rule changes on the Japan side. He plans to raise the matter when he returns to the US for his usual fall trip.
This only partly worked. Worth knowing before you try it.
He is juggling several legal cases of his own, and his lawyers do not have time to answer him every day. The AI transcribes audio, organizes his evidence and writes the case summaries he hands to them. He calls it the best tool he has ever had, and says stopping would mean going back to doing all of that alone.
Around Elmira and Corning, New York, event listings were scattered across library systems, a brewery site, a school app, chamber newsletters and Facebook, so people found out about things the day after. He had the AI build one page that checks 101 sources across three New York counties and part of northern Pennsylvania: 1,855 listings over the next 90 days, 1,767 events after duplicates are merged, about 250 in any week, at 159 venues. A cron job reruns it every six hours on cheap shared hosting, about 8,300 lines of PHP, and cancellations mostly handle themselves because an event disappears when its source stops listing it.
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.
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.
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.
Without being asked, Harry McCracken's Dot began flagging incoming messages it judged urgent or important in an inbox flooded with PR pitches. It also resurfaced an email from a freelance author that he had overlooked for weeks and nudged him to respond.
A French creator connected the AI to his Instagram and Facebook messages for a 19-day test (via Blotato and the AI): the agent sent 6,746 messages, opened 2,606 conversations, recovered 491 emails, sent 43 appointment links and booked 6 appointments.