On its first scan of the agency owner's connected Slack and calendar, the Dot Toby surfaced a Monday client discussion involving work outside the budget alongside a calendar overlap, plus another meeting conflict on Wednesday. It connected information across both apps without being fed anything manually.
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.
Kndarp sent the AI a photo of a broken IKEA cupboard door with its article number. The AI searched his emails for the original order number, reached out to customer support on chat, and arranged a replacement parcel arriving next week at no cost — 'No £ spent.'
Lixka, an accelerated nursing student at Mercy University, uploaded all six syllabi to her AI 'Mila'. Mila identified that Monday, September 28th was a 'triple-header' — two quizzes and a Pharm lab she hadn't noticed — then built a sustainable weekly rhythm around fixed classes, clinicals, and workouts, and asked permission before creating three tracked goals: quiz prep, reflection paper, and workouts/downtime.
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 updated an old email triage workflow for a client this weekend. Jev now runs alongside GPT-4o mini, which still controls which emails get forwarded to her customers.
Hemant Kadam, demonstrating his 'craziest use case' after a couple of days on the AI, opened the app to a Sarvam DevOps Engineer application page. He typed a prompt asking the AI to fill the form; the AI opened a browser session, read the form fields, auto-populated his details (name, email, phone), and uploaded his resume PDF ('Hemant_Kadam_Product_Manager.pdf').
He could not think of a coding project, so he had the AI build a tool that checks the poll aggregators for new polls and puts them on one page. He now hears about new polls about five minutes sooner.