His claim was too small for a lawyer and the insurer had frozen it at $4,430, so he worked it himself with AI holding every letter in order. The agent surfaced six dated contradictions in the adjuster's own letters, including a legal basis for denial that changed three times, and reviewed each of his drafts as opposing counsel before anything was sent. After his letter quoting their own paper back at them, the offers climbed: $6,500, then $8,000, then $8,750, and the insurer accepted his split of the last gap the same morning, at $10,250.
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.
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.
Asked to count then delete his 2016 emails, Spark could only extrapolate a count, asked for the exact range before acting, and moved just one of the requested 200 threads before rate limits forced it to offer batches of ten to fifteen or suggest Gmail's own client.
This one went wrong. See what happened before you try it.
TechMitra founder Ayush Singhal asked the AI to triage his Gmail thread by thread. It proposed archiving ten promotional emails, correctly found nothing to do on other categories, and unprompted flagged a spam comment on his second website. After his approval it archived nine FYI threads and left two genuine action items.
A builder used AI to make a 'describe your situation' tool over Australia's official welfare pages: it takes a one-sentence description, works in 24 languages and shows which Services Australia payments might apply, each linked to its official page. Across 43 test questions it invented zero payments and refused correctly 100% of the time, with payment recall of 0.76.
Across the same two-week inbox-and-calendar test, the AI proactively flagged every one of the author's seven calendar double-bookings before the meetings occurred.
His agent reads his email, including PDF attachments, finds the dates and appointments inside, and adds them to his calendar with a check for duplicates. With two kids at different schools sending home a stream of letters, he calls it a big time saver.
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.
He pointed the AI Fable at a newspaper archive and asked for a timeline of wildfire events in and around the Adirondacks. The result is an interactive timeline built from 12,000 pages of newspapers.