Before a speaking engagement, Ulanoff couldn't recall where he was talking or where to park. He asked the AI to find the original note from his contact, misspelling the contact's name.
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.
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.
His morning agent reads his email and builds a prioritized to do list with time blocks for the day. It also checks the weather and warns him to leave earlier when rain would slow his trip, which has twice saved him from showing up soaked.
The AI was fed government forms, UI design and legal requirements and produced the app in 1 hour; the team completed conversion of 150+ forms in 2 weeks with one person versus a year before.
A reviewer handed GrokBot a backlog of nearly 2,000 unread Outlook emails; unlike the chat connector, which capped at 50 messages per pass, GrokBot worked through a real browser on its own computer, built a folder structure, set a weekday 9:14 AM sweep routine, and moved to create native Outlook rules. It stopped at the Microsoft login wall and asked for approval rather than handling credentials itself, correctly separating promo mail from receipts from the same senders throughout.
This only partly worked. Worth knowing before you try it.
He runs AI on his homelab. He can ask the AI to throw an event on his calendar and it appears, and the setup can also send events to his primary calendar by email.