What was the result?
self-reportedShawkat, a St. Louis founder who runs small-business work through a team of Grok Bots, says his company email was broken after 3 Microsoft support reps and a few hours of his own time. He says his bot fixed it in 3 minutes and then tested it end to end.
Shawkat's company email stopped working, and neither 3 Microsoft support reps nor a few hours of his own troubleshooting fixed it. He gave his Grok Bot, named Roxy, access, and says it fixed the problem in 3 minutes and tested the fix end to end. He does not say what the actual fault was. The play is handing a stuck IT problem to an agent that can log in and check settings, with you watching what it changes.
Who did this?
How do I try it?
- Editorial adaptation: write down the exact problem, error messages and what support already tried.
- Give the agent access to the admin console it needs, ideally through a separate admin account you can disable later.
- Ask it to explain what it finds and what it plans to change before it changes anything.
- Have it test the fix end to end, such as sending and receiving a test email from outside.
- Ask for a short log of every setting it changed, and remove or reduce its access afterwards.
Editorial adaptation, not Shawkat's exact request. My company email [describe problem, error messages, what support tried]. Using the admin access I've given you, find the cause. Before changing anything, tell me what you found and exactly what you plan to change. After I approve, make the fix, then test sending and receiving from an outside address. Give me a list of every setting you changed. Do not delete mailboxes, users or DNS records.
Make it run every week
A play works once. Turn it into a routine in three small steps:
- Run it once and check the result yourself.
- Give your AI a schedule. Tell it when to run this play (every week, or every month) and to message you with what it found before you act.
- Keep a log. One line per run: what was checked, anything flagged, what you did.
What should I watch out for?
Self-reported in one post; the fault and fix are not described. Giving an agent admin access to email or DNS is powerful and risky; use a separate admin account, ask for a plan before changes, and keep a log (Safer version). Build it with Page: an IT notes page listing your accounts and who has access.
Did it work for you?
PageMotor keeps this site free.