Grok Bot tests company email delivery and forwarding
@Shawkat_m1 reports Roxy, a Grok Bot, fixing company email and testing delivery end to end. An attached conversation shows outbound, inbound and forwarding checks.
x.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Investigate [company email delivery problem] using [authorised accounts]. Explain proposed changes before applying them. Test outbound delivery, authentication, inbound delivery and forwarding from an outside sender separately. Ask me before test sends and report the observed results.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- @Shawkat_m1
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- Company email fixed in 3 minutes and tested end to end, reported by the poster. The screenshot records the bot reporting successful outbound, inbound and external forwarding tests.
- Human involvement
- @Shawkat_m1 supplied access. The screenshot explicitly asks the poster to press Send for the outside-inbox test. The exact repair and actual mail headers are not shown.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- @Shawkat_m1 gave Roxy access to address a broken company email setup.
- The attached conversation shows the bot reporting an Outlook-to-Gmail test and SPF, DKIM and DMARC checks.
- The bot reports testing inbound delivery, then prepares an outside-inbox forwarding test and asks the poster to press Send.
@Shawkat_m1 says a Grok Bot named Roxy fixed broken company email after 3 Microsoft support reps and a few hours of the poster's time. The fix took 3 minutes, reported by the poster. The post itself does not identify the underlying configuration change.
An attached conversation provides more useful detail about the testing. The bot reports sending from Outlook to Gmail, checking inbox placement and examining signature headers. It says SPF, DKIM and DMARC pass, then distinguishes that outbound test from the remaining need to check inbound delivery and forwarding.
The conversation next describes a Gmail-to-company-inbox test. The bot says the message arrived in Outlook without a bounce, but explains that a self-sent message is not a decisive forwarding test. It therefore sets up an outside inbox and asks the poster to press Send on a mail card. Its final message reports that the external test reached the company inbox and forwarded to Gmail without bouncing.
These are visible bot statements in a screenshot, not independently inspected message headers or delivery logs. They support an account of staged verification with a human send checkpoint, not a reproducible diagnosis or a promise that similar email faults can always be fixed in the same time.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: X · @Shawkat_m1
Frequently asked questions
What caused the email problem?
The post and visible conversation do not establish the exact root cause or configuration change; an old IP-block bounce is mentioned by the bot.
What does the attached conversation show?
The bot describes outbound and inbound tests, authentication checks and a separate external forwarding test. These are bot-reported results, not independently inspected logs.
Was a person involved in the tests?
Yes. The bot asks the poster to press Send on the outside-inbox test card; the account is not evidence that every send was unattended.
More details
Remaining steps
- The screenshot records the bot reporting delivery to the company inbox and forwarding to Gmail without a bounce.
About this account
Roxy addresses the email problem and coordinates outbound delivery, authentication, inbound delivery and outside-sender forwarding checks, as described in the post and attached conversation.
Post text, publication date and bio checked through public FxTwitter syndication on 2026-10-27. Results reported by the poster, not independently reproduced. No Nous Research affiliation or tool-vendor employment is declared in the checked bio. Suggested prompt written by Agents In Use, not a quoted original prompt. Both attached images were inspected. One is about Search Console and unrelated to the repair; the other contains the bot-reported mail tests. Captured material includes a labelled reviewer transcription of the relevant test conversation, not raw mail headers.
Credit: @Shawkat_m1 on X
Source published
Added to Agents In Use
Source checked
Tools and topics
Grok Bot · Microsoft Outlook · Gmail
Email troubleshooting · Delivery testing · Human approval
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.